4.5 sec in total
360 ms
2.1 sec
2.1 sec
Click here to check amazing Igr content for France. Otherwise, check out these important facts you probably never knew about igr.fr
Premier centre de lutte contre le cancer en Europe, Gustave Roussy place l’innovation au cœur des soins et de la recherche contre le cancer, au bénéfice des patients.
Visit igr.frWe analyzed Igr.fr page load time and found that the first response time was 360 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
igr.fr performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value9.3 s
1/100
25%
Value5.2 s
60/100
10%
Value720 ms
41/100
30%
Value0.145
77/100
15%
Value10.7 s
22/100
10%
360 ms
571 ms
49 ms
164 ms
247 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Igr.fr, 72% (39 requests) were made to Gustaveroussy.fr and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (773 ms) relates to the external source Gustaveroussy.fr.
Page size can be reduced by 266.3 kB (28%)
968.4 kB
702.0 kB
In fact, the total size of Igr.fr main page is 968.4 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. 45% of websites need less resources to load. Images take 581.4 kB which makes up the majority of the site volume.
Potential reduce by 137.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 137.5 kB or 84% of the original size.
Potential reduce by 12.2 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. Igr images are well optimized though.
Potential reduce by 109.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 109.8 kB or 63% of the original size.
Potential reduce by 6.8 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. Igr.fr needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 14% of the original size.
Number of requests can be reduced by 17 (37%)
46
29
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Igr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
igr.fr
360 ms
www.gustaveroussy.fr
571 ms
uc.js
49 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
164 ms
css_roRmulWqOEzVoUDgy4oISXY895qe2RJklYkEtTeAGT8.css
247 ms
css_zki1KszIyYd4ZTSxEHtEASCXtvd9cSZwplnwX0UrJN0.css
248 ms
css_Qn6EwKn9HgPUsWdFwnCDPEgUbv-9I3zQD5mwAg55NmI.css
334 ms
andre.css
340 ms
robin.css
265 ms
sergi.css
329 ms
jquery-1.8.3.min.js
31 ms
js_Hfha9RCTNm8mqMDLXriIsKGMaghzs4ZaqJPLj2esi7s.js
413 ms
js_2Wwdq3N-PLJf7bGdciu1mlV4OoB9-npkNMcxNveqmkw.js
348 ms
js_twCC1SNvhVOqeQdjii7nFvRYBHlM0jQX-EvgUNqNQcM.js
536 ms
andre.js
444 ms
css
34 ms
theme.css
418 ms
configuration.js
180 ms
cc.js
98 ms
logo.png
422 ms
homevid-fallback.jpg
634 ms
loupe.png
424 ms
actu-urgences-0622.jpg
424 ms
hp-actu-band-rh.jpg
633 ms
hp-actu-band-covid.jpg
621 ms
hp-actu-postasco22.jpg
633 ms
hp-temoin-band-01.jpg
622 ms
hp-temoin-band-02.jpg
642 ms
hp-temoin-band-03.jpg
635 ms
hp-temoin-s-bazin.jpg
643 ms
bc-v4.min.html
383 ms
css
13 ms
menumobile-left.png
447 ms
menumobile-right.png
447 ms
magnifier.png
447 ms
loupe-big.png
447 ms
male-user.png
447 ms
picto-don-coeur.png
449 ms
picto-social2.png
447 ms
current-tab-nav.png
448 ms
sep-nav-table.png
449 ms
picto-right-link.png
449 ms
hp-temoins-bg.png
499 ms
trait-after.png
500 ms
gutave_roussy.jpg
773 ms
picto-bottom-link.png
525 ms
backup.png
525 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
194 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
205 ms
,
126 ms
jquery-1.8.3.min.js
5 ms
igr.fr accessibility score
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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.
igr.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
igr.fr SEO score
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 Igr.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 Igr.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.
igr.fr
Open Graph data is detected on the main page of Igr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: