10.9 sec in total
1.6 sec
7 sec
2.3 sec
Visit eor.fr now to see the best up-to-date EOR content for France and also check out these interesting facts you probably never knew about eor.fr
Des conseillers en calcul et bilan retraite pour une assistance et un accompagnement sur-mesure pour votre dossier et départ à la retraite!
Visit eor.frWe analyzed Eor.fr page load time and found that the first response time was 1.6 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 85% of websites can load faster.
eor.fr performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value8.1 s
2/100
25%
Value11.3 s
5/100
10%
Value14,450 ms
0/100
30%
Value0.076
95/100
15%
Value26.5 s
0/100
10%
1556 ms
357 ms
346 ms
182 ms
347 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 57% of them (65 requests) were addressed to the original Eor.fr, 18% (20 requests) were made to Maps.googleapis.com and 9% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Eor.fr.
Page size can be reduced by 2.0 MB (48%)
4.2 MB
2.2 MB
In fact, the total size of Eor.fr main page is 4.2 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. 70% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 218.3 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 218.3 kB or 83% of the original size.
Potential reduce by 7.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. EOR 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 71% of the original size.
Potential reduce by 536.9 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. Eor.fr needs all CSS files to be minified and compressed as it can save up to 536.9 kB or 79% of the original size.
Number of requests can be reduced by 64 (69%)
93
29
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EOR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.eor.fr
1556 ms
jquery-2.1.4.min.js
357 ms
jquery.js
346 ms
jquery.validationEngine-fr.js
182 ms
jquery.validationEngine.js
347 ms
front-subscribers.js
187 ms
platform.js
64 ms
widget.css
292 ms
validationEngine.jquery.css
296 ms
layerslider.css
314 ms
css
26 ms
style.css
393 ms
dashicons.min.css
531 ms
desktop_style.css
395 ms
styles.css
406 ms
settings.css
419 ms
frontend.css
410 ms
style.css
1004 ms
font-awesome.css
498 ms
ilightbox.css
511 ms
style.css
518 ms
styles.css
527 ms
magnific-popup.css
600 ms
jquery-ui-skeleton.min.css
633 ms
business-contact-widget-skeleton.min.css
632 ms
business-contact-widget.min.css
634 ms
js
37 ms
infobox.js
30 ms
greensock.js
485 ms
jquery.min.js
31 ms
jquery-migrate.min.js
541 ms
layerslider.kreaturamedia.jquery.js
560 ms
layerslider.transitions.js
608 ms
jquery-ui.min.js
50 ms
business-contact-widget.min.js
572 ms
front_end_script.js
578 ms
jquery.form.min.js
632 ms
scripts.js
653 ms
itro-scripts.js
669 ms
jquery.themepunch.tools.min.js
782 ms
jquery.themepunch.revolution.min.js
804 ms
sbp-lazy-load.min.js
724 ms
comment-reply.min.js
745 ms
main.min.js
1126 ms
wp-embed.min.js
816 ms
pictograms-nps-telephone.png
715 ms
logosansblanc.png
721 ms
Telephone_Agenda_64.png
812 ms
Man_sitting_on_office_desk_working_in_front_a_monitor_of_computer_64.png
815 ms
close-icon.png
817 ms
sdk.js
270 ms
wp-emoji-release.min.js
766 ms
logo1.jpg
844 ms
greensock.js
569 ms
56 ms
xd_arbiter.php
216 ms
xd_arbiter.php
503 ms
analytics.js
12 ms
collect
68 ms
home2-min-min.jpg
1372 ms
bkgd_bw2.jpg
35 ms
mail.png
280 ms
paris2-min-min.jpg
1415 ms
collect
60 ms
bkgd_bw2.jpg
55 ms
icomoon.woff
656 ms
webfont.woff
185 ms
greensock.js
82 ms
webfont.ttf
182 ms
fontawesome-webfont.woff
305 ms
greensock.js
86 ms
greensock.js
86 ms
greensock.js
93 ms
greensock.js
88 ms
greensock.js
89 ms
greensock.js
97 ms
greensock.js
641 ms
www.eor.fr
822 ms
www.eor.fr
867 ms
ajax-loader.gif
106 ms
common.js
115 ms
util.js
117 ms
geocoder.js
115 ms
map.js
108 ms
marker.js
66 ms
infowindow.js
66 ms
onion.js
31 ms
openhand_8_8.cur
19 ms
StaticMapService.GetMapImage
331 ms
ViewportInfoService.GetViewportInfo
175 ms
stats.js
33 ms
controls.js
45 ms
css
20 ms
transparent.png
19 ms
mapcnt6.png
50 ms
google4.png
44 ms
sv5.png
28 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
28 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
27 ms
tmapctrl.png
28 ms
cb_scout5.png
30 ms
tmapctrl4.png
28 ms
imgs8.png
29 ms
spotlight-poi.png
30 ms
vt
54 ms
vt
57 ms
vt
54 ms
vt
55 ms
vt
58 ms
vt
58 ms
vt
56 ms
AuthenticationService.Authenticate
161 ms
eor.fr 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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
eor.fr 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
eor.fr 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eor.fr 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 Eor.fr 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.
eor.fr
Open Graph data is detected on the main page of EOR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: