1.3 sec in total
165 ms
605 ms
544 ms
Welcome to australia.worldcupblog.org homepage info - get ready to check Australia World Cup Blog best content right away, or after learning these important things about australia.worldcupblog.org
Read the latest news on Australia Soccer and World Cup South Africa 2010
Visit australia.worldcupblog.orgWe analyzed Australia.worldcupblog.org page load time and found that the first response time was 165 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
australia.worldcupblog.org performance score
165 ms
22 ms
32 ms
20 ms
20 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Australia.worldcupblog.org, 66% (45 requests) were made to Cdn.worldcupblog.org and 4% (3 requests) were made to Cdn.theoffside.com. The less responsive or slowest element that took the longest time to load (434 ms) relates to the external source Cdn.worldcupblog.org.
Page size can be reduced by 579.7 kB (67%)
867.2 kB
287.5 kB
In fact, the total size of Australia.worldcupblog.org main page is 867.2 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. 35% of websites need less resources to load. Javascripts take 446.9 kB which makes up the majority of the site volume.
Potential reduce by 55.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 8.4 kB, which is 12% 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 55.9 kB or 80% of the original size.
Potential reduce by 1.3 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. Australia World Cup Blog images are well optimized though.
Potential reduce by 308.4 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 308.4 kB or 69% of the original size.
Potential reduce by 214.1 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. Australia.worldcupblog.org needs all CSS files to be minified and compressed as it can save up to 214.1 kB or 83% of the original size.
Number of requests can be reduced by 39 (64%)
61
22
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Australia 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 13 to 1 for JavaScripts and as a result speed up the page load time.
australia.worldcupblog.org
165 ms
style.css
22 ms
prototype.js
32 ms
ajax.js
20 ms
utility.js
20 ms
jquery-1.4.min.js
31 ms
jquery.opTips.js
29 ms
ic_heart.jpg
271 ms
sbn.png
161 ms
logo_1316848a.jpg
36 ms
logo.gif
17 ms
small_australia.gif
313 ms
small_china.gif
184 ms
small_india.gif
34 ms
small_iran.gif
210 ms
small_japan.gif
209 ms
small_northkorea.gif
239 ms
small_saudiarabia.gif
218 ms
small_southkorea.gif
383 ms
dot.gif
210 ms
dot.gif
210 ms
arrow1.gif
214 ms
down_arrow.gif
213 ms
arrow4.gif
216 ms
end.gif
225 ms
large_australia.gif
384 ms
comments.gif
230 ms
cahill_germany_wideweb__470x3040.jpg
365 ms
rss-12x12.gif
242 ms
rss_home.jpg
242 ms
read_more.gif
244 ms
article_flag_japan.gif
255 ms
article_flag_australia.gif
297 ms
ic_mariners.jpg
146 ms
ic_melbourne.jpg
225 ms
facebook.png
228 ms
urchin.js
15 ms
article_flag_iran.gif
297 ms
article_flag_saudiarabia.gif
356 ms
article_flag_southkorea.gif
357 ms
article_flag_china.gif
434 ms
article_flag_northkorea.gif
364 ms
article_flag_india.gif
352 ms
closer_bottom.gif
356 ms
twitter.png
145 ms
rss.png
142 ms
small_india.gif
315 ms
common_gif.gif
316 ms
bgr_australia.gif
324 ms
bgr_main_hp.gif
316 ms
vertical_dot.gif
315 ms
common_head.gif
319 ms
storeTitle.jpg
319 ms
buy.jpg
319 ms
count.js
179 ms
SH1jrTHEHI8
149 ms
__utm.gif
61 ms
quant.js
71 ms
beacon.js
71 ms
pixel;r=1946663502;a=p-d9vfr8QTWnv1E;fpan=1;fpa=P0-844753307-1458507276670;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458507276669;tzo=-180;ref=;url=http%3A%2F%2Faustralia.worldcupblog.org%2F;ogl=
8 ms
ic_comment.gif
212 ms
www-embed-player-vflfNyN_r.css
67 ms
www-embed-player.js
88 ms
count-data.js
135 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
41 ms
ad_status.js
72 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
51 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
53 ms
australia.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 Australia.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 Australia.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.
australia.worldcupblog.org
Open Graph description is not detected on the main page of Australia 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: