Tools & Wizards About Us
eco.pl screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    94% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

eco.pl

Aktualności Fairtrade

Page Load Speed

6.2 sec in total

First Response

1 sec

Resources Loaded

5 sec

Page Rendered

114 ms

eco.pl screenshot

About Website

Click here to check amazing Eco content for Poland. Otherwise, check out these important facts you probably never knew about eco.pl

Informacje ze świata Sprawiedliwego Handlu

Visit eco.pl

Key Findings

We analyzed Eco.pl page load time and found that the first response time was 1 sec and then it took 5.2 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

eco.pl performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value5.9 s

49/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

eco.pl

1044 ms

_s.css

171 ms

_i.js

205 ms

s.js

1063 ms

s4u.gif

905 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 21% of them (12 requests) were addressed to the original Eco.pl, 74% (42 requests) were made to Zig.eco.pl and 4% (2 requests) were made to Ad.stat.4u.pl. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Zig.eco.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.7 kB (29%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eco.pl main page is 1.5 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 10.3 kB

  • Original 12.9 kB
  • After minification 9.6 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 3.3 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.3 kB or 80% of the original size.

Image Optimization

-22%

Potential reduce by 284.1 kB

  • Original 1.3 MB
  • After minification 1.0 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. Obviously, Eco needs image optimization as it can save up to 284.1 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-81%

Potential reduce by 143.6 kB

  • Original 176.7 kB
  • After minification 115.0 kB
  • After compression 33.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 143.6 kB or 81% of the original size.

CSS Optimization

-77%

Potential reduce by 2.7 kB

  • Original 3.5 kB
  • After minification 3.1 kB
  • After compression 800 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. Eco.pl needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (5%)

Requests Now

56

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eco. 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 as a result speed up the page load time.

Network Requests Diagram

eco.pl

eco.pl

1044 ms

_s.css

_s.css

171 ms

_i.js

_i.js

205 ms

s.js

s.js

1063 ms

s4u.gif

s4u.gif

905 ms

w1.jpg

w1.jpg

174 ms

komp.gif

komp.gif

173 ms

l-prac.gif

l-prac.gif

180 ms

l-wied.gif

l-wied.gif

180 ms

l-klub.gif

l-klub.gif

189 ms

l-capo.gif

l-capo.gif

266 ms

wd.gif

wd.gif

381 ms

w2.jpg

w2.jpg

392 ms

w3.jpg

w3.jpg

430 ms

s.cgi

s.cgi

411 ms

external.php

external.php

738 ms

jquery.js

jquery.js

265 ms

jquery.cycle.all.js

jquery.cycle.all.js

174 ms

26.png

26.png

254 ms

44.png

44.png

255 ms

40.png

40.png

257 ms

29.png

29.png

258 ms

11.png

11.png

259 ms

15.png

15.png

261 ms

35.png

35.png

506 ms

25.png

25.png

510 ms

24.png

24.png

524 ms

36.png

36.png

523 ms

33.png

33.png

516 ms

5.png

5.png

525 ms

39.png

39.png

760 ms

14.png

14.png

769 ms

43.png

43.png

784 ms

4.png

4.png

798 ms

28.png

28.png

890 ms

13.png

13.png

801 ms

31.png

31.png

1020 ms

9.png

9.png

1027 ms

16.png

16.png

1036 ms

17.png

17.png

1053 ms

32.png

32.png

1059 ms

10.png

10.png

1157 ms

7.png

7.png

1279 ms

27.png

27.png

1281 ms

34.png

34.png

1311 ms

12.png

12.png

1319 ms

37.png

37.png

1315 ms

6.png

6.png

1412 ms

38.png

38.png

1530 ms

21.png

21.png

1540 ms

42.png

42.png

1578 ms

22.png

22.png

1572 ms

3.png

3.png

1575 ms

23.png

23.png

1668 ms

2.png

2.png

1619 ms

41.png

41.png

1566 ms

18.png

18.png

1579 ms

Accessibility Review

eco.pl accessibility score

57

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

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

High

Links do not have a discernible name

Best Practices

eco.pl best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

eco.pl SEO score

62

Search Engine Optimization Advices

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

    PL

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eco.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 Eco.pl main page’s claimed encoding is iso-8859-2. 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

eco.pl

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