7 sec in total
332 ms
4.8 sec
1.9 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 332 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eor.fr performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.4 s
0/100
25%
Value9.6 s
11/100
10%
Value6,920 ms
0/100
30%
Value0.259
47/100
15%
Value23.1 s
1/100
10%
332 ms
487 ms
230 ms
242 ms
392 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 66% of them (50 requests) were addressed to the original Eor.fr, 18% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Cdn.trustindex.io. The less responsive or slowest element that took the longest time to load (765 ms) belongs to the original domain Eor.fr.
Page size can be reduced by 213.0 kB (38%)
559.8 kB
346.7 kB
In fact, the total size of Eor.fr main page is 559.8 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. 70% of websites need less resources to load. Images take 274.2 kB which makes up the majority of the site volume.
Potential reduce by 211.5 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 211.5 kB or 83% of the original size.
Potential reduce by 1.4 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 189 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 48 (84%)
57
9
The browser has sent 57 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 38 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
eor.fr
332 ms
www.eor.fr
487 ms
thegem__js__thegem-pagespeed-lazy-items-js-v36e330273a945a65eec60e2acb498911072c3989.js
230 ms
fwweg.css
242 ms
fwweg.css
392 ms
css
45 ms
fwweg.css
418 ms
fwweg.css
483 ms
fwwef.css
427 ms
fwwef.css
429 ms
css
41 ms
fwwef.css
334 ms
jquery.min.js
515 ms
jquery-migrate.min.js
466 ms
vue.min.js
73 ms
simulateur-diff-wp__js__chunk-vendors-js-v6d5c724de4f5eb3dd617fbc60ec56b39e346216f.js
643 ms
js
79 ms
mailin__js__mailin-front-js-v618a0aef1e39486d4c101b19a7def4ee542a4024.js
512 ms
platform.js
40 ms
vue.min.js
19 ms
fwwef.css
370 ms
thegem__js__thegem-form-elements-js-v684d536677d240e56f49e35d7f3b9ab87d60d24c.js
400 ms
thegem__js__jquery-easing-js-v8a0af32d76631fc2cab42417a7064791864bde85.js
415 ms
thegem__js__thegem-menu_init-js-v5f2ff1af200418d9749ebd3d9bfdbbdc6d33d76e.js
431 ms
thegem__js__thegem-header-js-v649306fdc02c294114b7f00ef805321a65d5e05d.js
441 ms
thegem__js__functions-js-v64728906b906834f60ac7315b96b11eb244436e2.js
441 ms
thegem__js__fancybox__jquery-mousewheel-pack-js-v90b720b3183ee6751189e37ad84de80f28de41bf.js
475 ms
jquery.fancybox.min.js
578 ms
thegem__js__fancybox__jquery-fancybox-init-js-v4cbd9f4156beefc2b4155da4170b656b2a0e7023.js
579 ms
index.js
580 ms
index.js
579 ms
simulateur-diff-wp__js__app-js-v52f75a8c34f42321fbee090bcd3db6bb1506f53c.js
761 ms
wpcf7-redirect__build__js__wpcf7r-fe-js-v2085b4cd0d48a77485400905b5c9e0a88eb6e476.js
761 ms
thegem-elements__inc__gdpr__assets__js__public-js-vc041767573db3880e51dcec0fe22f36dbc66546c.js
760 ms
api.js
40 ms
wp-polyfill-inert.min.js
761 ms
regenerator-runtime.min.js
762 ms
wp-polyfill.min.js
761 ms
index.js
762 ms
js_composer_front.min.js
764 ms
thegem__js__thegem-lazyloading-js-v4568d5730cac3c80123945ae558089b5721017b3.js
762 ms
thegem__js__quickfinders-effects-js-va39cc3cc5c9876e97e76605a44572beed2d9f165.js
763 ms
loader.js
27 ms
vc-waypoints.min.js
764 ms
thegem__js__thegem-portfolio-grid-extended-js-v382cb96c038301531cd38a43d48490cf247a6099.js
764 ms
thegem__js__owl__owl-carousel-js-vf5576fe51d0c75532df1a0d1286c86bf9a9157c3.js
765 ms
thegem__js__thegem-portfolio-carousel-js-v4d234e552778dc134c1b826d56f6e91e40aa5769.js
691 ms
thegem__js__thegem-scrollmonitor-js-v1cc632f501adc2bed67ec7456920b8d13fd4a025.js
680 ms
thegem__js__thegem-itemsanimations-js-vac38b9256b289e26df3a79cb3ac38ed02bccffcb.js
580 ms
sa.js
465 ms
gtm.js
254 ms
logo_c9b5ba4e62880b6bc4f93b0fbab3e9fd_1x.png
332 ms
logo_11c096b9d096e5913c8b6b32f8c9e8ba_1x.png
456 ms
background-landing-eor-1-1024x576.jpg
445 ms
12-10.jpg
318 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
137 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
278 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
278 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
282 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
281 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
283 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
281 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
279 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
278 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
379 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
384 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
387 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
386 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
384 ms
thegem-icons.woff
274 ms
preloader-1.gif
554 ms
icon.svg
74 ms
f.svg
95 ms
thegem-socials.woff
88 ms
icons-material.css
142 ms
icons-elegant.css
147 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
Form elements do not have associated labels
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.
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: