Global website speed test

See how fast your page loads for visitors in Seoul, Tokyo, Singapore, Sydney, Virginia, Oregon, Frankfurt and London. A real Chrome browser in each region opens the page twice, first with an empty cache and then as a returning visitor, so you can spot slow regions, missing CDN caching and locations that cannot reach your site. Response time from the US matters for SEO too, because Googlebot and most AI crawlers connect from there.

Runs only this test. Want everything? Run all 18 tests from the home page.

What this test checks

Availability by region

Whether the page loads in each region, with the exact error where it does not: DNS failure, refused connection, timeout, SSL error or redirect loop.

Full load time

Time from navigation start to the load event, measured on a first visit with an empty cache and again on a repeat visit.

Server response (TTFB)

Time from sending the request to the first byte of the response, not counting DNS lookup and connection setup.

DNS and connection time

DNS lookup plus the TCP and TLS handshake in each region, which shows how far visitors are from the server that answers them.

8-region speed grade

An A+ to F grade built from the fastest region, the average of all regions, the slowest region and how many regions load faster on a repeat visit.

US response time

Average server response from US East (Virginia) and US West (Oregon), where Googlebot and most AI crawlers connect from.

CDN and edge cache

Whether a nearby CDN edge server answers in every region, and whether it also serves your HTML from its cache instead of the origin server.

Sample result

A real result for devteam.co.kr, tested 3 hours ago.

Global load speed

Loaded in a real browser from 8 regions worldwide: average load 1.08 s, slowest Frankfurt. From the US, the source of most Googlebot and AI crawler traffic, the server responds in 705 ms. Still needs...

77/100C
US response time (Google & AI crawlers) (Improve)
Responses are slowish from the US, the source of most Googlebot and AI crawler traffic. Google lowers its crawl rate for sites that respond slowly.
705 ms (East 872 ms · West 537 ms)
Target: 0.6s or less
How to fixCaching the HTML of public pages at the CDN edge gets US responses down to tens of milliseconds. Start by cutting server processing time with page caching and faster database queries.
CDN & edge cache (Improve)
The CDN connects visitors to a nearby edge server, but the HTML is fetched from the origin server every time. From London, the first response takes 1.4 s.
CDN (HTML from origin)
Target: First response within 0.8s from any region
How to fixCache the HTML of public pages (no login or cart) at the CDN as well; in Cloudflare, Cache Rules set what is cached and the Edge TTL. Purge a page's cached URL whenever you edit it.
Availability by region (Good)
The page loaded normally in all 8 regions, so crawlers anywhere in the world can read the site.
8/8 regions OK
Target: Loads in every region
Load speed across 8 regions (Good)
Across 8 regions: average server response 622 ms, average full load 1.08 s. Slowest: Frankfurt (1.12 s).
Rated A+ · avg 1.08 s
Target: Rated A or better on the 8-region scale

Full page load by region — first visit and repeat visit

Seoulap-northeast-2
324 ms
Tokyoap-northeast-1
523 ms
Singaporeap-southeast-1
922 ms
Sydneyap-southeast-2
1.22 s
US EastVirginia
1.54 s
US WestOregon
1.11 s
Frankfurteu-central-1
1.39 s
Londoneu-west-2
1.63 s
First visit (empty cache)Repeat visit (cached)

Timing details

RegionDNS + connectServer responseLoadRepeat loadRequests
Seoul ap-northeast-2 29 ms 71 ms 324 ms 249 ms 13
Tokyo ap-northeast-1 100 ms 206 ms 523 ms 361 ms 13
Singapore ap-southeast-1 171 ms 508 ms 922 ms 668 ms 13
Sydney ap-southeast-2 431 ms 557 ms 1.22 s 753 ms 13
US East us-east-1 407 ms 872 ms 1.54 s 937 ms 13
US West us-west-2 317 ms 537 ms 1.11 s 531 ms 13
Frankfurt eu-central-1 30 ms 1.12 s 1.39 s 1.3 s 12
London eu-west-2 301 ms 1.1 s 1.63 s 1.36 s 12

Measured with headless Chrome on 8 AWS regions by Global Website Speed Test. Server response = request sent → first byte (excludes DNS/TCP/TLS); load = navigation start → load event.

How it works

  1. Probe servers in eight AWS regions (Seoul, Tokyo, Singapore, Sydney, US East, US West, Frankfurt and London) load your page in headless Chrome at the same time.
  2. Each probe opens the page twice, first with an empty cache and then as a repeat visit, and reports navigation timings in milliseconds.
  3. Regions appear on the page as they answer, and a full run typically takes about 45 seconds.
  4. A region that cannot load the page within 30 seconds counts as failed, while a probe that is itself offline is left out and does not count against your site.
  5. The 8-region grade uses the same thresholds as Global Website Speed Test (globalwebsitespeedtest.com), so both tools give the same grade.

How it is scored

The test score uses our item-weighted formula: a pass earns full credit, a warning half and a fail none, with availability, the 8-region grade and US response weighted 3× and the CDN check 2×. The 8-region grade is the best grade whose limits are all met for the fastest region, the average, the slowest region and repeat-visit speed-up; the last three rows show the main limits.

CheckGoodNeeds workPoor
Regions that load the pageAll tested regions1 region fails2 or more regions fail
8-region speed gradeA+ or AB or CD or F
US server response (Virginia and Oregon average)0.6 s or less0.6–1.5 sOver 1.5 s
Slowest region, first response (DNS + connect + server)0.8 s or less0.8–1.8 sOver 1.8 s
Average full load, all regions3.5 s or less (A)3.5–5.5 s (B–C)Over 5.5 s (D–F)
Average server response, all regions1.2 s or less (A)1.2–2.0 s (B–C)Over 2.0 s (D–F)
Regions faster on a repeat visit60% or more (A)37.5–59% (B–C)Under 37.5% (D–F)

Grades: A+ 95–100 · A 90–94 · B 80–89 · C 70–79 · D 60–69 · F below 60.

FAQ

How do I test my website speed from different countries?
Enter your URL and run this test. Probe servers in 8 regions across the US, Europe, Asia and Australia load the page in a real Chrome browser at the same time and report load time, server response and connection time for each one. Results appear as each region answers.
What is a good server response time (TTFB)?
For the US check, 0.6 seconds or less is good and anything over 1.5 seconds is poor. For an A on the 8-region grade, the fastest region needs 0.4 seconds or less and the average across all regions 1.2 seconds or less. Our TTFB excludes DNS and connection setup, so it reflects server processing time plus one network round trip.
Why is my website slow in some countries but fast in others?
Without a CDN, every visitor connects to one origin server, so distant regions spend extra time on the TCP and TLS handshake and on every request. The CDN and edge cache check reads the connection timings to tell whether a nearby edge server answers and whether it also caches your HTML. Caching the HTML of public pages at the CDN edge makes the biggest difference for distant regions.
Why does my site fail to load in one region?
The report shows the exact error for each region, such as a DNS failure, refused connection, timeout or SSL certificate error. Common causes are firewall, WAF or country-blocking rules that reject foreign or data-center IP addresses, and DNS that answers differently by region. If one of our probes is unavailable, that region is marked offline and does not count against you.
Why does response time from the US matter for SEO?
Googlebot crawls mainly from US IP addresses, and so do most AI crawlers. Google lowers its crawl rate for hosts that respond slowly or with errors, which can delay indexing of new pages. That is why the test reports a separate US response time from Virginia and Oregon.