2.7 sec in total
411 ms
2 sec
351 ms
Click here to check amazing IFR content. Otherwise, check out these important facts you probably never knew about ifr.fr
Découvrez nos formations en langues, informatique, communication, management, hygiène et sécurité, oenologie etc...
Visit ifr.frWe analyzed Ifr.fr page load time and found that the first response time was 411 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ifr.fr performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value14.9 s
0/100
25%
Value10.6 s
7/100
10%
Value2,220 ms
6/100
30%
Value0.168
71/100
15%
Value12.0 s
16/100
10%
411 ms
247 ms
333 ms
170 ms
256 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 63% of them (64 requests) were addressed to the original Ifr.fr, 12% (12 requests) were made to Maps.googleapis.com and 7% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (930 ms) belongs to the original domain Ifr.fr.
Page size can be reduced by 1.6 MB (55%)
3.0 MB
1.4 MB
In fact, the total size of Ifr.fr main page is 3.0 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. 65% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 27.6 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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 27.6 kB or 79% of the original size.
Potential reduce by 38.8 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. IFR 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 72% of the original size.
Potential reduce by 376.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. Ifr.fr needs all CSS files to be minified and compressed as it can save up to 376.8 kB or 86% of the original size.
Number of requests can be reduced by 38 (43%)
88
50
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
ifr.fr
411 ms
bootstrap.min.css
247 ms
style.css
333 ms
shop.css
170 ms
icons.css
256 ms
animate.css
259 ms
bar.css
172 ms
default.css
253 ms
dark.css
261 ms
light.css
327 ms
jquery-ui.css
413 ms
owl.carousel.css
340 ms
responsive.css
340 ms
css
32 ms
api.js
47 ms
jquery-2.0.3.js
609 ms
jquery.min.js
444 ms
jquery-ui.min.js
519 ms
bootstrap.min.js
868 ms
theme20.js
444 ms
jquery.nivo.slider.js
443 ms
jquery.prettyPhoto.js
517 ms
jquery.flexslider-min.js
546 ms
custom.js
545 ms
owl.carousel.min.js
596 ms
recaptcha__en.js
89 ms
1.jpg
927 ms
logo.png
319 ms
1.png
698 ms
new_logo.png
336 ms
CPF.png
396 ms
AGEFICE.png
408 ms
cannes_miniature.png
511 ms
afdas.jpg
615 ms
forco.jpg
619 ms
constructys.jpg
680 ms
opca3plus.jpg
681 ms
agefos.jpg
680 ms
fafih.jpg
687 ms
opcadefi.jpg
697 ms
FFP.png
698 ms
opcabaya.png
699 ms
AGEFICE.png
703 ms
logo_anfa.jpg
751 ms
intergros.jpg
749 ms
logo_fifpl.png
750 ms
opcapl.png
749 ms
logo_FAFTT_0.jpg
769 ms
opcalim.jpg
811 ms
fongecif.png
811 ms
opcalia-paca.jpg
811 ms
analytics.js
64 ms
embed
113 ms
opcaim.jpg
781 ms
pole_emploi.jpg
930 ms
republique_francaise.png
808 ms
ElegantIcons.woff
899 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
42 ms
linkid.js
33 ms
collect
13 ms
collect
80 ms
js
134 ms
init_embed.js
55 ms
fontawesome-webfont.woff
829 ms
ue.jpg
741 ms
paca_fse.jpg
790 ms
uniformation.jpg
799 ms
header.png
774 ms
UnitedKingdom.png
781 ms
Italy.png
756 ms
Germany.png
742 ms
common.js
67 ms
map.js
95 ms
google4.png
54 ms
overlay.js
227 ms
util.js
226 ms
onion.js
223 ms
search_impl.js
222 ms
StaticMapService.GetMapImage
294 ms
Spain.png
675 ms
Russia.png
683 ms
stats.js
159 ms
France.png
474 ms
ViewportInfoService.GetViewportInfo
85 ms
transparent.png
74 ms
kh
144 ms
controls.js
56 ms
vt
113 ms
vt
106 ms
vt
116 ms
vt
107 ms
vt
115 ms
css
69 ms
mapcnt6.png
25 ms
sv5.png
31 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
30 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
36 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
43 ms
AuthenticationService.Authenticate
36 ms
style_print.css
96 ms
ifr.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
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ifr.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ifr.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
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifr.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Ifr.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.
ifr.fr
Open Graph description is not detected on the main page of IFR. 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: