Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 0

    Best Practices

  • 54

    SEO

    Google-friendlier than
    19% of websites

Page Load Speed

6 sec in total

First Response

1.1 sec

Resources Loaded

4.8 sec

Page Rendered

101 ms

stats.lef.pl screenshot

About Website

Visit stats.lef.pl now to see the best up-to-date Stats Lef content for Poland and also check out these interesting facts you probably never knew about stats.lef.pl

free/libre analytics platform

Visit stats.lef.pl

Key Findings

We analyzed Stats.lef.pl page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

stats.lef.pl performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value0.8 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.8 s

100/100

10%

Network Requests Diagram

stats.lef.pl

1145 ms

index.php

1023 ms

index.php

3425 ms

index.php

2482 ms

jquery.placeholder.js

189 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that all of those requests were addressed to Stats.lef.pl and no external sources were called. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Stats.lef.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.6 kB (82%)

Content Size

327.2 kB

After Optimization

59.6 kB

In fact, the total size of Stats.lef.pl main page is 327.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. CSS take 268.0 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 17.9 kB

  • Original 25.7 kB
  • After minification 24.3 kB
  • After compression 7.8 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 17.9 kB or 70% of the original size.

Image Optimization

-76%

Potential reduce by 10.2 kB

  • Original 13.4 kB
  • After minification 3.2 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, Stats Lef needs image optimization as it can save up to 10.2 kB or 76% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 16.1 kB

  • Original 20.1 kB
  • After minification 12.6 kB
  • After compression 4.0 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 16.1 kB or 80% of the original size.

CSS Optimization

-83%

Potential reduce by 223.3 kB

  • Original 268.0 kB
  • After minification 226.4 kB
  • After compression 44.6 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. Stats.lef.pl needs all CSS files to be minified and compressed as it can save up to 223.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (50%)

Requests Now

12

After Optimization

6

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stats Lef. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

stats.lef.pl accessibility score

93

Accessibility Issues

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

SEO Factors

stats.lef.pl SEO score

54

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

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stats.lef.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish 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 Stats.lef.pl main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

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