4.7 sec in total
187 ms
4 sec
546 ms
Visit sum.fr now to see the best up-to-date Sum content for France and also check out these interesting facts you probably never knew about sum.fr
Guide d'achat high-tech, développement, e-commerce et mobilité par Guillaume & friends sur Bloggito Ergo Sum, le blog de l'an 2000.
Visit sum.frWe analyzed Sum.fr page load time and found that the first response time was 187 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sum.fr performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value7.5 s
4/100
25%
Value8.8 s
16/100
10%
Value10,430 ms
0/100
30%
Value0.04
99/100
15%
Value17.0 s
4/100
10%
187 ms
2235 ms
162 ms
248 ms
276 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 68% of them (54 requests) were addressed to the original Sum.fr, 18% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Sum.fr.
Page size can be reduced by 756.2 kB (33%)
2.3 MB
1.5 MB
In fact, the total size of Sum.fr main page is 2.3 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 69.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. 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 69.6 kB or 84% of the original size.
Potential reduce by 3.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. Sum images are well optimized though.
Potential reduce by 324.6 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 324.6 kB or 66% of the original size.
Potential reduce by 358.2 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. Sum.fr needs all CSS files to be minified and compressed as it can save up to 358.2 kB or 83% of the original size.
Number of requests can be reduced by 32 (51%)
63
31
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
sum.fr
187 ms
sum.fr
2235 ms
wp-emoji-release.min.js
162 ms
widget.css
248 ms
font-awesome.min.css
276 ms
simple-line-icons.css
273 ms
style.css
271 ms
style.css
353 ms
responsive.css
267 ms
style.css
333 ms
style.css
359 ms
style.css
359 ms
style.css
360 ms
style.css
361 ms
jquery.js
513 ms
jquery-migrate.min.js
439 ms
main.js
440 ms
css
67 ms
css
81 ms
skrollr.js
528 ms
jquery.fitvids.js
370 ms
jquery-scrolltofixed-min.js
371 ms
waypoints.min.js
525 ms
jquery.flexslider-min.js
525 ms
jquery.magnific-popup.min.js
525 ms
matchMedia.js
524 ms
matchMedia.addListener.js
552 ms
custom.js
552 ms
wp-embed.min.js
552 ms
count.js
551 ms
analytics.js
96 ms
f212b683a039258784473f93ac8d58ec
773 ms
main_bg.png
353 ms
indispensable-2016-650x454.jpg
351 ms
icon_sprite.png
352 ms
traduire-wordpress-po-mo-704x454.jpg
554 ms
faire-des-economies.jpg
352 ms
je-veux-mon-cafe-nespresso-704x400.jpg
440 ms
j-aime-pas-facebook-704x454.jpg
554 ms
loading.gif
479 ms
IMG_0228-704x454.jpg
782 ms
IMG_0229-704x454.jpg
784 ms
IMG_0231-704x454.jpg
641 ms
IMG_0232-704x454.jpg
726 ms
IMG_0236-704x454.jpg
812 ms
IMG_0238-704x454.jpg
813 ms
IMG_0228-150x150.jpg
730 ms
IMG_0229-150x150.jpg
812 ms
IMG_0231-150x150.jpg
816 ms
IMG_0232-150x150.jpg
867 ms
IMG_0236-150x150.jpg
868 ms
IMG_0238-150x150.jpg
896 ms
simple-smile.png
897 ms
paiement-cb-internet-704x275.jpg
983 ms
billets-euro-704x405.jpg
987 ms
romano.jpg
1037 ms
93346bc8bca8d21e619da63a8f67c81e
518 ms
twitter_ico.png
907 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
316 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
368 ms
MTP_ySUJH_bn48VBG8sNShsxEYwM7FgeyaSgU71cLG0.woff
384 ms
k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff
385 ms
EInbV5DfGHOiMmvb1Xr-hhsxEYwM7FgeyaSgU71cLG0.woff
385 ms
UQsuzNW4csFAjwcBb7-0yg.woff
423 ms
kyZw18tqQ5if-_wpmxxOeD8E0i7KZn-EPnyo3HZu7kw.woff
422 ms
GJwjUwFhmPlcBRsWC9zdGPesZW2xOQ-xsNqO47m55DA.woff
421 ms
PRmiXeptR36kaC0GEAetxv25ds880Du_gFZbUlZlsbg.woff
422 ms
O4NhV7_qs9r9seTo7fnsVD8E0i7KZn-EPnyo3HZu7kw.woff
423 ms
PRmiXeptR36kaC0GEAetxpXMLUeV6_io0G3F6eXSVcg.woff
424 ms
PRmiXeptR36kaC0GEAetxjZJchHK-lPtiIaM3GRtbZU.woff
423 ms
fontawesome-webfont.woff
1015 ms
9DvVT9Q9vsI
128 ms
collect
37 ms
www-embed-player-vflfNyN_r.css
103 ms
www-embed-player.js
115 ms
base.js
133 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
33 ms
ad_status.js
39 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
24 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
sum.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
sum.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
sum.fr SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sum.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 Sum.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.
sum.fr
Open Graph data is detected on the main page of Sum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: