1.4 sec in total
166 ms
1.1 sec
128 ms
Visit ifape.com now to see the best up-to-date IFAPE content and also check out these interesting facts you probably never knew about ifape.com
L’IFAPE, Organisme de Formation depuis plus de 20 ans a acquis une expérience qui lui confère, efficience et réactivité.
Visit ifape.comWe analyzed Ifape.com page load time and found that the first response time was 166 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
ifape.com performance score
166 ms
82 ms
74 ms
77 ms
78 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Ifape.com, 8% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (401 ms) belongs to the original domain Ifape.com.
Page size can be reduced by 399.2 kB (77%)
517.4 kB
118.2 kB
In fact, the total size of Ifape.com main page is 517.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. Javascripts take 322.9 kB which makes up the majority of the site volume.
Potential reduce by 12.9 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 2.1 kB, which is 12% 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 12.9 kB or 78% of the original size.
Potential reduce by 0 B
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. IFAPE images are well optimized though.
Potential reduce by 234.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 234.8 kB or 73% of the original size.
Potential reduce by 151.6 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. Ifape.com needs all CSS files to be minified and compressed as it can save up to 151.6 kB or 86% of the original size.
Number of requests can be reduced by 23 (53%)
43
20
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFAPE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ifape.com
166 ms
style.css
82 ms
red.css
74 ms
superfish.css
77 ms
prettyPhoto.css
78 ms
font-awesome.css
85 ms
audioplayer.css
85 ms
settings.css
143 ms
responsive.css
145 ms
jquery-1.8.3.min.js
186 ms
hoverIntent.js
150 ms
superfish.js
149 ms
jquery.jcarousel.js
149 ms
jquery.tweet.js
215 ms
jflickrfeed.js
216 ms
jquery.prettyPhoto.js
219 ms
slides.min.jquery.js
217 ms
jquery.mobilemenu.js
220 ms
jquery.contact.js
257 ms
jquery.preloadify.min.js
287 ms
jquery.jplayer.min.js
290 ms
jquery.isotope.min.js
294 ms
jquery.themepunch.plugins.min.js
300 ms
jquery.themepunch.revolution.min.js
304 ms
custom.js
329 ms
css
27 ms
fond_header.png
76 ms
logo.png
110 ms
nav-bg.png
76 ms
shadow.png
76 ms
top-shadow.png
77 ms
slide9.jpg
255 ms
slide2.jpg
291 ms
slide3.jpg
291 ms
slide1.jpg
401 ms
slide6.jpg
220 ms
layer1.png
217 ms
layer2.png
364 ms
bottom-shadow.png
292 ms
pc_bleue.png
327 ms
dark-logo.png
362 ms
loader.gif
365 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
13 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
12 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
13 ms
slider-left-arrow.png
74 ms
slider-right-arrow.png
75 ms
ifape.com SEO score
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifape.com 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 Ifape.com 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.
ifape.com
Open Graph description is not detected on the main page of IFAPE. 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: