Benchmark report
Is cloudflare.com slow?
Page load times from 4 cities
Slow from some locations
Singapore waited 482 ms, about 2× Amsterdam. The gap suggests some test locations reach a distant server.
- Fastest
- 237 ms
- Amsterdam
- Slowest
- 482 ms
- Singapore
- Successful requests
- 100%
- 4 locations
Response time around the world
Amsterdam237 ms
San Francisco244 ms
Montreal338 ms
Singapore482 ms
Why is Singapore slower?
Singapore waited 482 ms for the homepage, twice Amsterdam and San Francisco at about 240 ms, with Montreal in between at 338 ms. Finding, reaching and securing the connection took single-digit milliseconds everywhere. Almost all of the wait is the server preparing and sending a 1.3 MB document, so a faster DNS would change nothing here. Content closer to the slow cities would.
Click the location to see each stage.
Singapore590 ms
Singapore- Reaching the server
- 7 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 571 ms
- Receiving the response
- 13 ms
- Total
- 590 ms
Each part is its own worst case, so they do not add up to the total. Why
Compare all locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam410 ms
Amsterdam- Reaching the server
- 10 ms
- Setting up security
- 11 ms
- Waiting for the server: most of the time
- 355 ms
- Receiving the response
- 40 ms
- Total
- 410 ms
Montreal487 ms
Montreal- Reaching the server
- 11 ms
- Setting up security
- 14 ms
- Waiting for the server: most of the time
- 473 ms
- Receiving the response
- 43 ms
- Total
- 487 ms
San Francisco429 ms
San Francisco- Reaching the server
- 9 ms
- Setting up security
- 10 ms
- Waiting for the server: most of the time
- 412 ms
- Receiving the response
- 13 ms
- Total
- 429 ms
Singapore590 ms
Singapore- Reaching the server
- 7 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 571 ms
- Receiving the response
- 13 ms
- Total
- 590 ms
Each part is its own worst case, so they do not add up to the total. Why
Cloudflare still feels slow?
- Check Cloudflare’s status page
- Edge incidents are posted per location there. If your region is listed, that is the cause and not your site.
- This is not a benchmark of your zone
- Your site’s speed on Cloudflare depends on your cache rules, origin location and plan. A slow cloudflare.com says little about it, and Workers, R2, 1.1.1.1 and the dashboard are other systems again.
- Served from Cloudflare’s own edge
- The homepage was a cache hit at Cloudflare’s edge in every city. A slow result here is that edge delivering a 1.3 MB document to your region.
Response time over the last 8 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 5 September 2026 | 82 ms | 137 ms | 278 ms ▲ | 331 ms | 191 ms | — |
| 6 September 2026 | 83 ms | 134 ms | 253 ms ▲ | 275 ms | 205 ms | — |
| 8 September 2026 | 79 ms | 138 ms | 56 ms | 269 ms | 193 ms | 245 ms |
| 9 September 2026 | 82 ms | 155 ms | 75 ms | 284 ms | 196 ms | 244 ms |
| 10 September 2026 | 77 ms | 146 ms | 60 ms | 281 ms | 205 ms | 263 ms |
| 11 September 2026 | 90 ms | 141 ms | 83 ms | 275 ms | 192 ms | 241 ms |
| 12 September 2026 | 89 ms | 132 ms | 72 ms | 263 ms | 200 ms | 242 ms |
About this measurement
GET www.cloudflare.com · 20 requests per location · 1 March 2026
What we tested · Marketing website. The www.cloudflare.com marketing homepage, a 1.3 MB HTML document served from Cloudflare's own edge cache.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: The CDN edge that serves your zone, Workers, 1.1.1.1 or the dashboard. A cdnjs asset surface is planned.
The measured request loads the HTML of www.cloudflare.com, Cloudflare’s marketing homepage. It does not load every image and script as a browser would. It also does not test how Cloudflare serves your site: your cache rules, origin and plan determine that request’s behaviour. The shared company name does not make the two measurements interchangeable.
The main results come from four test locations on 1 March 2026. The history shows later daily collection, with dates on the charts. In the published run, Amsterdam and San Francisco received the homepage in about 240 ms typical, while Singapore took 482 ms. That difference belongs to this document and test period.
A small CSS file from cdnjs is a separate measured endpoint in the catalog. Its own results can help describe static-file delivery once published, but they cannot replace the homepage’s timings. This page does not measure Workers, R2, the dashboard, WARP, or the 1.1.1.1 resolver.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 237 ms | 410 ms | 20 |
| Montreal | 338 ms | 487 ms | 20 |
| San Francisco | 244 ms | 429 ms | 20 |
| Singapore | 482 ms | 590 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.cloudflare.com
- Measured from
- Amsterdam · Montreal · San Francisco · Singapore
- Requests
- 80 requests · 20 from each of 4 cities · 1 March 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
Cloudflare website
https://www.cloudflare.com/
Independent measurement by LatencyRadar. Not affiliated with Cloudflare. · 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.
