So-net.ne.jp

Tests Summary Summary Widget Summary Table

Latency Summary Latency Test Overview Latency Graph Latency Details Compare Latency rating table Latency Importance

DNS Summary DNS Speed Tests DNS Graph Compare DNS Rating Table

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

Site Speed Laboratory Summary for this website

Summary Widget

Website Latency (Ping Test)

Latency History Graph

How to read the graph's data

Compare Latency Statistic

Compare latency

vs

Our Servers

Usa

NY, New York
Florida, Tampa

Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester

Dynamic of the Latency Changes for the website from various locations.

Why the low latency is important with this site as an example

To display this website browser needs to download 51 objects. Though modern browsers use parallel connection now, we'll simplify the conditions and calculate the time spent by the browser for these sites in a single-threaded mode. Time required to establish HTTP connection only: + preparation of the webserver response. Number 3 in the formula is a three phase of a TCP connection: sending a SYN request from the client to the server, sending ASK + SYN from the server to the client and the ASK sending from the client to the server. Though we can not calculate the time for a webserver response, the total time for sending and receiving requests for each of the object will be: Of course, modern browsers use several simultaneous connections to download content from a domain (from 2 to 8 at the time of writing this document). And in some browsers the number of connections can be set manually (Opera). But, if you impose these data on the first site Mooinic.net from the latency table for the city , it turns out that the difference in time only for the sending and receiving requests to the web server could be: 15.3 sec. Sure, making such calculations must always take into account the audience site, and always make an accent on the fact that the server should always be so geographically closer to the primary audience as it possible. Also we recommend to pay attention to an article about importance of the latency on our site.

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 So-net.ne.jp'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.

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 423.6 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 105.9 Kb (saving 317.7 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in So-net Entertainment Corporation.

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 1 redirects before page components start loading. The following list contains some of these redirects:
Try to reduce the number unnecessary redirects.

Using H1 tag

Show main content of the page clearly. One of the most important internal website ranking factors is the H1 tag. It's a title of the document and the most powerful keyword, actually. Our robot did not find the h1 tag on the page.

Content Semantics

We suggest you along with important and well-known tags like Title & H1 use also H2, H3, H4, H5, STRONG tags. Each page can (and should) highlight not only the main topic, but also complement the semantic core of the page and the whole site with the secondary keywords. For example, if the main topic of the page is dedicated servers, there is a probability that page has a blog about managed dedicated servers. If so try to highlight the title of the block by using tag <H2>, and an information that you provide this service in the United Kingdom highlight with H3 tag and so on. Thus try to highlight every important fragment of the information on your page with tags like STRONG, H2, H3, etc. We did not find H2 tags, H3 tags, H4 tags, H5 tags, STRONG tags on the page