11.7 sec in total
2.4 sec
9.1 sec
147 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 2.4 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
eligor.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value15.4 s
0/100
25%
Value17.4 s
0/100
10%
Value840 ms
34/100
30%
Value0.074
95/100
15%
Value15.8 s
6/100
10%
2397 ms
68 ms
48 ms
272 ms
292 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 84% of them (106 requests) were addressed to the original Eligor.com, 6% (8 requests) were made to Cdnjs.cloudflare.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Eligor.com.
Page size can be reduced by 360.5 kB (28%)
1.3 MB
940.3 kB
In fact, the total size of Eligor.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 745.8 kB which makes up the majority of the site volume.
Potential reduce by 113.0 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 113.0 kB or 79% 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 171.8 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 171.8 kB or 23% of the original size.
Potential reduce by 67.3 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 67.3 kB or 36% of the original size.
Number of requests can be reduced by 108 (92%)
118
10
The browser has sent 118 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 80 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
www.eligor.com
2397 ms
gtm.js
68 ms
css
48 ms
ie10-viewport-bug-workaround.css
272 ms
slider-pro.min.css
292 ms
jquery-ui.min.css
315 ms
jquery.mCustomScrollbar.min.css
336 ms
ie-emulation-modes-warning.js
354 ms
wp-notification-bars-public.css
371 ms
style.min.css
491 ms
frontend.css
411 ms
owl.carousel.min.css
432 ms
cookie-law-info-public.css
453 ms
cookie-law-info-gdpr.css
475 ms
woocommerce-layout.css
489 ms
woocommerce.css
513 ms
common.css
533 ms
style.min.css
553 ms
cookieblocker.min.css
573 ms
search-filter.min.css
588 ms
bootstrap.min.css
42 ms
index.php
836 ms
lightbox.min.css
43 ms
all.css
48 ms
owl.carousel.min.css
52 ms
jquery.min.js
717 ms
jquery-migrate.min.js
650 ms
frontend.js
670 ms
owl.carousel.min.js
692 ms
cookie-law-info-public.js
710 ms
jquery.blockUI.min.js
745 ms
add-to-cart.min.js
764 ms
js.cookie.min.js
790 ms
woocommerce.min.js
804 ms
wp-notification-bars-public.js
825 ms
search-filter-build.min.js
860 ms
chosen.jquery.min.js
868 ms
ie10-viewport-bug-workaround.js
808 ms
popper.min.js
823 ms
infinite-scroll.pkgd.min.js
844 ms
jquery.sliderPro.min.js
869 ms
jquery-ui.min.js
980 ms
bootstrap.min.js
15 ms
lightbox.min.js
12 ms
owl.carousel.min.js
11 ms
wc-blocks.css
904 ms
file-upload.css
744 ms
dashicons.min.css
826 ms
display-structure.css
736 ms
display-structure.css
744 ms
display-structure.css
728 ms
cookie-law-info-table.css
744 ms
jquery.mCustomScrollbar.concat.min.js
734 ms
isotope.pkgd.min.js
733 ms
sourcebuster.min.js
735 ms
order-attribution.min.js
730 ms
react.min.js
737 ms
react-jsx-runtime.min.js
748 ms
hooks.min.js
747 ms
deprecated.min.js
750 ms
dom.min.js
756 ms
react-dom.min.js
847 ms
escape-html.min.js
757 ms
element.min.js
710 ms
is-shallow-equal.min.js
711 ms
i18n.min.js
710 ms
keycodes.min.js
718 ms
priority-queue.min.js
728 ms
compose.min.js
717 ms
private-apis.min.js
717 ms
redux-routine.min.js
712 ms
data.min.js
719 ms
lodash.min.js
723 ms
wp-polyfill.min.js
706 ms
wc-blocks-registry.js
715 ms
url.min.js
711 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff
19 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff
25 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff
32 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff
34 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XpjLdSL57k.woff
34 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5XpjLdSL57k.woff
34 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XpjLdSL57k.woff
34 ms
api-fetch.min.js
731 ms
wc-settings.js
735 ms
data-controls.min.js
732 ms
html-entities.min.js
728 ms
notices.min.js
709 ms
wc-blocks-middleware.js
709 ms
wc-blocks-data.js
697 ms
dom-ready.min.js
688 ms
a11y.min.js
707 ms
primitives.min.js
717 ms
warning.min.js
707 ms
blocks-components.js
726 ms
blocks-checkout.js
721 ms
order-attribution-blocks.min.js
702 ms
common.js
719 ms
site_main.js
721 ms
awdr-dynamic-price.js
714 ms
core.min.js
721 ms
datepicker.min.js
723 ms
functions.js
722 ms
main.js
717 ms
complianz.min.js
699 ms
jquery.iframe-transport.js
699 ms
jquery.fileupload.js
700 ms
jquery.fileupload-process.js
699 ms
jquery.fileupload-validate.js
705 ms
underscore.min.js
715 ms
backbone.min.js
720 ms
front-end-deps.js
719 ms
front-end.js
722 ms
fieldFile.js
719 ms
front-end.js
719 ms
front-end.js
706 ms
front-end.js
718 ms
logo-portail-daccueil.png
728 ms
logo-footer.svg
721 ms
portail-dacces-porte-professionnels-910x1024.jpg
719 ms
portail-dacces-porte-collectionneurs-910x1024.jpg
812 ms
prev.png
14 ms
next.png
18 ms
loading.gif
13 ms
close.png
17 ms
woocommerce-smallscreen.css
102 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
Links do not have a discernible name
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: