5.1 sec in total
1.2 sec
3.6 sec
326 ms
Visit ecat.elit.ro now to see the best up-to-date ECAT ELIT content for Romania and also check out these interesting facts you probably never knew about ecat.elit.ro
LKQ Elit Piese Auto Originale va ofera o gama diversa de piese auto pentru autoturisme si autoutilitare, scule si echipamente pentru service auto si servicii post vanzare.
Visit ecat.elit.roWe analyzed Ecat.elit.ro page load time and found that the first response time was 1.2 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ecat.elit.ro performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value8.5 s
1/100
25%
Value7.6 s
25/100
10%
Value570 ms
52/100
30%
Value0.137
79/100
15%
Value8.8 s
35/100
10%
1207 ms
360 ms
246 ms
248 ms
606 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 72% of them (65 requests) were addressed to the original Ecat.elit.ro, 21% (19 requests) were made to Img.elit.cz and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Img.elit.cz.
Page size can be reduced by 1.5 MB (35%)
4.3 MB
2.8 MB
In fact, the total size of Ecat.elit.ro main page is 4.3 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. 55% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 65.4 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 65.4 kB or 79% of the original size.
Potential reduce by 68.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. ECAT ELIT images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 81% of the original size.
Potential reduce by 167.7 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. Ecat.elit.ro needs all CSS files to be minified and compressed as it can save up to 167.7 kB or 83% of the original size.
Number of requests can be reduced by 54 (61%)
89
35
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECAT ELIT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ecat.elit.ro
1207 ms
styles.css
360 ms
skin.css
246 ms
dd.css
248 ms
jquery-1.7.2.min.js
606 ms
jquery.ie-select-width.js
250 ms
util.js
368 ms
jquery.filtercomplete.js
388 ms
jquery.innerfiltercomplete.js
391 ms
jquery.jcarousel.js
518 ms
jquery.text-overflow.js
475 ms
jquery.numericupdown.js
483 ms
jquery.dd.min.js
514 ms
jquery.baloon.js
515 ms
base64min.js
595 ms
jquery.scrollTo.min.js
597 ms
colorbox.css
635 ms
WebResource.axd
755 ms
ScriptResource.axd
1023 ms
ScriptResource.axd
712 ms
ScriptResource.axd
713 ms
ScriptResource.axd
718 ms
ScriptResource.axd
749 ms
ScriptResource.axd
945 ms
ScriptResource.axd
740 ms
ScriptResource.axd
741 ms
ScriptResource.axd
770 ms
ScriptResource.axd
775 ms
ScriptResource.axd
846 ms
ScriptResource.axd
858 ms
ScriptResource.axd
889 ms
ScriptResource.axd
896 ms
jquery.jstree.js
1090 ms
style.css
960 ms
jquery-ui-1.8.22.custom.min.js
1224 ms
jquery.ui.combogrid-1.6.2.js
1005 ms
jquery-ui-1.8.22.custom.css
912 ms
jquery.ui.combogrid.css
915 ms
jquery-ui.min.css
947 ms
jquery.colorbox-min.js
992 ms
jquery-ui.min.js
896 ms
logo-ecat.png
481 ms
0ad8a10b-8b98-489f-a8ee-61a2f6417ab4.png
609 ms
3286cbeb-ba90-490c-b5a8-416c2d5ce94b.png
610 ms
14d888fe-268d-4e37-991f-2f5ff786166b.jpg
1512 ms
e8f176a7-ca4c-490f-bd54-bf0deadde68f.jpg
1331 ms
e49db51e-308c-4cb6-a88d-fe7e988ff1fe.jpg
1572 ms
2b9f5772-65e3-4384-9fee-4bce2bb51224.jpg
1395 ms
8b6caafd-6b34-4941-b83c-e548e744fbd7.jpg
1631 ms
ef45204c-c4ba-43f8-acae-e86e6369cb7f.jpg
1341 ms
1674a0bc-6de5-4522-9e26-d6a7a99f3d6b.jpg
1704 ms
143d21b4-f13a-4289-a54c-17e5164fd1dc.jpg
1576 ms
4036523d-cb19-407c-9306-d0a3289b11c1.jpg
1622 ms
a72e43141f664bc48341dcba8548e5b5.jpg
1628 ms
19f6dddf9e504f07959454cba3a7e9f3.jpg
1690 ms
39be0142763e4844a9cad1ddc4602fc7.jpg
1693 ms
50cd463e688a4fe7a2f008c1ffac55de.jpg
1736 ms
bfa1909608524cae9ef160676f69b921.jpg
1747 ms
75644892a18144aa994881617200166d.jpg
1746 ms
f6ecb21297ba4e9da0bf6510253025e4.jpg
1809 ms
N-background.png
521 ms
N-magnifier.png
542 ms
minimize.png
553 ms
help.png
603 ms
close.png
610 ms
whisphlp.png
746 ms
footer-rhiag.png
746 ms
footer-tecdoc.png
746 ms
s.gif
746 ms
ga.js
38 ms
__utm.gif
11 ms
overlay.png
462 ms
N-mainborder.png
467 ms
basket.png
485 ms
submenuend.png
476 ms
N-subborder.png
497 ms
analytics.js
134 ms
counter.js
7 ms
t.php
144 ms
flag_ro.png
125 ms
flag_en.png
122 ms
flag_ua.png
136 ms
flag_hu.png
149 ms
title-bg.gif
176 ms
dd_arrow.gif
173 ms
arrowLeft.png
242 ms
arrowRight.png
244 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
258 ms
collect
11 ms
print.css
119 ms
ecat.elit.ro 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
Buttons do not have an accessible name
Links do not have a discernible name
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
ecat.elit.ro best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ecat.elit.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecat.elit.ro can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ecat.elit.ro 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.
ecat.elit.ro
Open Graph description is not detected on the main page of ECAT ELIT. 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: