Mangesh Supe, Hosting Performance Analyst

By

Founder, ThatMy.com • Independent Hosting Benchmarks • ISP & Network Infrastructure Background


The same WordPress host can deliver 28ms TTFB to a visitor in Virginia and 320ms to a visitor in Sydney. Server location matters as much as server hardware for global audiences. This page documents per-region TTFB measurements for the 5 leading WordPress hosts in the 2026 speed leaderboard, tested from WebPageTest nodes in North America, Europe, Asia, and Australia.

ScalaHosting - Global TTFB Test

Methodology Overview

Each host was tested from four WebPageTest nodes: Dulles (US East), Frankfurt (EU), Singapore (Asia), and Sydney (AU). Tests ran against the same WordPress 6.5 install with identical plugins and a single uncached page request. The numbers below are the median of 9 runs per region, captured between April and May 2026.

Four-step methodology showing WebPageTest nodes, WordPress setup, run count, and median calculation

North America (Dulles, VA)

US East is where every host in this test keeps (or peers closest to) its primary origin, so this column is the fairest read of raw server speed. Rocket.net and WPX lead at 45ms, both serving through their edge networks even on a first request. Cloudways (Vultr HF) follows at 72ms, with Kinsta and ScalaHosting shared at 78ms. ScalaHosting's managed VPS with server-side caching enabled drops to 28ms, the fastest single number we recorded anywhere in this study, but that is a cached response; the shared-plan 78ms is the honest uncached baseline.

HostUS East TTFBSydney TTFBDistance penalty
Rocket.net45ms92ms+47ms
Kinsta78ms195ms+117ms
Cloudways (Vultr HF)72ms210ms+138ms
ScalaHosting (shared)78ms310ms+232ms
WPX45ms320ms+275ms
Average TTFB by Region - Hosting Providers

Europe (Frankfurt)

European results depend almost entirely on whether the host lets you place the origin there. Cloudways can deploy directly to Frankfurt (and London, Amsterdam, Paris) through its cloud providers, which turns the EU from a remote region into a home region. Kinsta offers Google Cloud's Frankfurt and Netherlands regions the same way. ScalaHosting operates an EU datacenter alongside its US locations, so EU-majority sites can flip the geography entirely. Rocket.net leans on its Cloudflare Enterprise edge, which serves cached pages from EU POPs regardless of where the origin sits. WPX routes through its custom CDN's European locations. For a US-origin setup, expect Frankfurt numbers to land between the US East and Sydney extremes in the table above, closer to the US figure for edge-cached hosts, closer to Sydney for single-origin hosts. Per-node Frankfurt medians land in the next research pass.

Asia (Singapore)

Asia is the hardest region for US-origin WordPress: the trans-Pacific round trip is unforgiving on uncached requests. The pattern from the Sydney column applies with slightly smaller penalties, Singapore sits one hop closer to US West than Sydney does. Hosts with a real Asian presence change the math: Cloudways deploys origins in Singapore directly, Kinsta offers Google Cloud's Singapore and Taiwan regions, and the edge-cache hosts (Rocket.net, WPX) serve cached HTML from Asian POPs at near-local speed. If Asia is your primary audience, pick a host that puts the origin there rather than relying on a CDN to hide the distance. Per-node Singapore medians land in the next research pass.

Australia (Sydney)

Sydney is the stress test: it is the farthest common test node from US East and it exposes exactly how each host handles distance. Rocket.net holds the penalty to +47ms (45→92ms) because its edge network serves from Australia. Kinsta (+117ms) and Cloudways (+138ms) degrade in line with a single well-peered origin. ScalaHosting (+232ms) and WPX (+275ms) show what an origin with no Australian edge presence looks like from Sydney, over 300ms TTFB before the page even starts rendering. If Australian visitors matter to you, either deploy the origin in Sydney (Cloudways and Kinsta both offer it) or use a host whose edge cache has Australian POPs.

Dumbbell chart showing TTFB spread from US East to Sydney for five WordPress hosts

Practical Takeaways

If more than 40% of your traffic comes from one region, your origin server should be in or near it. A CDN can mitigate the gap for cacheable pages but will not help dynamic requests like WooCommerce checkout or logged-in WordPress admin. The Cloudways and Kinsta regional networks are the most flexible for distributed audiences; ScalaHosting has US and EU; Rocket.net uses an edge cache to compensate for fewer origin locations.

Do and don't guidance for choosing CDN or origin server placement based on traffic type

Back to the full speed comparison: Fastest WordPress Hosting 2026.