Benchmark report
Is netlify.com slow?
Homepage load times from 5 cities
Fast globally
Netlify responds quickly from all 5 test locations. Montreal was fastest at 23 ms; Amsterdam took 72 ms.
- Fastest
- 23 ms
- Montreal
- Slowest
- 72 ms
- Amsterdam
- Successful requests
- 100%
- 5 of 6 locations
Response time around the world
Montreal23 ms
Tokyo26 ms
Singapore28 ms
San Francisco31 ms
Amsterdam72 ms
MumbaiCollecting since 7 Sept 2026
Why is Amsterdam slower?
Four cities look alike in the controlled run of 7 September: 20 to 29 ms in total, with the TLS handshake at 4 to 6 ms and the download at 6 to 10 ms. Amsterdam took 69 ms, and the extra time sits in two places: the handshake (18 ms) and the download (33 ms). Both grow with distance, which suggests Amsterdam is reaching an edge further away than the other cities are. The wait for the first byte was only 16 ms.
Click the location to see each stage.
Amsterdam69 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 2 ms
- Setting up security
- 18 ms
- Waiting for the server
- 16 ms
- Receiving the response: most of the time
- 33 ms
- Total
- 69 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
Compare all locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam69 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 2 ms
- Setting up security
- 18 ms
- Waiting for the server
- 16 ms
- Receiving the response: most of the time
- 33 ms
- Total
- 69 ms
San Francisco29 ms
San Francisco- Finding the server
- 12 ms
- Reaching the server
- 4 ms
- Setting up security
- 6 ms
- Waiting for the server
- 9 ms
- Receiving the response: most of the time
- 10 ms
- Total
- 29 ms
Montreal20 ms
Montreal- Finding the server
- 15 ms
- Reaching the server
- 2 ms
- Setting up security
- 4 ms
- Waiting for the server: most of the time
- 8 ms
- Receiving the response
- 6 ms
- Total
- 20 ms
Singapore23 ms
Singapore- Finding the server
- 4 ms
- Reaching the server
- 3 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 8 ms
- Receiving the response
- 7 ms
- Total
- 23 ms
Tokyo22 ms
Tokyo- Finding the server
- 3 ms
- Reaching the server
- 2 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 8 ms
- Receiving the response
- 7 ms
- Total
- 22 ms
The phases come from the controlled run of 7 September 2026. Typical times pool daily requests; slower times use controlled full runs. 5 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo.
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
Netlify still feels slow?
- Check Netlify’s status page
- Platform and CDN incidents are posted there before they show up in a benchmark.
- This is not a benchmark of your site
- A site on Netlify has its own build output, redirects, functions and cache headers. Functions, Edge Functions, forms, identity and the dashboard are not measured here.
- European visitors get the Amsterdam number
- Our cities reached two addresses in the controlled run, 49 ms apart at most. Amsterdam's longer handshake and download suggest it is served from further away than the other four. If your visitors are in Europe, expect its number rather than Montreal's.
Response time over the last 30 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 27 August 2026 | 73 ms | 41 ms | 24 ms | 29 ms | 29 ms | — |
| 28 August 2026 | 81 ms | 31 ms | 25 ms | 24 ms | 29 ms | — |
| 29 August 2026 | 75 ms | 37 ms | 24 ms | 88 ms ▲ | 27 ms | — |
| 30 August 2026 | 69 ms | 36 ms | 26 ms | 94 ms ▲ | 28 ms | — |
| 31 August 2026 | 72 ms | 31 ms | 25 ms | 90 ms ▲ | 27 ms | — |
| 1 September 2026 | 72 ms | 31 ms | 24 ms | 21 ms | 32 ms | — |
| 2 September 2026 | 66 ms | 39 ms | 22 ms | 29 ms | 27 ms | — |
| 3 September 2026 | 68 ms | 27 ms | 23 ms | 25 ms | 1337 ms ▲ | — |
| 4 September 2026 | 71 ms | 1010 ms ▲ | 22 ms | 25 ms | 27 ms | — |
| 5 September 2026 | 69 ms | 29 ms | 24 ms | 31 ms | 24 ms | — |
| 6 September 2026 | 73 ms | 30 ms | 22 ms | 29 ms | 25 ms | — |
| 7 September 2026 | 73 ms | 37 ms | 22 ms | 30 ms | 23 ms | 26 ms |
| 8 September 2026 | 80 ms | 28 ms | 19 ms | 25 ms | 24 ms | 26 ms |
| 9 September 2026 | 67 ms | 25 ms | 22 ms | 32 ms | 27 ms | 22 ms |
| 10 September 2026 | 74 ms | 39 ms | 21 ms | 23 ms | 23 ms | 21 ms |
| 11 September 2026 | 84 ms | 35 ms | 37 ms | 30 ms | 27 ms | 33 ms |
| 12 September 2026 | 74 ms | 24 ms | 43 ms | 24 ms | 21 ms | 23 ms |
About this measurement
GET www.netlify.com · 70 requests per location over 14 daily runs · 30 August 2026 to 12 September 2026
What we tested · Marketing website. The www.netlify.com marketing homepage, about 410 KB of HTML served from Netlify's own CDN cache.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: A site you deploy on Netlify, its Functions, or the dashboard.
One Netlify surface: the www.netlify.com marketing homepage, about 410 KB of HTML that Netlify serves from its own CDN cache. Netlify hosts it on the same delivery network it sells, so the page shows how that network answers a cold request from each of our cities. It does not stand for a site you deploy there: your build output, redirects, functions and cache headers set your own numbers.
Not measured: sites deployed on Netlify, Functions, Edge Functions, the dashboard, forms or identity, or anything a browser does after the HTML arrives. We cannot see Netlify's cache from outside, so a slow request could be a cache miss or the path from our worker to the edge; the timing alone does not say which.
Between 30 August and 12 September 2026 four cities had a typical time of 23 to 31 ms and Amsterdam 72 ms. Amsterdam's daily median stayed between 66 and 84 ms over 14 runs, so this is a steady difference rather than a few slow days. San Francisco and Tokyo were the opposite: usually under 40 ms, with one daily median above a second each (1010 ms on 4 September and 1337 ms on 3 September) that the pooled typical time absorbs but the history chart shows. Fastly, measured the same way, is faster still in four cities; Vercel is slower in every city.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 72 ms | 84 ms | 20 |
| San Francisco | 31 ms | 40 ms | 20 |
| Montreal | 23 ms | 29 ms | 20 |
| Singapore | 28 ms | 66 ms | 20 |
| Tokyo | 26 ms | 35 ms | 20 |
| Mumbai | Collecting since 7 Sept 2026 | ||
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.netlify.com
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo
- Requests
- Daily measurements from 30 August 2026 to 12 September 2026. 5 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo. · 30 August 2026 to 12 September 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
- Report coverage
- 5 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo.
- Daily requests in each location
- Amsterdam: 70 · San Francisco: 70 · Montreal: 70 · Singapore: 70 · Tokyo: 70
- Typical response time
- Median of the eligible daily requests in each included location.
- Slower response time
- Median of recent controlled full-run p95 values in each included location.
Netlify
https://www.netlify.com/
Independent measurement by LatencyRadar. Not affiliated with Netlify. · How we measure (v1.1)
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.
