Benchmark report
Is shopify.com slow?
Homepage load times from 6 cities
Fast globally
Shopify responds quickly from all 6 test locations. Montreal was fastest at 52 ms; Amsterdam took 94 ms.
- Fastest
- 52 ms
- Montreal
- Slowest
- 94 ms
- Amsterdam
- Successful requests
- 100%
- 6 locations
Response time around the world
Montreal52 ms
Tokyo54 ms
Mumbai59 ms
San Francisco63 ms
Singapore76 ms
Amsterdam94 ms
Amsterdam’s download, and a tail in Asia
In the controlled run of 4 October the median request finished in 50 to 91 ms in every city. Connecting took 2 to 7 ms, the TLS handshake 5 to 12 ms, the wait for the first byte 36 to 49 ms and the download of 700 KB 4 to 8 ms in five cities. Amsterdam was the slowest city at 91 ms: its download took 28 ms, and its cache header named London rather than a Dutch point of presence. The slowest 5% of requests look different in Singapore: 259 ms, against 64 to 106 ms in the other five cities. Across the two weeks Singapore's slower time was 306 ms, while its daily medians stayed between 59 and 111 ms.
Click the location to see each stage.
Amsterdam91 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 7 ms
- Setting up security
- 12 ms
- Waiting for the server: most of the time
- 44 ms
- Receiving the response
- 28 ms
- Total
- 91 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.
Amsterdam91 ms
Amsterdam- Finding the server
- 1 ms
- Reaching the server
- 7 ms
- Setting up security
- 12 ms
- Waiting for the server: most of the time
- 44 ms
- Receiving the response
- 28 ms
- Total
- 91 ms
San Francisco56 ms
San Francisco- Finding the server
- 17 ms
- Reaching the server
- 4 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 37 ms
- Receiving the response
- 7 ms
- Total
- 56 ms
Montreal50 ms
Montreal- Finding the server
- 2 ms
- Reaching the server
- 2 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 39 ms
- Receiving the response
- 4 ms
- Total
- 50 ms
Singapore71 ms
Singapore- Finding the server
- 7 ms
- Reaching the server
- 3 ms
- Setting up security
- 11 ms
- Waiting for the server: most of the time
- 49 ms
- Receiving the response
- 8 ms
- Total
- 71 ms
Tokyo51 ms
Tokyo- Finding the server
- 5 ms
- Reaching the server
- 3 ms
- Setting up security
- 5 ms
- Waiting for the server: most of the time
- 36 ms
- Receiving the response
- 7 ms
- Total
- 51 ms
Mumbai58 ms
Mumbai- Finding the server
- 11 ms
- Reaching the server
- 3 ms
- Setting up security
- 8 ms
- Waiting for the server: most of the time
- 41 ms
- Receiving the response
- 6 ms
- Total
- 58 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
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 six 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 29 days
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 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 |
| 13 September 2026 | 85 ms | 57 ms | 59 ms | 59 ms | 55 ms | 59 ms |
| 14 September 2026 | 81 ms | 67 ms | 47 ms | 62 ms | 52 ms | 56 ms |
| 15 September 2026 | 72 ms | 31 ms | 22 ms | 49 ms | 27 ms | 30 ms |
| 16 September 2026 | 93 ms | 66 ms | 60 ms | 60 ms | 57 ms | 61 ms |
| 17 September 2026 | 82 ms | 60 ms | 43 ms | 69 ms | 71 ms | 74 ms |
| 18 September 2026 | 87 ms | 63 ms | 57 ms | 89 ms | 58 ms | 44 ms |
| 19 September 2026 | 86 ms | 58 ms | 59 ms | 66 ms | 45 ms | 55 ms |
| 20 September 2026 | 88 ms | 67 ms | 51 ms | 86 ms | 51 ms | 54 ms |
| 21 September 2026 | 89 ms | 63 ms | 54 ms | 68 ms | 59 ms | 57 ms |
| 22 September 2026 | 103 ms | 67 ms | 50 ms | 66 ms | 55 ms | 61 ms |
| 23 September 2026 | 87 ms | 79 ms | 51 ms | 71 ms | 53 ms | 46 ms |
| 24 September 2026 | 102 ms | 70 ms | 40 ms | 64 ms | 48 ms | 72 ms |
| 25 September 2026 | 84 ms | 54 ms | 33 ms | 74 ms | 77 ms | 69 ms |
| 26 September 2026 | 86 ms | 56 ms | 45 ms | 58 ms | 43 ms | 44 ms |
| 27 September 2026 | 80 ms | 56 ms | 48 ms | 66 ms | 67 ms | 57 ms |
| 28 September 2026 | 89 ms | 70 ms | 51 ms | 69 ms | 49 ms | 58 ms |
| 29 September 2026 | 79 ms | 71 ms | 52 ms | 70 ms | 63 ms | 64 ms |
| 30 September 2026 | 94 ms | 62 ms | 60 ms | 59 ms | 58 ms | 56 ms |
| 1 October 2026 | 102 ms | 60 ms | 46 ms | 75 ms | 49 ms | 64 ms |
| 2 October 2026 | 91 ms | 60 ms | 60 ms | 68 ms | 50 ms | 69 ms |
| 3 October 2026 | 102 ms | 52 ms | 44 ms | 67 ms | 45 ms | 59 ms |
| 4 October 2026 | 95 ms | 55 ms | 57 ms | 91 ms | 63 ms | 50 ms |
| 5 October 2026 | 91 ms | 59 ms | 51 ms | 77 ms | 51 ms | 63 ms |
| 6 October 2026 | 96 ms | 85 ms | 59 ms | 89 ms | 57 ms | 67 ms |
| 7 October 2026 | 91 ms | 73 ms | 52 ms | 77 ms | 48 ms | 108 ms |
| 9 October 2026 | 109 ms | 80 ms | 53 ms | 111 ms | 54 ms | 86 ms |
| 10 October 2026 | 93 ms | 71 ms | 50 ms | 74 ms | 55 ms | 53 ms |
About this measurement
GET www.shopify.com · 65 requests per location over 13 daily runs · 27 September 2026 to 10 October 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.
Between 27 September and 10 October 2026 the typical time ranged from 52 ms in Montreal to 94 ms in Amsterdam, with Tokyo at 54 ms, Mumbai at 59 ms, San Francisco at 63 ms and Singapore at 76 ms. Amsterdam's requests were answered from a London point of presence, and its download of the 700 KB took 28 ms in the controlled run against 4 to 8 ms elsewhere. No daily median left 44 to 111 ms. The highest were Mumbai at 108 ms on 7 October and Amsterdam and Singapore at 109 and 111 ms on 9 October. 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. Singapore's slower time, 306 ms, is about four times its typical; in the other cities it stays between 87 and 119 ms. The Docker Hub and GitLab APIs sit behind Cloudflare too and are measured on the same days.
| Test location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 94 ms | 114 ms | 65 |
| San Francisco | 63 ms | 101 ms | 65 |
| Montreal | 52 ms | 95 ms | 65 |
| Singapore | 76 ms | 306 ms | 65 |
| Tokyo | 54 ms | 87 ms | 65 |
| Mumbai | 59 ms | 119 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 www.shopify.com
- 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.
- Coverage changes
- Mumbai (measured since 7 September 2026) joined this report on 21 September 2026. Earlier daily bands keep their previous location set.
- 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.
Shopify
https://www.shopify.com/
Independent measurement by LatencyRadar. Not affiliated with Shopify. · 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.
