Benchmark report
Is google.com slow?
Page load times from 5 cities
Fast globally
Google responds quickly from all 5 test locations. Amsterdam was fastest at 56 ms; San Francisco took 102 ms.
- Fastest
- 56 ms
- Amsterdam
- Slowest
- 102 ms
- San Francisco
- Successful requests
- 100%
- 5 locations
Response time around the world
Amsterdam56 ms
Singapore57 ms
Montreal82 ms
Tokyo98 ms
San Francisco102 ms
The wait is the server, not the network
Connecting and the secure handshake are quick in every city because each one talks to a nearby Google server. Most of each request, 40 to 75 ms depending on the city, is Google preparing the homepage. For a page like this that is the real work, and it is why San Francisco and Tokyo sit around 100 ms while Amsterdam and Singapore come in near 56 ms.
Compare all locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam56 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 2 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 43 ms
- Receiving the response
- 4 ms
- Total
- 56 ms
San Francisco102 ms
San Francisco- Finding the server
- 12 ms
- Reaching the server
- 2 ms
- Setting up security
- 19 ms
- Waiting for the server: most of the time
- 60 ms
- Receiving the response
- 21 ms
- Total
- 102 ms
Montreal82 ms
Montreal- Finding the server
- 2 ms
- Reaching the server
- 3 ms
- Setting up security
- 21 ms
- Waiting for the server: most of the time
- 53 ms
- Receiving the response
- 5 ms
- Total
- 82 ms
Singapore57 ms
Singapore- Finding the server
- 4 ms
- Reaching the server
- 3 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 42 ms
- Receiving the response
- 5 ms
- Total
- 57 ms
Tokyo98 ms
Tokyo- Finding the server
- 2 ms
- Reaching the server
- 3 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 76 ms
- Receiving the response
- 11 ms
- Total
- 98 ms
Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.
Bars show the typical request, so the parts add up to its total. Why
Google still feels slow?
- Check Google’s status dashboard
- A Google-side incident shows up there before it shows up in a benchmark.
- This is not a search benchmark
- The page measures the homepage document only. A search query, the results page and signed-in Google products run on other systems.
- Served by Google’s front end
- The homepage is marked private, so no shared cache sits in between. Each of our cities reached a different Google address, and most of the time is Google building the page rather than the trip to it.
Response time over the last 17 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 26 August 2026 | 70 ms | 99 ms | 107 ms | 51 ms | 95 ms | — |
| 27 August 2026 | 64 ms | 108 ms | 93 ms | 165 ms ▲ | 96 ms | — |
| 28 August 2026 | 52 ms | 163 ms | 87 ms | 56 ms | 97 ms | — |
| 29 August 2026 | 52 ms | 101 ms | 102 ms | 48 ms | 138 ms | — |
| 30 August 2026 | 52 ms | 98 ms | 85 ms | 53 ms | 96 ms | — |
| 31 August 2026 | 54 ms | 101 ms | 105 ms | 51 ms | 95 ms | — |
| 1 September 2026 | 52 ms | 98 ms | 101 ms | 52 ms | 96 ms | — |
| 2 September 2026 | 52 ms | 93 ms | 84 ms | 52 ms | 98 ms | — |
| 3 September 2026 | 51 ms | 105 ms | 82 ms | 50 ms | 90 ms | — |
| 4 September 2026 | 52 ms | 103 ms | 97 ms | 54 ms | 96 ms | — |
| 5 September 2026 | 53 ms | 91 ms | 82 ms | 55 ms | 98 ms | — |
| 6 September 2026 | 52 ms | 93 ms | 89 ms | 67 ms | 93 ms | — |
| 7 September 2026 | 53 ms | 98 ms | 83 ms | 56 ms | 95 ms | 126 ms |
| 8 September 2026 | 50 ms | 94 ms | 78 ms | 47 ms | 93 ms | 121 ms |
| 9 September 2026 | 51 ms | 144 ms | 83 ms | 56 ms | 97 ms | 119 ms |
| 10 September 2026 | 51 ms | 94 ms | 142 ms | 52 ms | 94 ms | 119 ms |
| 11 September 2026 | 50 ms | 278 ms ▲ | 79 ms | 51 ms | 90 ms | 114 ms |
| 12 September 2026 | 49 ms | 95 ms | 86 ms | 54 ms | 106 ms | 182 ms |
About this measurement
GET www.google.com · 20 requests per location · 20 August 2026
What we tested · Website document. The www.google.com homepage HTML, about 84 KB, served by Google's own front end (gws) with no shared cache in between.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: A search query, the results page, Maps, Gmail or any signed-in Google product.
One Google surface: GET www.google.com/, the homepage HTML, about 84 KB from Google's own front end (server gws) with private caching, so every request reaches Google. It measures the arrival of the HTML document, before a browser loads additional files or runs scripts. The request carries no search query and does not open a signed-in session.
Not measured: a search query and the results page, which run on a different backend; signed-in surfaces; Maps, Gmail and YouTube.
In the displayed 20 August run, Amsterdam and Singapore received the homepage in about 56 ms typical, while San Francisco and Tokyo took around 100 ms. That is a comparison of one document from these test locations. It does not measure how quickly Google completes a search or how quickly the rest of a page becomes usable.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 56 ms | 78 ms | 20 |
| San Francisco | 102 ms | 112 ms | 20 |
| Montreal | 82 ms | 104 ms | 20 |
| Singapore | 57 ms | 64 ms | 20 |
| Tokyo | 98 ms | 118 ms | 20 |
Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics
- Request
- GET www.google.com
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo
- Requests
- 100 requests · 20 from each of 5 cities · 20 August 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
https://www.google.com/
Independent measurement by LatencyRadar. Not affiliated with Google. · How we measure (v1.3)
How fast does your site load around the world?
Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.
No account required · Takes about 30 seconds.
