Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

leoz.com

Froxlor Domain Default Page

Page Load Speed

583 ms in total

First Response

253 ms

Resources Loaded

267 ms

Page Rendered

63 ms

leoz.com screenshot

About Website

Welcome to leoz.com homepage info - get ready to check Leoz best content right away, or after learning these important things about leoz.com

Visit leoz.com

Key Findings

We analyzed Leoz.com page load time and found that the first response time was 253 ms and then it took 330 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

leoz.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

leoz.com

253 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (10%)

Content Size

17.2 MB

After Optimization

15.4 MB

In fact, the total size of Leoz.com main page is 17.2 MB. 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 16.9 MB which makes up the majority of the site volume.

HTML Optimization

-30%

Potential reduce by 1.9 kB

  • Original 6.6 kB
  • After minification 6.5 kB
  • After compression 4.6 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.9 kB or 30% of the original size.

Image Optimization

-9%

Potential reduce by 1.6 MB

  • Original 16.9 MB
  • After minification 15.3 MB

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. Leoz images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 116.5 kB

  • Original 190.8 kB
  • After minification 141.0 kB
  • After compression 74.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 116.5 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 85.4 kB

  • Original 101.7 kB
  • After minification 71.1 kB
  • After compression 16.3 kB

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. Leoz.com needs all CSS files to be minified and compressed as it can save up to 85.4 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

leoz.com accessibility score

75

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

leoz.com 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

leoz.com SEO score

50

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leoz.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Leoz.com main page’s claimed encoding is . 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

Open Graph description is not detected on the main page of Leoz. 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: