Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 58

    SEO

    Google-friendlier than
    30% of websites

epuls.pl

Epuls.pl

Page Load Speed

4.2 sec in total

First Response

596 ms

Resources Loaded

3.4 sec

Page Rendered

209 ms

epuls.pl screenshot

About Website

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

Visit epuls.pl

Key Findings

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

Performance Metrics

epuls.pl performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

epuls.pl

596 ms

dojo.xd.js

688 ms

layout.20090624.1.js

468 ms

swfobject_source.js

356 ms

globalController.js

358 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Epuls.pl, 81% (126 requests) were made to Img2.epuls.pl and 6% (10 requests) were made to Img.epuls.pl. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Img2.epuls.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (60%)

Content Size

2.4 MB

After Optimization

969.8 kB

In fact, the total size of Epuls.pl main page is 2.4 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. 40% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 46.8 kB

  • Original 58.0 kB
  • After minification 45.4 kB
  • After compression 11.2 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 12.6 kB, which is 22% 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 46.8 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 50.3 kB

  • Original 653.9 kB
  • After minification 603.7 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. Epuls images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 839.3 kB

  • Original 1.1 MB
  • After minification 908.1 kB
  • After compression 273.6 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 839.3 kB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 504.8 kB

  • Original 586.2 kB
  • After minification 495.8 kB
  • After compression 81.4 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. Epuls.pl needs all CSS files to be minified and compressed as it can save up to 504.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (52%)

Requests Now

151

After Optimization

73

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

Accessibility Review

epuls.pl accessibility score

66

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

epuls.pl 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

epuls.pl SEO score

58

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

    N/A

  • Language Claimed

    PL

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epuls.pl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Polish. Our system also found out that Epuls.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

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