We loaded google.com from Amsterdam, Montreal, San Francisco and Singapore — 20 times each — and measured how long it actually took. Here's what real users in those cities would experience.
Independent measurement by LatencyRadar. Not affiliated with Google.
Google is the gold standard for global infrastructure, and this test shows why. Every request came back successfully, load times were fast in every city, and there was barely any difference between a typical request and a slow one. If you want to know what a well-optimized global service looks like, this is the benchmark to compare against.
A standard page load from four cities, repeated 20 times each. Google is a useful reference point precisely because it's one of the most optimized services on the internet — seeing how your own site or API compares to this result tells you a lot.
Everywhere — but not equally. Singapore was the fastest city in this test, which is unusual and reflects Google's heavy infrastructure investment in Asia. Amsterdam was nearly as fast. Montreal and San Francisco were slower, though still well within what users would consider instant.
Singapore came in at 41 ms typical — the fastest of any region. Amsterdam was close at 47 ms. Montreal climbed to 78 ms and San Francisco to 86 ms. The most notable number is San Francisco's occasional spike to 577 ms — rare, but worth knowing if your users are on the US West Coast. Every other region was remarkably consistent.
DNS lookup was effectively zero in every city — Google's name resolution is essentially instant globally. Most of the time is split between the security handshake and the server sending back the first byte of content. There's no download time to speak of, which makes sense for a search page that's designed to be as lightweight as possible.
Start with the headline number for each city. Open the technical breakdown only if you want to see where that time is coming from.
20 requests · 100% successful
20 requests · 100% successful
20 requests · 100% successful
20 requests · 100% successful
The typical load time tells you what most requests look like. But users don't only make typical requests. San Francisco is a good example here — 86 ms is the typical load time, which feels fast. But 1 in 100 requests took 577 ms. That's the kind of occasional slowness that makes a site feel unreliable even when it's usually quick. We show both numbers so you get the full picture.
We made a standard page request to google.com from servers in 4 cities: Amsterdam, Montreal, San Francisco and Singapore. Each city ran 20 requests. We measured how long each step took — DNS lookup, connecting, security handshake, and server response — then calculated typical and worst-case times from the results.
Run a free speed test from multiple cities and see how your load times compare — no setup, no account required.
Takes about 30 seconds.