3.8 sec in total
116 ms
3.4 sec
269 ms
Visit eidos.fr now to see the best up-to-date Eidos content and also check out these interesting facts you probably never knew about eidos.fr
We are the developers of Deus Ex, Marvel's Guardians of the Galaxy, Shadow of the Tomb Raider and more. Whether you are looking for our latest creations or a job in the games industry, you'v...
Visit eidos.frWe analyzed Eidos.fr page load time and found that the first response time was 116 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eidos.fr performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value20.5 s
0/100
25%
Value32.6 s
0/100
10%
Value86,550 ms
0/100
30%
Value0.064
97/100
15%
Value131.8 s
0/100
10%
116 ms
451 ms
437 ms
61 ms
78 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eidos.fr, 64% (64 requests) were made to Eu.square-enix.com and 3% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Eu.square-enix.com.
Page size can be reduced by 709.8 kB (17%)
4.2 MB
3.5 MB
In fact, the total size of Eidos.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. 60% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.3 kB or 73% of the original size.
Potential reduce by 287.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. Eidos images are well optimized though.
Potential reduce by 262.6 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 262.6 kB or 68% of the original size.
Potential reduce by 119.4 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. Eidos.fr needs all CSS files to be minified and compressed as it can save up to 119.4 kB or 86% of the original size.
Number of requests can be reduced by 53 (58%)
92
39
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eidos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
eidos.fr
116 ms
login
451 ms
en
437 ms
css
61 ms
madmin_42.css
78 ms
madmin_message.css
153 ms
home.css
155 ms
jqcarousel_corporate.css
156 ms
blogcarousel.css
155 ms
mainmenu.mobile.css
242 ms
system.css
308 ms
normalize.css
309 ms
responsive-sidebars.css
243 ms
pages.css
305 ms
blocks.css
322 ms
navigation.css
322 ms
node.css
378 ms
comments.css
382 ms
forms.css
380 ms
membership-bar.css
383 ms
footer.css
402 ms
common.css
400 ms
mainmenu.css
454 ms
typography.css
454 ms
shame.css
456 ms
jquery.min.js
700 ms
drupal.js
482 ms
en_GB_7a2e9f8f4e5a7279b00681eafeb440c9.js
481 ms
jquery.responsiveslides.min.js
529 ms
jqcarousel_corporate.js
529 ms
jquery.elastislide.min.js
533 ms
blogcarousel.js
561 ms
mainmenu.js
562 ms
jquery.drupalsearch.js
603 ms
first-word.js
603 ms
membership_bar.js
84 ms
buttons.js
23 ms
jquery.comments.length.js
606 ms
script.js
577 ms
square_logo.png
365 ms
icons-s2a6bf2cf3b.png
177 ms
ab696275b03d5fc57a24f003fc071c4f.jpg
415 ms
c6db76da4cd9593715aa6660f6d6a8e1.jpg
809 ms
ffce8b241018e4fd512b7d6339062a27.jpg
708 ms
46ecd8bb8302bef0dcb262a3f560bc50.jpg
645 ms
ca75a8dd3fa1d7b523b861a276e25add.jpg
699 ms
ff857cef87e46441e0c663daf552a536.jpg
805 ms
26cf4e1dc77207d2f662f479c0908ee7.jpg
778 ms
e2c39f250e875982cf3ea2a61e55acba.jpg
946 ms
05f267be0c246695dba08506944f1679.jpg
1006 ms
line.png
783 ms
e69df3c1249f614d997d680e544d6031.jpg
862 ms
71d4194fd2d6b07a9ceedb7af02eabe7.png
863 ms
80535980689416d8d17f9b2c66d36dc2.jpg
883 ms
907a12d3bf98d7f01e6eac30ba83a267.png
889 ms
b89f3193bf551507de8a645c4ac22243.gif
943 ms
a2753a58b6cff325140a652b900d9c53.jpg
940 ms
0c37c7538e44bd8f75952e2c49bf852b.png
1033 ms
5873585807dc81578099777fe9dff3ca.png
970 ms
f63ec9b8524a59b2d4c54d3e42618b51.png
1093 ms
4c052894af0dca4cd6a1fe6b31049211.png
1088 ms
avatar.png
1023 ms
facebook.jpg
1051 ms
twitter.jpg
1076 ms
youtube.jpg
1103 ms
rss.png
1108 ms
flags_small.png
1137 ms
all.js
190 ms
widgets.js
145 ms
ga.js
94 ms
getAllAppDefault.esi
37 ms
arrow_left.png
1022 ms
arrow_right.png
1032 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
46 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
69 ms
__utm.gif
44 ms
getSegment.php
174 ms
checkOAuth.esi
28 ms
140 ms
xd_arbiter.php
149 ms
xd_arbiter.php
286 ms
t.dhj
9 ms
pixel
28 ms
t.dhj
11 ms
cm
50 ms
pixel
30 ms
s-3271.xgi
14 ms
adxmapping.php
76 ms
hbpix
48 ms
19 ms
29 ms
xrefid.xgi
23 ms
pixel
16 ms
2981
35 ms
nr-885.min.js
34 ms
ping
80 ms
ffc36bd837
49 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
31 ms
buttons.ab966a004186897711de4a5ed256c924.css
22 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
5 ms
eidos.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
eidos.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
Missing source maps for large first-party JavaScript
eidos.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eidos.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eidos.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.
eidos.fr
Open Graph description is not detected on the main page of Eidos. 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: