Benchmark report
Is shopify.com slow?
Homepage load times from 5 cities
Fast globally
Shopify responds quickly from all 5 test locations. Tokyo was fastest at 58 ms; Amsterdam took 86 ms.
- Fastest
- 58 ms
- Tokyo
- Slowest
- 86 ms
- Amsterdam
- Successful requests
- 100%
- 5 of 6 locations
Response time around the world
Tokyo58 ms
Singapore60 ms
San Francisco62 ms
Montreal67 ms
Amsterdam86 ms
MumbaiCollecting since 7 Sept 2026
Amsterdam’s download, and one bad evening in Asia
In the controlled run of 7 September the median request finished in 42 to 83 ms in every city. Connecting took 2 to 9 ms, the TLS handshake 5 to 11 ms, the wait for the first byte 25 to 37 ms and the download of 700 KB 5 to 34 ms. Amsterdam was the slowest city at 83 ms: its download took 34 ms against 5 to 9 ms elsewhere, and its cache header named London rather than a Dutch point of presence. The slower times for Singapore (405 ms) and Tokyo (284 ms) are the median of two controlled runs that disagreed sharply. On 30 August the slower time was 562 ms in Singapore and 507 ms in Tokyo; on 7 September it was 248 and 61 ms. The daily medians in those two cities never left 48 to 93 ms, so the tail describes one evening rather than the usual visit.
Click the location to see each stage.
Amsterdam83 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 9 ms
- Setting up security
- 11 ms
- Waiting for the server
- 29 ms
- Receiving the response: most of the time
- 34 ms
- Total
- 83 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.
Amsterdam83 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 9 ms
- Setting up security
- 11 ms
- Waiting for the server
- 29 ms
- Receiving the response: most of the time
- 34 ms
- Total
- 83 ms
San Francisco57 ms
San Francisco- Finding the server
- 51 ms
- Reaching the server
- 4 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 37 ms
- Receiving the response
- 9 ms
- Total
- 57 ms
Montreal51 ms
Montreal- Finding the server
- 5 ms
- Reaching the server
- 2 ms
- Setting up security
- 7 ms
- Waiting for the server: most of the time
- 37 ms
- Receiving the response
- 5 ms
- Total
- 51 ms
Singapore42 ms
Singapore- Finding the server
- 6 ms
- Reaching the server
- 3 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 25 ms
- Receiving the response
- 9 ms
- Total
- 42 ms
Tokyo53 ms
Tokyo- Finding the server
- 5 ms
- Reaching the server
- 2 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 35 ms
- Receiving the response
- 8 ms
- Total
- 53 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
Shopify still feels slow?
- Check Shopify’s status page
- Incidents with the platform, storefronts and checkout are posted there. The marketing homepage can be fine while a store is not.
- This is not a storefront benchmark
- Merchant storefronts, checkout, the admin and the Storefront and Admin APIs are different systems from the marketing homepage measured here.
- Served through Cloudflare
- Two Cloudflare addresses across our five cities in the controlled run, each city answered from a nearby point of presence; Amsterdam's was London. Which edge serves your visitors depends on where they are.
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 | 115 ms | 119 ms | 47 ms | 274 ms ▲ | 54 ms | — |
| 28 August 2026 | 85 ms | 68 ms | 45 ms | 56 ms | 50 ms | — |
| 29 August 2026 | 84 ms | 85 ms | 44 ms | 51 ms | 58 ms | — |
| 30 August 2026 | 79 ms | 65 ms | 105 ms ▲ | 59 ms | 52 ms | — |
| 31 August 2026 | 88 ms | 71 ms | 103 ms | 67 ms | 60 ms | — |
| 1 September 2026 | 81 ms | 61 ms | 179 ms ▲ | 59 ms | 56 ms | — |
| 2 September 2026 | 87 ms | 63 ms | 43 ms | 57 ms | 68 ms | — |
| 3 September 2026 | 92 ms | 62 ms | 48 ms | 57 ms | 56 ms | — |
| 4 September 2026 | 94 ms | 56 ms | 40 ms | 60 ms | 56 ms | — |
| 5 September 2026 | 96 ms | 59 ms | 188 ms ▲ | 61 ms | 55 ms | — |
| 6 September 2026 | 84 ms | 61 ms | 190 ms ▲ | 57 ms | 56 ms | — |
| 7 September 2026 | 92 ms | 63 ms | 178 ms ▲ | 93 ms | 52 ms | 63 ms |
| 8 September 2026 | 80 ms | 59 ms | 37 ms | 59 ms | 55 ms | 98 ms |
| 9 September 2026 | 78 ms | 65 ms | 74 ms | 48 ms | 61 ms | 59 ms |
| 10 September 2026 | 87 ms | 52 ms | 52 ms | 74 ms | 60 ms | 77 ms |
| 11 September 2026 | 84 ms | 67 ms | 66 ms | 65 ms | 66 ms | 63 ms |
| 12 September 2026 | 88 ms | 51 ms | 53 ms | 73 ms | 63 ms | 61 ms |
About this measurement
GET www.shopify.com · 70 requests per location over 14 daily runs · 30 August 2026 to 12 September 2026
What we tested · Marketing website. The www.shopify.com marketing homepage, about 700 KB of HTML fronted by Cloudflare.
How LatencyRadar measures response time →
Technical details
Doesn’t measure: A merchant's storefront, checkout, the admin, or the Storefront and Admin APIs.
One Shopify surface: the www.shopify.com marketing homepage, about 700 KB of HTML that Shopify serves through Cloudflare. It is the page a prospective merchant lands on, and it shows how Shopify's public site answers a cold request from each of our cities. It does not stand for a store: merchant storefronts run on Shopify's storefront infrastructure with their own themes and apps, and checkout, the admin and the Storefront and Admin APIs are different systems again.
Not measured: any merchant's storefront, checkout, the admin, the Storefront and Admin APIs, or anything a browser does after the HTML arrives. From outside we cannot tell whether Cloudflare's edge or Shopify's origin answered a given request, so a slow run may be a cache miss, a deploy, or the path between our worker and the edge.
Between 30 August and 12 September 2026 the typical time ranged from 58 ms in Tokyo to 86 ms in Amsterdam. Amsterdam's requests were answered from a London point of presence, and its download of the 700 KB took 34 ms in the controlled run against 5 to 9 ms elsewhere. Montreal's typical is 67 ms, but its daily median jumped to 103 to 190 ms from 30 August to 1 September and from 5 to 7 September. The same days appear on the Docker Hub and GitLab pages, also fronted by Cloudflare, which suggests the cause was between our Montreal worker and Cloudflare rather than at Shopify. The slower times in Asia, 405 ms in Singapore and 284 ms in Tokyo, come from a single controlled run on 30 August; the daily medians there stayed between 48 and 93 ms.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 86 ms | 109 ms | 20 |
| San Francisco | 62 ms | 88 ms | 20 |
| Montreal | 67 ms | 96 ms | 20 |
| Singapore | 60 ms | 405 ms | 20 |
| Tokyo | 58 ms | 284 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.shopify.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.
Shopify
https://www.shopify.com/
Independent measurement by LatencyRadar. Not affiliated with Shopify. · 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.
