1.7 sec in total
159 ms
1.2 sec
315 ms
Visit mexico.worldcupblog.org now to see the best up-to-date Mexico World Cup Blog content and also check out these interesting facts you probably never knew about mexico.worldcupblog.org
Read the latest news on Mexico Soccer and World Cup South Africa 2010
Visit mexico.worldcupblog.orgWe analyzed Mexico.worldcupblog.org page load time and found that the first response time was 159 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
mexico.worldcupblog.org performance score
159 ms
20 ms
28 ms
42 ms
53 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mexico.worldcupblog.org, 75% (44 requests) were made to Cdn.worldcupblog.org and 5% (3 requests) were made to Cdn.bootsnall.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.worldcupblog.org.
Page size can be reduced by 230.0 kB (57%)
407.0 kB
176.9 kB
In fact, the total size of Mexico.worldcupblog.org main page is 407.0 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. 20% of websites need less resources to load. Javascripts take 227.1 kB which makes up the majority of the site volume.
Potential reduce by 56.4 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 8.9 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 56.4 kB or 81% of the original size.
Potential reduce by 2.6 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. Mexico World Cup Blog images are well optimized though.
Potential reduce by 159.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 159.6 kB or 70% of the original size.
Potential reduce by 11.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. Mexico.worldcupblog.org needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 78% of the original size.
Number of requests can be reduced by 39 (68%)
57
18
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mexico World Cup Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
mexico.worldcupblog.org
159 ms
style.css
20 ms
prototype.js
28 ms
ajax.js
42 ms
utility.js
53 ms
jquery-1.4.min.js
24 ms
jquery.opTips.js
43 ms
628x471.jpg
169 ms
ic_www.jpg
93 ms
sbn.png
91 ms
logo_1316848a.jpg
54 ms
logo.gif
179 ms
small_canada.gif
229 ms
small_costarica.gif
18 ms
small_honduras.gif
187 ms
small_mexico.gif
174 ms
small_panama.gif
174 ms
small_trinidadtobago.gif
301 ms
small_usa.gif
188 ms
dot.gif
192 ms
dot.gif
192 ms
arrow1.gif
225 ms
down_arrow.gif
197 ms
arrow4.gif
424 ms
end.gif
475 ms
large_mexico.gif
449 ms
comments.gif
311 ms
mexflg.jpg
280 ms
europe_map1-120x120.jpg
320 ms
Qbo-120x120.png
1061 ms
rss-12x12.gif
471 ms
rss_home.jpg
359 ms
read_more.gif
386 ms
article_flag_usa.gif
529 ms
article_flag_costarica.gif
449 ms
article_flag_mexico.gif
519 ms
article_flag_trinidadtobago.gif
535 ms
article_flag_canada.gif
505 ms
article_flag_panama.gif
510 ms
article_flag_honduras.gif
547 ms
facebook.png
80 ms
urchin.js
4 ms
closer_bottom.gif
678 ms
twitter.png
81 ms
rss.png
45 ms
common_gif.gif
756 ms
bgr_mexico.gif
675 ms
bgr_main_hp.gif
534 ms
vertical_dot.gif
521 ms
common_head.gif
550 ms
storeTitle.jpg
580 ms
buy.jpg
588 ms
__utm.gif
27 ms
quant.js
27 ms
beacon.js
27 ms
count.js
46 ms
pixel;r=1132673217;a=p-d9vfr8QTWnv1E;fpan=1;fpa=P0-1778773726-1458816516580;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458816516580;tzo=-180;ref=;url=http%3A%2F%2Fmexico.worldcupblog.org%2F;ogl=
16 ms
count-data.js
83 ms
ic_comment.gif
477 ms
mexico.worldcupblog.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mexico.worldcupblog.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mexico.worldcupblog.org 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.
mexico.worldcupblog.org
Open Graph description is not detected on the main page of Mexico World Cup Blog. 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: