5.2 sec in total
560 ms
4 sec
636 ms
Click here to check amazing Freepresse content. Otherwise, check out these important facts you probably never knew about freepresse.com
Visit freepresse.comWe analyzed Freepresse.com page load time and found that the first response time was 560 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
freepresse.com performance score
560 ms
169 ms
70 ms
170 ms
176 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 89% of them (70 requests) were addressed to the original Freepresse.com, 6% (5 requests) were made to Cosy-design.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Freepresse.com.
Page size can be reduced by 1.2 MB (25%)
4.9 MB
3.7 MB
In fact, the total size of Freepresse.com main page is 4.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 60.1 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 7.5 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 60.1 kB or 84% of the original size.
Potential reduce by 143.5 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. Freepresse images are well optimized though.
Potential reduce by 712.3 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 712.3 kB or 77% of the original size.
Potential reduce by 317.3 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. Freepresse.com needs all CSS files to be minified and compressed as it can save up to 317.3 kB or 86% of the original size.
Number of requests can be reduced by 32 (48%)
67
35
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freepresse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.freepresse.com
560 ms
wp-emoji-release.min.js
169 ms
css
70 ms
styles.css
170 ms
rgs.css
176 ms
font-awesome.min.css
249 ms
steadysets.css
172 ms
linecon.css
178 ms
style.css
430 ms
responsive.css
379 ms
jquery.js
421 ms
jquery-migrate.min.js
861 ms
modernizr.js
864 ms
js_composer_front.css
312 ms
jquery.form.min.js
461 ms
scripts.js
460 ms
superfish.js
495 ms
easing.js
494 ms
respond.js
570 ms
swipe.min.js
564 ms
nicescroll.js
589 ms
sticky.js
586 ms
prettyPhoto.js
667 ms
jquery.flexslider-min.js
665 ms
isotope.min.js
682 ms
imagesLoaded.min.js
681 ms
carouFredSel.min.js
884 ms
appear.js
767 ms
init.js
1292 ms
blog-masonry.js
806 ms
nectar-slider.js
941 ms
comment-reply.min.js
918 ms
nectar-love.js
907 ms
js_composer_front.js
918 ms
Free-Presse.jpg
413 ms
freepresse.jpg
1056 ms
fond-Free-Presse-Titres.jpg
439 ms
loading-white-bg.gif
162 ms
Thumb-CMDELUXE.jpg
1056 ms
transparent.png
166 ms
Thumb-CMSWISS.jpg
425 ms
Thumb-VALLAT1.jpg
1054 ms
Thumb-PVG.jpg
1056 ms
PPV-Couv-Home.jpg
1056 ms
Thumb-CosyCity.jpg
1054 ms
3V2015-Thumb.jpg
1063 ms
THUMB-CosyDesign1.jpg
1060 ms
Thumb-ESCAPE1.jpg
1057 ms
CM27-Thumb.jpg
1057 ms
Thumb-By_Sibuet.jpg
1057 ms
Livre-Dynastar-50-ans-600x403.jpg
1058 ms
Thumb-STYLE1.jpg
1060 ms
THUMB-LeBonTest1.jpg
1304 ms
Thumb-FolieDouce.jpg
1217 ms
Thumb_Skilabo.jpg
1217 ms
Thumb-GSI1.jpg
1217 ms
Livre-100-ans-Rossignol-600x403.jpg
1218 ms
analytics.js
36 ms
OpenSans-Regular-webfont.woff
1180 ms
OpenSans-Regular-webfont.woff
1241 ms
OpenSans-Semibold-webfont.woff
1283 ms
OpenSans-Semibold-webfont.woff
1261 ms
OpenSans-Bold-webfont.woff
1553 ms
OpenSansBold-webfont.woff
1727 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
59 ms
fontawesome-webfont.svg
1553 ms
icomoon.woff
1553 ms
collect
11 ms
Fond-Free-presse.jpg
342 ms
Edition-d%C3%A9l%C3%A9gu%C3%A9e.jpg
722 ms
Screen-LeBonTest-Flou.jpg
719 ms
Presse_Offerte-GERVASONI.jpg
1151 ms
grid.png
719 ms
Presse_Payante-Blossom-copie.jpg
891 ms
nectar-loading.gif
890 ms
diagonal_line.png
719 ms
OpenSans-Light-webfont.woff
888 ms
OpenSans-Light-webfont.woff
887 ms
fontawesome-webfont.woff
192 ms
freepresse.com SEO score
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freepresse.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Freepresse.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.
freepresse.com
Open Graph description is not detected on the main page of Freepresse. 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: