Benchmark report

unpkg thumbnail

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 41 ms.

Fastest
22 ms
Montreal
Slowest
41 ms
Amsterdam
Successful requests
100%
6 locations

Response time around the world

Amsterdam 41ms typicalSan Francisco 32ms typicalMontreal 22ms typicalSingapore 35ms typicalTokyo 23ms typicalMumbai 27ms typical
  • CanadaMontreal
    22 ms
  • JapanTokyo
    23 ms
  • IndiaMumbai
    27 ms
  • United StatesSan Francisco
    32 ms
  • SingaporeSingapore
    35 ms
  • NetherlandsAmsterdam
    41 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 27 September that showed in the connection: 11 ms to connect and 13 ms for the secure handshake from Amsterdam, against 2 to 5 ms and 5 to 8 ms from the other cities. Amsterdam was the slowest of the six on 11 of the 14 days: a small gap, but a steady one, which points to the route rather than a bad day.

Click the location to see each stage.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
48 ms
Finding the server
2 ms
Reaching the server
11 ms
Setting up security
13 ms
Waiting for the server: most of the time
24 ms
Receiving the response
0 ms
Total
48 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 locations

Click a city to see its stage-by-stage breakdown.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
48 ms
Finding the server
2 ms
Reaching the server
11 ms
Setting up security
13 ms
Waiting for the server: most of the time
24 ms
Receiving the response
0 ms
Total
48 ms
United StatesSan Francisco
26 ms
Finding the server
12 ms
Reaching the server
3 ms
Setting up security
8 ms
Waiting for the server: most of the time
14 ms
Receiving the response
1 ms
Total
26 ms
CanadaMontreal
22 ms
Finding the server
1 ms
Reaching the server
5 ms
Setting up security
5 ms
Waiting for the server: most of the time
12 ms
Receiving the response
0 ms
Total
22 ms
SingaporeSingapore
33 ms
Finding the server
7 ms
Reaching the server
3 ms
Setting up security
6 ms
Waiting for the server: most of the time
23 ms
Receiving the response
1 ms
Total
33 ms
JapanTokyo
24 ms
Finding the server
1 ms
Reaching the server
2 ms
Setting up security
8 ms
Waiting for the server: most of the time
13 ms
Receiving the response
1 ms
Total
24 ms
IndiaMumbai
26 ms
Finding the server
2 ms
Reaching the server
3 ms
Setting up security
7 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 27 September 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 18 days

Daily median of 5 requests per location, 9 September 2026 to 27 September 2026.
050100 ms9 Sept27 SeptSingapore, 13 September 2026: 73 ms, well above its usual level.

A dot marks a day well above that location’s usual level.

Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
9 September 202637 ms47 ms22 ms35 ms24 ms39 ms
10 September 202643 ms39 ms27 ms32 ms25 ms30 ms
11 September 202644 ms34 ms25 ms37 ms27 ms31 ms
12 September 202640 ms28 ms27 ms31 ms24 ms25 ms
13 September 202647 ms43 ms28 ms73 ms ▲25 ms31 ms
14 September 202638 ms32 ms24 ms39 ms21 ms27 ms
15 September 202640 ms31 ms22 ms30 ms23 ms33 ms
16 September 202639 ms33 ms27 ms29 ms23 ms24 ms
17 September 202650 ms33 ms22 ms37 ms23 ms28 ms
18 September 202640 ms34 ms22 ms35 ms28 ms23 ms
19 September 202642 ms30 ms26 ms29 ms22 ms27 ms
20 September 202643 ms29 ms22 ms40 ms25 ms22 ms
21 September 202645 ms34 ms20 ms29 ms23 ms25 ms
22 September 202643 ms38 ms18 ms37 ms20 ms27 ms
23 September 202641 ms24 ms20 ms37 ms33 ms36 ms
24 September 202638 ms41 ms26 ms37 ms21 ms30 ms
25 September 202642 ms28 ms20 ms46 ms22 ms37 ms
26 September 202638 ms27 ms20 ms33 ms27 ms33 ms
27 September 202641 ms37 ms27 ms26 ms23 ms22 ms

About this measurement

GET unpkg.com/normalize.css@8.0.1/normalize.css · 70 requests per location over 14 daily runs · 14 September 2026 to 27 September 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.

Not measured: minified copies, ES module or bundle requests, package directory listings, or the redirect unpkg answers with when the URL names a version range instead of an exact version.

Between 14 and 27 September 2026 the typical time was 22 ms in Montreal, 23 ms in Tokyo, 27 ms in Mumbai, 32 ms in San Francisco, 35 ms in Singapore and 41 ms in Amsterdam. The spread is small and steady: Amsterdam's daily median stayed between 38 and 50 ms and Montreal's between 18 and 27 ms, and no city's slower time went above 54 ms.

Test locationTypical response timeSlower response timeRequests
Amsterdam41 ms53 ms20
San Francisco32 ms43 ms20
Montreal22 ms31 ms20
Singapore35 ms54 ms20
Tokyo23 ms34 ms20
Mumbai27 ms40 ms20

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 14 September 2026 to 27 September 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 14 September 2026 to 27 September 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: 70 · San Francisco: 70 · Montreal: 70 · Singapore: 70 · Tokyo: 70 · Mumbai: 70
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.2)

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.

Test my site

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →