9.9 sec in total
1.6 sec
8 sec
234 ms
Welcome to eligor.com homepage info - get ready to check Eligor best content for France right away, or after learning these important things about eligor.com
Fabricant français de véhicules miniatures de collection et de modèles personnalisés de grande qualité à l'échelle 1/43ème depuis 1973
Visit eligor.comWe analyzed Eligor.com page load time and found that the first response time was 1.6 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eligor.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value14.3 s
0/100
25%
Value15.7 s
0/100
10%
Value7,830 ms
0/100
30%
Value0.074
95/100
15%
Value19.6 s
2/100
10%
1640 ms
59 ms
77 ms
364 ms
360 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 81% of them (73 requests) were addressed to the original Eligor.com, 9% (8 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Eligor.com.
Page size can be reduced by 186.4 kB (25%)
755.5 kB
569.2 kB
In fact, the total size of Eligor.com main page is 755.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. 55% of websites need less resources to load. Javascripts take 244.6 kB which makes up the majority of the site volume.
Potential reduce by 82.8 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 82.8 kB or 81% of the original size.
Potential reduce by 8.5 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. Eligor images are well optimized though.
Potential reduce by 46.4 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 46.4 kB or 19% of the original size.
Potential reduce by 48.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. Eligor.com needs all CSS files to be minified and compressed as it can save up to 48.7 kB or 26% of the original size.
Number of requests can be reduced by 74 (84%)
88
14
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eligor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
www.eligor.com
1640 ms
gtm.js
59 ms
css
77 ms
ie10-viewport-bug-workaround.css
364 ms
slider-pro.min.css
360 ms
jquery-ui.min.css
449 ms
jquery.mCustomScrollbar.min.css
609 ms
ie-emulation-modes-warning.js
422 ms
style.min.css
604 ms
wc-blocks-vendors-style.css
502 ms
wc-blocks-style.css
925 ms
analytics.js
73 ms
frontend.css
438 ms
owl.carousel.min.css
593 ms
cookie-law-info-public.css
593 ms
cookie-law-info-gdpr.css
667 ms
woocommerce-layout.css
817 ms
woocommerce.css
895 ms
common.css
693 ms
style.min.css
781 ms
search-filter.min.css
932 ms
bootstrap.min.css
123 ms
index.php
1580 ms
lightbox.min.css
119 ms
all.css
223 ms
owl.carousel.min.css
152 ms
jquery.min.js
1164 ms
jquery-migrate.min.js
1169 ms
frontend.js
994 ms
owl.carousel.min.js
1002 ms
cookie-law-info-public.js
1170 ms
search-filter-build.min.js
1132 ms
chosen.jquery.min.js
1141 ms
collect
32 ms
ie10-viewport-bug-workaround.js
1119 ms
popper.min.js
1159 ms
infinite-scroll.pkgd.min.js
1179 ms
jquery.sliderPro.min.js
1400 ms
jquery-ui.min.js
1819 ms
jquery.mCustomScrollbar.concat.min.js
1353 ms
isotope.pkgd.min.js
1343 ms
file-upload.css
1316 ms
dashicons.min.css
1912 ms
display-structure.css
1815 ms
bootstrap.min.js
36 ms
lightbox.min.js
35 ms
owl.carousel.min.js
35 ms
collect
33 ms
ga-audiences
32 ms
display-structure.css
1747 ms
display-structure.css
1766 ms
cookie-law-info-table.css
1767 ms
jquery.blockUI.min.js
1709 ms
add-to-cart.min.js
1682 ms
js.cookie.min.js
1630 ms
woocommerce.min.js
1614 ms
cart-fragments.min.js
1525 ms
common.js
1503 ms
site_main.js
1501 ms
awdr-dynamic-price.js
1501 ms
core.min.js
1756 ms
datepicker.min.js
1734 ms
functions.js
1333 ms
main.js
1683 ms
front-scripts.min.js
1572 ms
cart_widget.min.js
1484 ms
jquery.iframe-transport.js
1534 ms
jquery.fileupload.js
1615 ms
jquery.fileupload-process.js
1520 ms
jquery.fileupload-validate.js
1409 ms
underscore.min.js
1581 ms
backbone.min.js
1407 ms
front-end-deps.js
1588 ms
front-end.js
1573 ms
fieldFile.js
1483 ms
front-end.js
1474 ms
front-end.js
1453 ms
front-end.js
1544 ms
wp-emoji-release.min.js
1428 ms
logo-portail-daccueil.png
1120 ms
logo-footer.svg
1031 ms
portail-dacces-porte-professionnels-910x1024.jpg
1636 ms
portail-dacces-porte-collectionneurs-910x1024.jpg
1662 ms
www.eligor.com
124 ms
prev.png
65 ms
next.png
40 ms
loading.gif
41 ms
close.png
41 ms
www.eligor.com
964 ms
woocommerce-smallscreen.css
130 ms
eligor.com 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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eligor.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eligor.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eligor.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Eligor.com 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.
eligor.com
Open Graph data is detected on the main page of Eligor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: