2.2 sec in total
157 ms
1.7 sec
322 ms
Visit germany.worldcupblog.org now to see the best up-to-date Germany World Cup Blog content and also check out these interesting facts you probably never knew about germany.worldcupblog.org
Read the latest news on Germany Soccer and World Cup South Africa 2010
Visit germany.worldcupblog.orgWe analyzed Germany.worldcupblog.org page load time and found that the first response time was 157 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
germany.worldcupblog.org performance score
157 ms
72 ms
86 ms
103 ms
78 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Germany.worldcupblog.org, 86% (85 requests) were made to Cdn.worldcupblog.org and 3% (3 requests) were made to Cdn.bootsnall.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cdn.worldcupblog.org.
Page size can be reduced by 241.3 kB (70%)
344.5 kB
103.2 kB
In fact, the total size of Germany.worldcupblog.org main page is 344.5 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. 15% of websites need less resources to load. Javascripts take 227.1 kB which makes up the majority of the site volume.
Potential reduce by 69.0 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 10.5 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 69.0 kB or 83% of the original size.
Potential reduce by 1.2 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. Germany 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. Germany.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 81 (83%)
98
17
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Germany 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.
germany.worldcupblog.org
157 ms
style.css
72 ms
prototype.js
86 ms
ajax.js
103 ms
utility.js
78 ms
jquery-1.4.min.js
80 ms
jquery.opTips.js
107 ms
urchin.js
17 ms
ic_hamburg.jpg
106 ms
sbn.png
109 ms
logo_1316848a.jpg
38 ms
facebook.png
87 ms
logo.gif
179 ms
small_albania.gif
178 ms
small_austria.gif
177 ms
small_belgium.gif
35 ms
small_bosnia.gif
179 ms
small_croatia.gif
185 ms
small_czechrepublic.gif
203 ms
small_denmark.gif
371 ms
small_england.gif
200 ms
small_france.gif
196 ms
small_germany.gif
372 ms
small_greece.gif
374 ms
small_ireland.gif
208 ms
small_israel.gif
406 ms
small_italy.gif
224 ms
small_netherlands.gif
229 ms
small_norway.gif
329 ms
small_poland.gif
247 ms
small_portugal.gif
424 ms
small_romania.gif
515 ms
small_russia.gif
391 ms
small_scotland.gif
548 ms
small_serbia.gif
674 ms
small_slovakia.gif
579 ms
small_slovenia.gif
572 ms
small_spain.gif
599 ms
small_sweden.gif
690 ms
small_switzerland.gif
835 ms
small_turkey.gif
819 ms
small_ukraine.gif
836 ms
small_wales.gif
847 ms
dot.gif
800 ms
dot.gif
706 ms
arrow1.gif
750 ms
down_arrow.gif
781 ms
twitter.png
97 ms
rss.png
68 ms
arrow4.gif
953 ms
end.gif
1017 ms
__utm.gif
29 ms
quant.js
27 ms
beacon.js
27 ms
count.js
61 ms
pixel;r=763880910;a=p-d9vfr8QTWnv1E;fpan=1;fpa=P0-1585903698-1458252622425;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458252622425;tzo=-180;ref=;url=http%3A%2F%2Fgermany.worldcupblog.org%2F;ogl=
6 ms
count-data.js
125 ms
large_germany.gif
826 ms
comments.gif
681 ms
rss-12x12.gif
1004 ms
rss_home.jpg
723 ms
read_more.gif
709 ms
article_flag_france.gif
736 ms
article_flag_croatia.gif
755 ms
article_flag_czechrepublic.gif
767 ms
article_flag_england.gif
769 ms
article_flag_germany.gif
851 ms
article_flag_italy.gif
789 ms
article_flag_netherlands.gif
777 ms
article_flag_poland.gif
705 ms
article_flag_portugal.gif
750 ms
article_flag_serbia.gif
727 ms
article_flag_spain.gif
691 ms
article_flag_sweden.gif
705 ms
article_flag_switzerland.gif
699 ms
article_flag_ukraine.gif
679 ms
article_flag_greece.gif
608 ms
article_flag_russia.gif
598 ms
article_flag_scotland.gif
580 ms
article_flag_ireland.gif
574 ms
article_flag_norway.gif
566 ms
article_flag_turkey.gif
508 ms
article_flag_romania.gif
494 ms
article_flag_austria.gif
476 ms
article_flag_denmark.gif
430 ms
article_flag_albania.gif
416 ms
article_flag_belgium.gif
412 ms
article_flag_wales.gif
416 ms
article_flag_bosnia.gif
385 ms
article_flag_israel.gif
451 ms
article_flag_slovakia.gif
389 ms
article_flag_slovenia.gif
394 ms
closer_bottom.gif
592 ms
common_gif.gif
325 ms
bgr_germany.gif
335 ms
bgr_main_hp.gif
286 ms
vertical_dot.gif
284 ms
common_head.gif
276 ms
ic_comment.gif
291 ms
germany.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 Germany.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 Germany.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.
germany.worldcupblog.org
Open Graph description is not detected on the main page of Germany 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: