8.9 sec in total
713 ms
7.8 sec
386 ms
Click here to check amazing Blog Edcom content for France. Otherwise, check out these important facts you probably never knew about blog.edcom.fr
Avec Edcom.fr, comparez tous les forfaits de téléphone mobile, les box Internet et les derniers smartphones en un clic ! Faîtes des économies en profitant des promotions et bons plans des opérateurs
Visit blog.edcom.frWe analyzed Blog.edcom.fr page load time and found that the first response time was 713 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
blog.edcom.fr performance score
713 ms
175 ms
177 ms
371 ms
193 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 48% of them (65 requests) were addressed to the original Blog.edcom.fr, 14% (19 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Blog.edcom.fr.
Page size can be reduced by 481.7 kB (27%)
1.8 MB
1.3 MB
In fact, the total size of Blog.edcom.fr main page is 1.8 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. 75% 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 37.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 6.1 kB, which is 13% 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 37.9 kB or 79% of the original size.
Potential reduce by 87.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. Blog Edcom images are well optimized though.
Potential reduce by 236.0 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 236.0 kB or 69% of the original size.
Potential reduce by 120.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. Blog.edcom.fr needs all CSS files to be minified and compressed as it can save up to 120.4 kB or 86% of the original size.
Number of requests can be reduced by 62 (51%)
122
60
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Edcom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
blog.edcom.fr
713 ms
pagenavi-css.css
175 ms
style.css
177 ms
style.css
371 ms
blue.css
193 ms
jquery.min.js
485 ms
jquery.flexslider.js
289 ms
jquery.selectnav.js
257 ms
jquery.twitter.js
263 ms
jquery.modernizr.js
287 ms
jquery.easing.1.3.js
344 ms
jquery.contact.js
351 ms
jquery.isotope.min.js
383 ms
jquery.jcarousel.js
383 ms
jquery.fancybox.min.js
518 ms
jquery.layerslider.min.js
529 ms
jquery.shop.js
459 ms
custom.js
479 ms
mediaelement-and-player.js
735 ms
script.js
1829 ms
base.css
211 ms
responsive.css
212 ms
icons.css
240 ms
css
24 ms
analytics.js
65 ms
background.jpg
712 ms
logo_trans.png
510 ms
facebook-icone.png
232 ms
twitter-icone.png
230 ms
gplus-32.png
230 ms
twitter.png
139 ms
facebook.png
138 ms
dribbble.png
140 ms
linkedin.png
139 ms
rss.png
139 ms
search.png
140 ms
layerslider-loader.gif
186 ms
innovation980x242.png
404 ms
applicationmobile980x242.png
668 ms
culturemobile980x242.png
506 ms
etudes980x242.png
663 ms
astucesetbonplans980x242.png
666 ms
wtf980x242.png
663 ms
infographie980x242.png
662 ms
blog-smartphone-rue.jpg
816 ms
giphy.gif
1266 ms
blog-.png
830 ms
video.jpg
841 ms
blog-.jpg
851 ms
image2.gif
1302 ms
blog-edcom-soofa.jpg
1007 ms
tatoooooo1.gif
1991 ms
image1.gif
1032 ms
DC6.jpg
1041 ms
tout-du-monde-mobile.jpg
1104 ms
blog-edcom-valeur-smartphone-etude.jpg
1128 ms
recyclage_mobile_art.jpg
1233 ms
Blackberry-blog.jpg
1207 ms
Voleur-mobile-blog.jpg
1223 ms
pub_apple_vs_samsung.jpg
1296 ms
blog-batterie.jpg
1320 ms
blog-edcom.png
1328 ms
bescherelletameire.png
1349 ms
ramzy.jpg
1391 ms
dionne-baxter.jpg
1391 ms
all.js
276 ms
telephone-vole.jpg
1384 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
92 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
95 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
97 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
98 ms
widgets.js
17 ms
collect
74 ms
platform.js
126 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
27 ms
skin.css
1547 ms
fontawesome-webfont.woff
2566 ms
syndication
111 ms
289312689682006016
240 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
39 ms
page
290 ms
postmessageRelay
47 ms
api.js
38 ms
core:rpc:shindig.random:shindig.sha1.js
82 ms
2536007149-postmessagerelay.js
141 ms
137 ms
xd_arbiter.php
249 ms
xd_arbiter.php
482 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
14 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
16 ms
rVRJGroR_normal.png
288 ms
aGEbxR5H_normal.png
221 ms
rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ
14 ms
rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA
33 ms
rs=AGLTcCMMb57M3RONAMBCFtW9UevF0hnP2A
84 ms
photo.jpg
161 ms
image-google%252B.jpg
202 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
171 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
191 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
228 ms
rs=AGLTcCMMb57M3RONAMBCFtW9UevF0hnP2A
30 ms
rs=AGLTcCMMb57M3RONAMBCFtW9UevF0hnP2A
17 ms
jot
26 ms
slider-left.png
91 ms
slider-right.png
98 ms
ping
34 ms
fontawesome-webfont.ttf
348 ms
like_box.php
185 ms
C-D3sjGKj3j.css
281 ms
zEMlMNmIXUJ.css
349 ms
Czh0gDTFcBt.css
419 ms
b4M-RzS5nZj.css
548 ms
eOBdiRfK3u5.css
555 ms
_rx8naC75Dy.js
616 ms
5G7NsSyki-I.js
638 ms
0wM5s1Khldu.js
487 ms
TTCre3391I0.js
485 ms
njO1TPvGzoR.js
550 ms
b_6HNn_J2BZ.js
569 ms
6kb4qPGfoPa.js
678 ms
ezSeJz80WmZ.js
819 ms
fontawesome-webfont.svg
355 ms
12541077_1075777919120322_8019664358178205202_n.png
403 ms
safe_image.php
1090 ms
safe_image.php
1187 ms
safe_image.php
1316 ms
safe_image.php
1310 ms
safe_image.php
1339 ms
1908168_930173223680793_7374556278052744433_n.jpg
458 ms
wL6VQj7Ab77.png
88 ms
s7jcwEQH7Sx.png
88 ms
QDwYpIaRyfG.png
87 ms
sOQnlBB68lt.png
87 ms
I6-MnjEovm5.js
68 ms
f6T91Deal_q.js
135 ms
blog.edcom.fr SEO score
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.edcom.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 Blog.edcom.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.
blog.edcom.fr
Open Graph description is not detected on the main page of Blog Edcom. 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: