Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ekoportal.pl

Strona główna - EKOportal

Page Load Speed

5.6 sec in total

First Response

316 ms

Resources Loaded

5.1 sec

Page Rendered

248 ms

ekoportal.pl screenshot

About Website

Welcome to ekoportal.pl homepage info - get ready to check EKOportal best content for Poland right away, or after learning these important things about ekoportal.pl

Visit ekoportal.pl

Key Findings

We analyzed Ekoportal.pl page load time and found that the first response time was 316 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ekoportal.pl performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

ekoportal.pl

316 ms

www.ekoportal.gov.pl

2470 ms

stylesheet_9577fb8b58.css

220 ms

lessphp_48e4c6a220a786ac63953c474b7ed48e04fb2a19.css

768 ms

flexslider.css

222 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ekoportal.pl, 81% (43 requests) were made to Ekoportal.gov.pl and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Ekoportal.gov.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 865.4 kB (76%)

Content Size

1.1 MB

After Optimization

270.4 kB

In fact, the total size of Ekoportal.pl main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 668.2 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 614.9 kB

  • Original 668.2 kB
  • After minification 661.9 kB
  • After compression 53.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 614.9 kB or 92% of the original size.

Image Optimization

-38%

Potential reduce by 80.2 kB

  • Original 210.3 kB
  • After minification 130.1 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, EKOportal needs image optimization as it can save up to 80.2 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 170.3 kB

  • Original 257.3 kB
  • After minification 257.3 kB
  • After compression 87.1 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 170.3 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (63%)

Requests Now

46

After Optimization

17

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

Accessibility Review

ekoportal.pl accessibility score

100

Accessibility Issues

Best Practices

ekoportal.pl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ekoportal.pl SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekoportal.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Ekoportal.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 EKOportal. 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: