Analyze Netherlands World Cup Blog

Read the latest news on Netherlands Soccer and World Cup South Africa 2010

Page load speed analysis

  • 71/100

    Good result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    191 ms

  • Resources loaded

    848 ms

  • Page rendered

    579 ms

  • Total page load time

    1.6 sec

Welcome to homepage info - get ready to check Netherlands World Cup Blog best content right away, or after learning these important things about

We analyzed page load time and found that the first response time was 191 ms and then it took 1.4 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.

Page optimization

  • HTML 93.2 kB
    Images 126.8 kB
    Javascripts 239.5 kB
    CSS 14.7 kB

    In fact, the total size of main page is 474.3 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. 25% of websites need less resources to load. Javascripts take 239.5 kB which makes up the majority of the site volume.

    • Original 93.2 kB
    • After minification 80.3 kB
    • After compression 16.0 kB

    HTML optimization

    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 12.9 kB, which is 14% 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 77.2 kB or 83% of the original size.

    • Original 126.8 kB
    • After optimization 122.8 kB

    Image optimization

    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. Netherlands World Cup Blog images are well optimized though.

    • Original 239.5 kB
    • After minification 198.9 kB
    • After compression 59.1 kB

    JavaScript optimization

    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 180.4 kB or 75% of the original size.

    • Original 14.7 kB
    • After minification 13.1 kB
    • After compression 3.3 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 78% of the original size.

Network requests diagram

  • style.css
  • prototype.js
  • ajax.js
  • utility.js
  • jquery-1.4.min.js
  • jquery.opTips.js
  • logo.gif
  • small_albania.gif
  • small_austria.gif
  • small_belgium.gif
  • small_bosnia.gif
  • small_croatia.gif
  • small_czechrepublic.gif
  • small_denmark.gif
  • small_england.gif
  • small_france.gif
  • small_germany.gif
  • small_greece.gif
  • small_ireland.gif
  • small_israel.gif
  • small_italy.gif
  • small_netherlands.gif
  • small_norway.gif
  • small_poland.gif
  • small_portugal.gif
  • small_romania.gif
  • small_russia.gif
  • small_scotland.gif
  • small_serbia.gif
  • small_slovakia.gif
  • small_slovenia.gif
  • small_spain.gif
  • small_sweden.gif
  • small_switzerland.gif
  • small_turkey.gif
  • small_ukraine.gif
  • small_wales.gif
  • dot.gif
  • dot.gif
  • arrow1.gif
  • down_arrow.gif
  • arrow4.gif
  • robben-2.jpg
  • ic_ajax.jpg
  • sbn.png
  • logo_1316848a.jpg
  • icon_smile.gif
  • stats.jpg
  • ibi.jpg
  • robben.jpg
  • end.gif
  • large_netherlands.gif
  • comments.gif
  • jan-logo2-120x120.png
  • 230px-Jetro_Willems-120x120.jpg
  • portu-fans-120x120.jpg
  • Frank-Rijkaard-120x120.jpg
  • german-national-team-120x120.jpg
  • rss-12x12.gif
  • rss_home.jpg
  • read_more.gif
  • common_gif.gif
  • bgr_netherlands.gif
  • bgr_main_hp.gif
  • vertical_dot.gif
  • common_head.gif
  • storeTitle.jpg
  • facebook.png
  • urchin.js
  • twitter.png
  • rss.png
  • buy.jpg
  • article_flag_france.gif
  • article_flag_croatia.gif
  • article_flag_czechrepublic.gif
  • article_flag_england.gif
  • article_flag_germany.gif
  • article_flag_italy.gif
  • article_flag_netherlands.gif
  • article_flag_poland.gif
  • article_flag_portugal.gif
  • article_flag_serbia.gif
  • article_flag_spain.gif
  • article_flag_sweden.gif
  • article_flag_switzerland.gif
  • article_flag_ukraine.gif
  • article_flag_greece.gif
  • article_flag_russia.gif
  • quant.js
  • beacon.js
  • __utm.gif
  • article_flag_scotland.gif
  • article_flag_ireland.gif
  • pixel;r=476530369;a=p-d9vfr8QTWnv1E;fpan=1;fpa=P0-272303911-1458252623231;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458252623231;tzo=-180;ref=;;ogl=
  • article_flag_norway.gif
  • article_flag_turkey.gif
  • article_flag_romania.gif
  • article_flag_austria.gif
  • article_flag_denmark.gif
  • article_flag_albania.gif
  • article_flag_belgium.gif
  • article_flag_wales.gif
  • article_flag_bosnia.gif
  • article_flag_israel.gif
  • article_flag_slovakia.gif
  • article_flag_slovenia.gif
  • closer_bottom.gif
  • ic_comment.gif

Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original, 84% (92 requests) were made to and 4% (4 requests) were made to The less responsive or slowest element that took the longest time to load (474 ms) relates to the external source

Additional info on


The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Netherlands 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 8 to 1 for JavaScripts and as a result speed up the page load time.









Possible request optimization











Normal result

IP address uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 300

Language and encoding

Normal result


EN en language flag


N/A  language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of is located in United States, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Netherlands 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:

Share this report in social media

Analyze another website