Tools & Wizards About Us
lua.org screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

lua.org

The Programming Language Lua

Page Load Speed

1.4 sec in total

First Response

273 ms

Resources Loaded

1 sec

Page Rendered

109 ms

lua.org screenshot

About Website

Click here to check amazing Lua content for China. Otherwise, check out these important facts you probably never knew about lua.org

Official website of the Lua language

Visit lua.org

Key Findings

We analyzed Lua.org page load time and found that the first response time was 273 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

lua.org performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

lua.org

273 ms

www.lua.org

569 ms

lua.css

92 ms

lua.gif

180 ms

puc.gif

180 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that all of those requests were addressed to Lua.org and no external sources were called. The less responsive or slowest element that took the longest time to load (569 ms) belongs to the original domain Lua.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.3 kB (38%)

Content Size

58.7 kB

After Optimization

36.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Lua.org main page is 58.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 53.4 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.7 kB

  • Original 3.0 kB
  • After minification 2.9 kB
  • After compression 1.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.7 kB or 58% of the original size.

Image Optimization

-36%

Potential reduce by 19.1 kB

  • Original 53.4 kB
  • After minification 34.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Lua needs image optimization as it can save up to 19.1 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-68%

Potential reduce by 1.6 kB

  • Original 2.3 kB
  • After minification 1.8 kB
  • After compression 724 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lua.org needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 68% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images
  • CSS

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lua. According to our analytics all requests are already optimized.

Network Requests Diagram

lua.org

lua.org

273 ms

www.lua.org

www.lua.org

569 ms

lua.css

lua.css

92 ms

lua.gif

lua.gif

180 ms

puc.gif

puc.gif

180 ms

search.png

search.png

94 ms

Accessibility Review

lua.org accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

lua.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

lua.org SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lua.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lua.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lua.org

Open Graph description is not detected on the main page of Lua. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: