9.4 sec in total
1.4 sec
7.7 sec
327 ms
Visit elgo.pl now to see the best up-to-date Elgo content and also check out these interesting facts you probably never knew about elgo.pl
Oferujemy całą gamę opraw oświetleniowych LED i tradycyjnych. Zajmujemy się również sprzedażą szerokiego asortymentu źródeł światła. Serdecznie zapraszamy!
Visit elgo.plWe analyzed Elgo.pl page load time and found that the first response time was 1.4 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
elgo.pl performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.21
59/100
15%
Value0
0/100
10%
1408 ms
604 ms
360 ms
361 ms
724 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Elgo.pl, 6% (4 requests) were made to App.customericare.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Brilum24.pl.
Page size can be reduced by 1.1 MB (37%)
2.9 MB
1.8 MB
In fact, the total size of Elgo.pl main page is 2.9 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 172.9 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 102.3 kB, which is 55% 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 172.9 kB or 93% of the original size.
Potential reduce by 197.0 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, Elgo needs image optimization as it can save up to 197.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 509.9 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 509.9 kB or 67% of the original size.
Potential reduce by 199.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. Elgo.pl needs all CSS files to be minified and compressed as it can save up to 199.6 kB or 81% of the original size.
Number of requests can be reduced by 14 (23%)
62
48
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elgo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
brilum24.pl
1408 ms
ODoxOjA6cGxfUEw6MTowOm1haW4.css
604 ms
brilumico.css
360 ms
style.min.css
361 ms
ODowOjA6cGxfUEw6MDoxOm1haW4tanE.js
724 ms
jstree.min.js
484 ms
moretext.js
471 ms
api
539 ms
conversion.js
40 ms
api.1104.js
286 ms
analytics.js
95 ms
1px.gif
580 ms
logo.png
582 ms
throbber.gif
576 ms
300_300_productGfx_deacfd91b8e9d7246c155b47b0cb64d8.jpg
578 ms
300_300_productGfx_5781624f759cc498073a80660478dd39.jpg
576 ms
300_300_productGfx_5073ad599ecc408f8724bdf05f7d0940.jpg
575 ms
300_300_productGfx_91c549539f574594328882c64b7bbbda.jpg
924 ms
300_300_productGfx_f99b1b8fcfa5149281106b974d2715db.jpg
926 ms
300_300_productGfx_501fec020f3d6e324eb2f9a561c057f3.jpg
929 ms
300_300_productGfx_968ab58654c938d4ad9d2748670a9f54.jpg
931 ms
300_300_productGfx_d9bbb3ad09996880ceb35a66a20a25cf.jpg
929 ms
300_300_productGfx_72eb1cd0f0751df0a1ea40b21850942b.jpg
928 ms
300_300_productGfx_4eb23f67c61e4fc61dea1be49d777016.jpg
1290 ms
300_300_productGfx_426c4dcbc5a59f072d758b98283a89f9.jpg
1296 ms
300_300_productGfx_db25bff7172ccdfeb3a180e6ce418b4a.jpg
1298 ms
300_300_productGfx_6716476a434be52e2100263639c31dd2.jpg
1297 ms
300_300_productGfx_8c770eaf08a33c09ff4427452c2ac26a.jpg
1297 ms
300_300_productGfx_f78b3f81ad154d626a897ab167d27181.jpg
1296 ms
300_0_productGfx_8dc0d43b01ed483882569d010ba4dc76.jpg
1644 ms
300_0_productGfx_a44be23732bcea57bfc1b767d90d7dc5.jpg
1653 ms
300_300_productGfx_1f1aa12faea5590a77751d5300142eb6.jpg
1654 ms
300_300_productGfx_bcd519944ed492fce6b2b8f83efaa679.jpg
1657 ms
300_0_productGfx_cc338996caca1cfe20790f1c1eb6fca7.jpg
1654 ms
300_300_productGfx_14b9e5dcfacdc6acd9f604e8d681eebc.jpg
1656 ms
300_0_productGfx_63e4e98d370382f265cf00927608d0f9.jpg
1999 ms
gplus-icon.png
2007 ms
twitter-icon.png
2008 ms
pinterest-icon.png
2011 ms
gtm.js
138 ms
logo_background.png
1981 ms
LIGHTPLUS_rz_small.png
1980 ms
tags_npb.png
2280 ms
led.png
2288 ms
MyriadPro-Regular.otf
2655 ms
MyriadPro-Light.otf
2656 ms
brilumico85883158.woff
2289 ms
MyriadPro-Semibold.otf
2655 ms
api_package.js
377 ms
collect
259 ms
collect
328 ms
278 ms
conversion_async.js
256 ms
46 ms
49 ms
ga-audiences
26 ms
rwd-custom.woff
2148 ms
fontawesome-webfont.woff
2397 ms
MyriadPro-BoldCond.otf
2515 ms
b5f6213b2abf77f394212aec32941dde.jpg
3329 ms
7391b936e293c5b0268f9bbbe8406f72.jpg
3101 ms
67237efe4f4a14e23f9d1182b488b361.jpg
3455 ms
2a59666ceb01b51dd1d101d60b5262a1.jpg
3105 ms
7c2ec46852f01cb4b83e9a0857109abf.jpg
3105 ms
9b0de2d30259f24d83157094b6504396.jpg
3698 ms
667f0f39f052e0c886c0febf00c193cb.jpg
3810 ms
ico_arrow_left_small.png
3328 ms
ico_arrow_right_small.png
3456 ms
32px.png
3096 ms
api.php
176 ms
elgo.pl accessibility score
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
<frame> or <iframe> elements do not have a title
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
elgo.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
elgo.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elgo.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 Elgo.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.
elgo.pl
Open Graph description is not detected on the main page of Elgo. 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: