Google.com.vn

 
Latensy Flash Graph
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester
Learn more at Latency Testing Profile
Separate test for different locations, time frames
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester
Learn more at DNS Testing Profile
Separate test for different locations, time frames
Learn more at PageSpeed Testing Profile

WebSite Speed Profile

Site Speed Success Formula = good website latency + fast DNS lookup + high page load speed.
Site Speed Laboratory offers analysis of DNS Lookup speed & latency tests (ping) & Page Load speed for every website. Our analysis is based on data for May 24 2011. Since the first of July 2010 we carried out 23 tests from locations
for the main page of this website, the last of which were made about 28481 hours ago

Tests Summary

Latency Summary

DNS Summary

Page Speed Summary

Site Speed Laboratory Summary for this website

Location Ping Ping,
change
DNS Lookup DNS Resolve,
change
Page Speed Page Speed,
change
 Usa
6.40% of traffic
NY, New York 22 ms 195 ms 55 % 98.77 Kb/s 61%
Florida, Tampa 31 ms 293 ms 74 %
 Germany
1.50% of traffic
Frankfurt 22 ms 267 % 76 ms 245 %
 Canada
Montreal 8 ms 332 ms
 United Kingdom
Gloucester 15 ms 26 ms

Summary Widget

SiteSpeedLab Overall Website Rating for this website
Based on our speed test results table and considering features of the current webserver location (United states, Mountain view), we concluded
overall This website speed rank is 65. That means 65% of the sites from the Mountain view are slower for visitors than this website.

It is important to understand that you can't evaluate website speed without considering website audience location. You should evaluate the speed of the site considering location of your primary audience (visitors), and not just from abstract tests from various points of the planet. There is a chance that your website is quite slow for visitors from German but pretty quick for Australian users at the same time. Based on a primary audience location data Site Speed Laboratory maintains objective rating. Test servers located in the Usa and Germany are more useful and important to Google.com.vn because the shares of each country are 6.40 and 1.50 percent respectively.

You should not overestimate the importance of the website speed factor. Google has more than 200 ranking factors and website speed is just one of them.

Graph Milestones

Milestones indicate the approximate date when the Web server was moved from one location to another. We specifically did not perform measurements at the time of the move (DNS requests may receive a different IP for the same domain from different locations, where the testing servers are located). Therefore we have the graph with two or more segments. It's a data measured before and after webserver was moved to the new location.
  Date Country, City Hosting IP
Milestone l 24.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 209.85.225.103
Milestone k 24.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.39.103 to 66.102.13.103
Milestone j 20.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.39.103
Milestone i 20.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.95.103 to 66.102.13.103
Milestone h 20.05.2011 From United States, Atlanta
to United States, Mountain view
From Google
to Google
72.14.209.104 to 74.125.95.103
Milestone g 20.05.2011 From United States, Mountain view
to United States, Atlanta
From Google
to Google
74.125.67.103 to 72.14.209.104
Milestone f 15.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.67.103
Milestone e 15.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.225.48 to 66.102.13.103
Milestone d 15.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.225.48
Milestone c 15.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.16 to 66.102.13.103
Milestone b 11.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.16
Milestone a 11.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.225.16 to 66.102.13.103
Milestone ` 11.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.225.16
Milestone _ 11.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.159.103 to 66.102.13.103
Milestone ^ 06.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.159.103
Milestone ] 06.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.45.103 to 66.102.13.103
Milestone \ 02.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.45.103
Milestone [ 02.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.225.16 to 66.102.13.103
Milestone Z 02.05.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.225.16
Milestone Y 02.05.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.48 to 66.102.13.103
Milestone X 27.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.48
Milestone W 27.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.225.16 to 66.102.13.103
Milestone V 27.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.225.16
Milestone U 27.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.80 to 66.102.13.103
Milestone T 22.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.80
Milestone S 22.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.67.103 to 66.102.13.103
Milestone R 22.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.67.103
Milestone Q 18.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.45.103 to 66.102.13.103
Milestone P 18.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.45.103
Milestone O 18.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.80 to 66.102.13.103
Milestone N 12.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.80
Milestone M 12.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.225.16 to 66.102.13.103
Milestone L 12.04.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.225.16
Milestone K 12.04.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.80 to 66.102.13.103
Milestone J 29.03.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.80
Milestone I 29.03.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.80 to 66.102.13.103
Milestone H 23.03.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.80
Milestone G 23.03.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.16 to 66.102.13.103
Milestone F 15.02.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.226.16
Milestone E 15.02.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.230.112 to 66.102.13.103
Milestone D 15.02.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.230.112
Milestone C 10.02.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.95.103 to 66.102.13.103
Milestone B 10.02.2011 From United States, Santa monica
to United States, Mountain view
From Google
to Google
66.102.13.103 to 74.125.95.103
Milestone A 05.02.2011 From United States, Mountain view
to United States, Santa monica
From Google
to Google
74.125.226.16 to 66.102.13.103

Website Latency (Ping Test)

Latency Tests

Check details on Ping Graph

Latency affects on the rate of exchange of network packets between the client (user's computer) and the webserver. The lower latency to webserver means the faster start of the processing of all requests to the webserver, and after all the faster page loading. According to our data the average latency to the web server is 19 ms (see details). Test was conducted from 5 different locations. Average latency rating of the website is good (95% websites are slower). For detailed latency stats from different locations, as well as time slices for a month, 3 months and 6 months and more visit Ping Test Graph. We also recommend to take a look at latency rating at the United states, Mountain view location. This will give you an idea about average latency values in the region. And the answer to the question of how good this result for the this website.

Latency History Graph

Compare Latency From
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Numbered vertical lines indicate the change of IP for the current site
  • Data Loss
Compare Latency From
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Numbered vertical lines indicate the change of IP for the current site
  • Data Loss
Compare Latency From
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Numbered vertical lines indicate the change of IP for the current site
  • Data Loss
Compare Latency From
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Numbered vertical lines indicate the change of IP for the current site
  • Data Loss

How to read the graph's data

This graph represents a detailed statistics of website latency. Periodical measurements give a complete picture of website availability from the different areas of the planet. Particular attention is given to the expansion of our testing servers around the world, in order to test the site availability and latency in those locations where most of your visitors are. Of course, the faster access to the site means users get content faster. It means less bounce (bounce rate) and faster ads delivering (and therefore better performance CTR, eCPM). This is even more important given the fact that we've detected Google Adsense ad network code on this site. Ultimately, the best availability of the site gives you an edge over your competitors. More information can be read on our page about the importance of the latency speed for the website speed up.

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.

Location Last check 7 day change 1 month change 3 month change 6 month change
 Usa
6.40% of traffic
NY, New York 22 ms
Florida, Tampa 31 ms
 Germany
1.50% of traffic
Frankfurt 22 ms
 Canada
Montreal 8 ms
 United Kingdom
Gloucester 15 ms

Fragment of Mountain view latency speed rating table for this website

The table is constructed according to the data from the US datacenters

# Domain Compare Ping Provider
1. Dota-utilities.com 15 ms Google
2. Ieatishootipost.sg 15 ms Google
3. Malaysiancareer.com 15 ms Google
... ... ... ... ...
54. Google.com.co 19 ms Google
55. Google.be 19 ms Google
56. Google.com.vn 19 ms Google
57. Google.se 19 ms Google
58. Google.com.pe 19 ms Google
... ... ... ... ...
2533. Medicaljordan.com 29 ms
6 % Loss
Google
... ... ... ... ...
2682. Dotnspot.com
100 % Loss
Google

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

To display this website browser needs to download 8 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:
3 * website latency * website objects
+ 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:
3 * 19 ms * 8 objects = 0 sec
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 Dota-utilities.com from the latency table for the city Mountain view, it turns out that the difference in time only for the sending and receiving requests to the web server could be: 0.1 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

Browser should lookup domain name and get IP address of the server (209.85.225.103) before downloading the page. We test DNS resolve for this domain from 5 locations. That's how we've got the average time of receiving IP: 0.18s (which is better than 24% of all sites). For more detailed stats look at DNS tests graph and DNS resolve page for United states, Mountain view location (Average value on the widget is an average DNS resolve time for websites hosted at the same location).

DNS History Graph

Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss

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.

Location Last check 7 day change 1 month change 3 month change 6 month change
 Usa
6.40% of traffic
NY, New York 195 ms
Florida, Tampa 293 ms
 Germany
1.50% of traffic
Frankfurt 76 ms
 Canada
Montreal 332 ms
 United Kingdom
Gloucester 26 ms

Fragment of Mountain view DNS Speed rating table for this website

The table is constructed according to the data from the US datacenters

# Domain Compare DNS Resolve Speed Provider
1. Google.com 19 ms Google
2. Smugmug.net 22 ms Smugmug
3. Meebo.org 26 ms Meebo
... ... ... ... ...
2011. Southasiablog.com 183 ms Google
2012. Madstratter.com 183 ms Google
2013. Google.com.vn 184 ms Google
2014. Google.com.fj 184 ms Google
2015. Fundmymutualfund.com 184 ms Google
... ... ... ... ...
2682. Piratasdepc.com 4772 ms Google

Page Speed Test

Content-Type's Weights
 
 
Content-Type's Weights by Hosts
 
 
Downloading page itself is the final stage of the testing. Actually, this is the last stage, after which page is displayed completely for user. The download speed depends on many factors. Main factors are the following: the width of the bandwidth up to the domain, the number of simultaneous download threads, speed of the server, a distance between user and domain web server. Recent measurements have shown the speed of page download for this domain is 98.771Kb/s (which is better than 65% of all sites in this region). For more detailed stats check out report for Mountain view hosted websites.

 
 
 

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:

Pagespeed Flash 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.

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.
http://www.google.com.vn/images/srpr/nav_logo27.png  Content-Encoding: image/png. File size 30.6 Kb.
http://www.google.com.vn/extern_js/f/CgJ2aRICdm4rMEU4ACwrMFo4ACwrMA44A...  Content-Encoding: text/javascript; charset=UTF-8. File size 37.12 Kb.

Alternate text for the images.

As you may already know, search engine that indexes your pages, do not have eyes. And all content you are trying to display on your site is just HTML & CSS code, images, Flash, etc for the robots. It is It's extremely important to describe each of the objects more datailed using ALT, TITLE and other tags.

Our robot has determined that the google.com.vn page has 1 images, which has no tag ALT. Tag ALT is a text field, that specifies an alternate text for an image. But not only. Search engines consider this tag as a supplemental result for assessing the content of your page entirely. Do not ignore it!

For example your page has this code:
10.   <img src="/textinputassistant/tia.png" style="position: absolute; cursor: pointer; right: 5px; top: 4px; z-index: 300;" onclick="var s=document.createElement('script');s.src='/textinputassistant/0/vi_tia.js';google.append(s);" height="23" width="27">
We recommend you use rich img code in that place:
10.   <img src="/textinputassistant/tia.png" style="position: absolute; cursor: pointer; right: 5px; top: 4px; z-index: 300;" onclick="var s=document.createElement('script');s.src='/textinputassistant/0/vi_tia.js';google.append(s);" height="23" width="27" alt="kinh doanh">


P.S. We used keyword for this image that seemed to us most important for your page. But you can go ahead and give to each of 1 images an ALT text. This problem requires responsible approach. No need to put the same text at alt tag of the all images. Imagine that the pictures do not show and try to make sure that users understand what is shown on the picture based on the alt tag

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

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:
10.   <a href="http://www.google.com.vn/imghp?hl=vi&tab=wi" onclick="gbar.qs(this)" class="gb1">Hình ảnh</a>
We suggest you to remake it in this way:
10.   <a href="http://www.google.com.vn/imghp?hl=vi&tab=wi" onclick="gbar.qs(this)" class="gb1" title="hình ảnh">Hình ảnh</a>
Of course, you can (and should) use more proper phrase instead of the "hình ảnh" that describes the link http://www.google.com.vn/imghp?hl=vi&tab=wi.


Our Mailbox © 2009 — 2014 SiteSpeedLab & SiteSpeedLab.com
Be Quick or Be Dead