Shockwave.com

Tests Summary Summary Widget Summary Table

DNS Summary DNS Speed Tests DNS Graph Compare DNS New york Rating Table

Page Speed Summary Page Speed Summary Page Speed Load Objects Page Load Tips

Site Speed Laboratory Summary for this website

Summary Widget

DNS Lookup Speed

DNS History Graph

Compare DNS Speed

Compare DNS Lookup

vs

Our Servers

Usa

NY, New York
Florida, Tampa

Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester

The table below shows the dynamic of the DNS Lookup speed changes for the website from various locations.

Page Speed Test

   

Page Speed

Page Speed is a key factor in the website speed estimations (along with DNS lookup speed and website latency). Speed of the page loading, sophisticated subdomains usage for static content (images, css), optimized code (html, js), hosting on fast servers with good latency to its audience leads to good results and, ultimately, to a good website profitability.

While conducting tests we emulate a visit your website using the browser Firefox 3.5.6. Test results of the page loading listed in this table:

Ways to improve website performance

Once the document (website's main page) has been downloaded, we analyze it. It allows us to give webmasters some recommendations on how to optimize page load speed. We analyze the internal and external factors.

Reduse DNS Resolve

Browsers must resolve site's hosts to display all of the elements of the Shockwave.com's page. Every domain name resolve requires a time, which precedes the load from a specific domain. You can speed up page loading by reducing the number of hosts, from which elements of the page are loaded.

Combine Small Images Into One

To display a page, a browser needs to load a lot of small images. Try to combine images into one and display them via CSS. This technology is called 'CSS Sprites'. It helps you reduce the number of requests to the web server, which in turn also requires time and bandwidth. For more details about this technology read our manual.

Try to combine JavaScript files into one file.

This will reduce the time for requests for files and reduce the number of requests to the web server.

Enable GZIP Compression

This is a good practice to give the user content in compressed form. We've detected 6.72 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 1.68 Kb (saving 5.04 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in Viacom.

Keep Components under 25K

Users often visit web site using a mobile phone. Even the most modern and advanced gadgets have some limitations. For example an iPhone browser do not cache page components bigger than 25K. So you should strive to ensure that scripts, CSS-styles, etc. are less than 25K.

Avoid 301 & 302 Redirects

Redirect allows you to make website or page available under many URLs. Webmasters use redirects when their sites change domain name, several websites are merged into one, document is moved too a new location, etc. Using a redirect delays content obtaining. Any delay negatively affects on the user experience. We've detected that page has 16 redirects before page components start loading. The following list contains some of these redirects:
Try to reduce the number unnecessary redirects.

Specify image dimensions

The browser needs to know the actual dimensions of image (width and height) to quickly render webpage.

We have detected that the 38 images has no width and height.

If you do not specify the width and/or height, then in order to correctly display the image browser needs to download it and only then put on the screen. Otherwise, there is a chance browser will display elements under the picture inappropriately as well as the possible presence of "jumping" effect of the page content (until the page load is finished).

We provide below example of how to define the image /i/picons/shamanodysseytropic_small.jpg dimensions:

3882.

<img class="picon_small" alt="Shaman Odyssey: Tropic Adventure™" src="/i/picons/shamanodysseytropic_small.jpg" width="IMAGE_WIDTH_HERE" height="IMAGE_HEIGHT_HERE">

Use the TITLE for A tag

As we have already mentioned, search engine bots can not see the site like a people do it. They more focused on the descriptions of certain page elements. That's why we strongly recommend use TITLE operator in the "A" tag. This operator not only describes the page referenced by the page more detailed, but also takes part in the page describing. For example, you have the link on your website:

411.

<a href="http://www.addictinggames.com/">addictinggames</a>

We suggest you to remake it in this way:

411.

<a href="http://www.addictinggames.com/" title="downloadable games">addictinggames</a>

Of course, you can (and should) use more proper phrase instead of the "downloadable games" that describes the link http://www.addictinggames.com/.

Number of links on the page

Try to avoid a large number of links on the page. Our robot have found 412 links on this page. Google recommends to keep the number of links fewer than 100. More information about this topic you can find in Google Webmaster Guidelines and in the post "How many links per page?" by Matt Cutts (head of Google’s Webspam team)