4.5 sec in total
1.5 sec
2.9 sec
95 ms
Welcome to e.pl homepage info - get ready to check E best content for Poland right away, or after learning these important things about e.pl
e.pl – adres, którego nie można zapomnieć - centrum e-handlu i e-usług. Znajdziesz tutaj najniższe ceny na wszelakie produkty włączając w to aparaty cyfrowe, notebooki, projektory, komputery i akcesor...
Visit e.plWe analyzed E.pl page load time and found that the first response time was 1.5 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
e.pl performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value2.7 s
86/100
25%
Value4.1 s
78/100
10%
Value10 ms
100/100
30%
Value0.001
100/100
15%
Value2.0 s
99/100
10%
1499 ms
436 ms
719 ms
172 ms
163 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 98% of them (39 requests) were addressed to the original E.pl, 3% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain E.pl.
Page size can be reduced by 65.6 kB (53%)
123.5 kB
57.8 kB
In fact, the total size of E.pl main page is 123.5 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. 15% of websites need less resources to load. Javascripts take 48.1 kB which makes up the majority of the site volume.
Potential reduce by 34.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 34.6 kB or 85% of the original size.
Potential reduce by 5.9 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, E needs image optimization as it can save up to 5.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 25.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 25.1 kB or 52% of the original size.
Number of requests can be reduced by 15 (38%)
39
24
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
e.pl
1499 ms
partner.js
436 ms
function_normal.js
719 ms
header_face.jpg
172 ms
header_text_wp.jpg
163 ms
header_bg.jpg
162 ms
menu_top.gif
291 ms
menu_top_center.gif
292 ms
menu_top_left_selected.gif
292 ms
menu_top_bg_selected.gif
311 ms
generated_1c55b6840a5fd954a9e25c1828f166e8.png
312 ms
menu_top_right_selected.gif
321 ms
menu_top_left.gif
440 ms
menu_top_bg.gif
440 ms
generated_c7ac7fc1dc5e2d1c7bb2f52adaece70a.png
440 ms
menu_top_right.gif
460 ms
generated_a096be77a32edab001a662188998095b.png
460 ms
generated_9bdf8550f7aed7f6ba06c5d2eb19af51.png
470 ms
menu_bottom.gif
591 ms
blank.gif
589 ms
generated_5c9d93da869f52dc7773fd12615cb6aa.png
590 ms
generated_d48215a45fa51b0ec1a0a979e4e689e4.gif
609 ms
generated_3259267132ca77f6ac2de2d869a3f61f.png
609 ms
generated_dd63ad73411f9eef3a2710b7c4df4e9c.gif
619 ms
generated_91518edc425fa05245b4f95943662389.png
739 ms
2004_07_26_silver.jpg
738 ms
generated_3f39d69c6453a923e40c8e8aba2e6ee1.gif
739 ms
generated_640899b993fb10b9b7079c42cc9e34d6.gif
758 ms
generated_a6b8290af97dba6817dbf3c2252a5fff.gif
759 ms
generated_33e5b2c101ca4c2793367914782eabd8.png
768 ms
2004_07_26_gold.jpg
888 ms
generated_cbfd56d174e80cf4025cc80772ee40fc.gif
888 ms
generated_912b8ecaa628cee9bbebbb23baebbbc1.png
888 ms
2004_07_26_platinum.jpg
907 ms
generated_a0c4d6e8f365583b1440ab1bdc45abca.gif
907 ms
generated_66d07edd8972035220c348d80a35971f.png
916 ms
2004_07_26_mojafirma.jpg
1037 ms
generated_21810acc12f0d39e24f6d3c73525d0c3.gif
1038 ms
ga.js
9 ms
generated_1f423acc2b39b2cdae3379993e7dabf2.png
1030 ms
e.pl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
e.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
e.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
PL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E.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 E.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.
e.pl
Open Graph description is not detected on the main page of E. 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: