Benchmark report
Is unpkg slow?
CDN response times from 6 cities
Fast globally
unpkg responds quickly from all 6 test locations. Montreal was fastest at 22 ms; Amsterdam took 42 ms.
- Fastest
- 22 ms
- Montreal
- Slowest
- 42 ms
- Amsterdam
- Successful requests
- 100%
- 6 locations
Response time around the world
Montreal22 ms
Tokyo24 ms
Mumbai28 ms
San Francisco30 ms
Singapore37 ms
Amsterdam42 ms
Why is Amsterdam slower?
unpkg runs behind Cloudflare, and every city reached a Cloudflare site in its own region except Amsterdam, whose requests were answered in London. In the controlled run of 4 October that showed in the connection: 8 ms to connect and 10 ms for the secure handshake from Amsterdam, against 2 to 6 ms and 6 to 8 ms from the other cities. Amsterdam was the slowest of the six on 8 of the 13 days and its daily median never fell below 38 ms: a small gap, but a steady one, which points to the route rather than a bad day.
Click the location to see each stage.
Amsterdam42 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 8 ms
- Setting up security
- 10 ms
- Waiting for the server: most of the time
- 24 ms
- Receiving the response
- 0 ms
- Total
- 42 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.
Amsterdam42 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 8 ms
- Setting up security
- 10 ms
- Waiting for the server: most of the time
- 24 ms
- Receiving the response
- 0 ms
- Total
- 42 ms
San Francisco28 ms
San Francisco- Finding the server
- 12 ms
- Reaching the server
- 4 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 17 ms
- Receiving the response
- 0 ms
- Total
- 28 ms
Montreal26 ms
Montreal- Finding the server
- 2 ms
- Reaching the server
- 6 ms
- Setting up security
- 6 ms
- Waiting for the server: most of the time
- 13 ms
- Receiving the response
- 1 ms
- Total
- 26 ms
Singapore37 ms
Singapore- Finding the server
- 6 ms
- Reaching the server
- 4 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 25 ms
- Receiving the response
- 1 ms
- Total
- 37 ms
Tokyo27 ms
Tokyo- Finding the server
- 1 ms
- Reaching the server
- 2 ms
- Setting up security
- 6 ms
- Waiting for the server: most of the time
- 19 ms
- Receiving the response
- 0 ms
- Total
- 27 ms
Mumbai26 ms
Mumbai- Finding the server
- 4 ms
- Reaching the server
- 2 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 16 ms
- Receiving the response
- 0 ms
- Total
- 26 ms
The phases come from the controlled run of 4 October 2026. Typical and slower times pool the daily requests. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
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
unpkg still feels slow?
- unpkg has no status page
- It is served through Cloudflare, so a Cloudflare incident can show up here. Cloudflare's status page is the closest thing to one.
- This is one pinned, unminified file
- We fetch normalize.css 8.0.1, 6.1 KB of unminified CSS at an exact version. Minified copies, ES module requests, directory listings and the redirect unpkg sends for a version range are not measured.
- Your route to Cloudflare decides who answers
- Which Cloudflare site answers depends on your network, not only on your city: our Amsterdam location went through London. A result from a nearby city is a better guide than the average.
Response time over the last 29 days
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 11 September 2026 | 44 ms | 34 ms | 25 ms | 37 ms | 27 ms | 31 ms |
| 12 September 2026 | 40 ms | 28 ms | 27 ms | 31 ms | 24 ms | 25 ms |
| 13 September 2026 | 47 ms | 43 ms | 28 ms | 73 ms | 25 ms | 31 ms |
| 14 September 2026 | 38 ms | 32 ms | 24 ms | 39 ms | 21 ms | 27 ms |
| 15 September 2026 | 40 ms | 31 ms | 22 ms | 30 ms | 23 ms | 33 ms |
| 16 September 2026 | 39 ms | 33 ms | 27 ms | 29 ms | 23 ms | 24 ms |
| 17 September 2026 | 50 ms | 33 ms | 22 ms | 37 ms | 23 ms | 28 ms |
| 18 September 2026 | 40 ms | 34 ms | 22 ms | 35 ms | 28 ms | 23 ms |
| 19 September 2026 | 42 ms | 30 ms | 26 ms | 29 ms | 22 ms | 27 ms |
| 20 September 2026 | 43 ms | 29 ms | 22 ms | 40 ms | 25 ms | 22 ms |
| 21 September 2026 | 45 ms | 34 ms | 20 ms | 29 ms | 23 ms | 25 ms |
| 22 September 2026 | 43 ms | 38 ms | 18 ms | 37 ms | 20 ms | 27 ms |
| 23 September 2026 | 41 ms | 24 ms | 20 ms | 37 ms | 33 ms | 36 ms |
| 24 September 2026 | 38 ms | 41 ms | 26 ms | 37 ms | 21 ms | 30 ms |
| 25 September 2026 | 42 ms | 28 ms | 20 ms | 46 ms | 22 ms | 37 ms |
| 26 September 2026 | 38 ms | 27 ms | 20 ms | 33 ms | 27 ms | 33 ms |
| 27 September 2026 | 41 ms | 37 ms | 27 ms | 26 ms | 23 ms | 22 ms |
| 28 September 2026 | 44 ms | 29 ms | 69 ms ▲ | 38 ms | 24 ms | 31 ms |
| 29 September 2026 | 43 ms | 28 ms | 79 ms ▲ | 37 ms | 28 ms | 26 ms |
| 30 September 2026 | 49 ms | 32 ms | 22 ms | 42 ms | 23 ms | 26 ms |
| 1 October 2026 | 42 ms | 29 ms | 20 ms | 32 ms | 25 ms | 31 ms |
| 2 October 2026 | 40 ms | 28 ms | 22 ms | 31 ms | 25 ms | 23 ms |
| 3 October 2026 | 41 ms | 26 ms | 20 ms | 44 ms | 25 ms | 30 ms |
| 4 October 2026 | 38 ms | 25 ms | 21 ms | 46 ms | 21 ms | 23 ms |
| 5 October 2026 | 39 ms | 31 ms | 24 ms | 30 ms | 29 ms | 29 ms |
| 6 October 2026 | 44 ms | 37 ms | 23 ms | 29 ms | 25 ms | 35 ms |
| 7 October 2026 | 39 ms | 32 ms | 19 ms | 41 ms | 24 ms | 39 ms |
| 9 October 2026 | 42 ms | 32 ms | 19 ms | 37 ms | 27 ms | 40 ms |
| 10 October 2026 | 42 ms | 33 ms | 18 ms | 38 ms | 23 ms | 30 ms |
About this measurement
GET unpkg.com/normalize.css@8.0.1/normalize.css · 65 requests per location over 13 daily runs · 27 September 2026 to 10 October 2026
What we tested · Static file. normalize.css 8.0.1 from unpkg.com: 6.1 KB of CSS behind Cloudflare. unpkg ships the unminified file, so it is larger than the cdnjs and jsDelivr copies.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: Minified copies, module or bundle requests, package directory listings, or unpkg's redirect for a version range.
One unpkg surface: normalize.css 8.0.1 from unpkg.com, 6.1 KB of CSS behind Cloudflare. unpkg serves files straight out of npm packages, and here it ships the unminified file, about three times the size of the minified copy on jsDelivr. This is the request a browser makes for a pinned version of a package file.
Between 27 September and 10 October 2026 the typical time was 22 ms in Montreal, 24 ms in Tokyo, 28 ms in Mumbai, 30 ms in San Francisco, 37 ms in Singapore and 42 ms in Amsterdam. The spread is small and mostly steady: Amsterdam's daily median stayed between 38 and 49 ms, and Montreal's between 18 and 27 ms except on 28 and 29 September (69 and 79 ms). Those two days give Montreal the highest slower time on the page, 79 ms, even though it was the fastest city on 9 of the 13 days. No other city's slower time went above 57 ms.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 42 ms | 50 ms | 65 |
| San Francisco | 30 ms | 47 ms | 65 |
| Montreal | 22 ms | 79 ms | 65 |
| Singapore | 37 ms | 57 ms | 65 |
| Tokyo | 24 ms | 36 ms | 65 |
| Mumbai | 28 ms | 53 ms | 65 |
Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics
- Request
- GET unpkg.com/normalize.css@8.0.1/normalize.css
- Measured from
- Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
- Requests
- Daily measurements from 27 September 2026 to 10 October 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 27 September 2026 to 10 October 2026
- Timings taken
- DNS, connect, TLS, waiting for the server, download
- Report coverage
- 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
- Daily requests in each location
- Amsterdam: 65 · San Francisco: 65 · Montreal: 65 · Singapore: 65 · Tokyo: 65 · Mumbai: 65
- Typical response time
- Median of the eligible daily requests in each included location.
- Slower response time
- The 95th percentile of the same eligible daily requests in each included location.
unpkg
https://unpkg.com/normalize.css@8.0.1/normalize.css
Independent measurement by LatencyRadar. Not affiliated with unpkg. · 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.
