We loaded cloudflare.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 Cloudflare.
Cloudflare's homepage loaded reliably every single time, but speed varied quite a bit depending on where you are. Users in Amsterdam and San Francisco get a snappy experience around 240 ms. Users in Singapore wait more than twice as long. If your audience is global, that gap is worth knowing about.
A straightforward page load from four cities, repeated 20 times each. No tricks, no warmup — just the same request your users would make. Every single one came back successfully.
Amsterdam and San Francisco had similar, fast results. Montreal was slower. Singapore was the slowest by a significant margin. If you're building something for a global audience, this kind of regional spread is exactly what you need to plan for.
Amsterdam was fastest at around 237 ms typical. San Francisco close behind at 244 ms. Montreal climbed to 338 ms typical, with occasional spikes past 480 ms. Singapore averaged 482 ms — more than double Amsterdam. One thing that stands out: San Francisco occasionally spiked to 688 ms, even though it's usually fast.
DNS lookup, connecting to the server, and the security handshake are all nearly instant — we're talking single-digit milliseconds. Almost all the wait time is the server preparing and sending the response. That means if you want Cloudflare to feel faster in slow regions, the answer isn't better DNS — it's getting the content closer to those users.
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
Average load times look great on paper but hide the slow requests that real users actually experience. We show both a typical speed and an 'on a bad day' number — that's the slowest 1 in 20 requests. If your users hit that occasionally, they'll notice. That's the number worth caring about.
We made a standard page request to cloudflare.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, connection, security handshake, server response, and download — then calculated typical and worst-case times from the results.
Run a free speed test from multiple cities and find out where your users are waiting — no setup, no account required.
Takes about 30 seconds.