In my November 2026 tests of 15 real WordPress sites, Kinsta had the fastest servers among managed WordPress hosts, at 227 ms to build an uncached page. It was also the only host here to get an A in the heavy load test, with up to 50 visitors at once.

Rank Host Server time (est.) Uncached TTFB Cached TTFB Under load Rating
1 Kinsta logo Kinsta 227 ms 229 ms 22 ms A (241 ms at 40-50 users, 2 sites) A
2 Nexcess (Liquid Web) logo Nexcess (Liquid Web) 615 ms 634 ms 358 ms B (767 ms at 40-50 users, 2 sites) B
3 WP Engine logo WP Engine 862 ms 1,045 ms 369 ms B (666 ms at 40-50 users, 2 sites) C
4 Cloudways logo Cloudways 1,141 ms 1,163 ms 44 ms E (stopped at 25-42 users, 6 sites) D
5 WPX Hosting logo WPX Hosting 1,395 ms 1,397 ms 161 ms E (stopped at 30-32 users, 2 sites) E

Every figure is the median of up to 3 live customer sites per host, tested with Grafana k6 from Ashburn, US, with the same method as my main web hosting benchmarks. These are real-world sites with their own themes and plugins, not identical test sites on accounts I bought, so read the results as a snapshot of sites on each host.

Only 5 managed WordPress hosts are ranked so far, so the grades compare these 5 with each other. A C or D here can still be a fast host next to shared hosting; it only means the others were faster in this group.

Key findings

  • Kinsta was fastest on the server: a median of 227 ms server time, and 22 ms for cached pages through its built-in Cloudflare edge.
  • Built-in caching hides slow servers. WPX Hosting needed 1,395 ms to build an uncached page but delivered cached pages in 161 ms. Cloudways did the same: 1,141 ms uncached, 44 ms cached.
  • Distance matters for WP Engine's sites: all three are on servers in Taiwan, so each request had about 183 ms of travel time from Ashburn before the server started. Server time removes that, which is why WP Engine ranks on 862 ms, not 1,045 ms.
  • Under load, the gap is wide: Kinsta stayed under 300 ms at 40 to 50 visitors (grade A), WP Engine and Nexcess under 0.8 s (B), while 5 of 6 Cloudways sites and both WPX sites had to be stopped (E). Cloudways customers choose their server size, and these sites ran on small servers.
  • Nexcess's page cache didn't answer on 2 of its 3 sites, so their cached and uncached times were almost the same (358 ms cached). Its server time is still second best.

Ranking: server time

Server time is the uncached time to first byte minus the network round trip from Ashburn, so a host with servers far from the US isn't penalised for distance. It's the closest measure of how fast the server builds a WordPress page when no cache can help, as happens with carts, searches, logged-in visitors and the first visit after a change.

Server time by managed WordPress host, lower is faster

15 real WordPress sites tested with k6 from Ashburn, US · median of up to 3 sites · bar colour = grade among these 5 hosts

  • Grade A
  • Grade B
  • Grade C
  • Grade D
  • Grade E

Server time = uncached TTFB minus the network round trip. Hover or tap a bar for its details.

Rank Host Sites Server time (est.) Fastest site Slowest site Server location Grade
1 Kinsta logo Kinsta 3 227 ms 150 ms 703 ms hidden behind Cloudflare A
2 Nexcess (Liquid Web) logo Nexcess (Liquid Web) 3 615 ms 359 ms 1,265 ms United States B
3 WP Engine logo WP Engine 3 862 ms 453 ms 4,642 ms Taiwan C
4 Cloudways logo Cloudways 3 1,141 ms 506 ms 1,151 ms Canada D
5 WPX Hosting logo WPX Hosting 3 1,395 ms 228 ms 1,771 ms United States, hidden behind WPX Cloud E

WP Engine's slowest site took 4,642 ms, 5 to 10 times as long as its other two, and WPX's sites ranged from 228 ms to 1,771 ms. On managed hosting the plan and the site itself still matter: a heavy theme or plugin stack slows down any host.

Cached and uncached: what built-in caching does

Managed WordPress hosts include a page cache or CDN that every customer gets, so the cached figure counts as the host's real-world speed here. I show it next to the uncached figure, because the uncached one is what visitors get on pages a cache can't serve.

Host Built-in cache or CDN Uncached TTFB Cached TTFB Cached share of uncached
Kinsta logo Kinsta Cloudflare edge cache (built in) 229 ms 22 ms 10%
Cloudways logo Cloudways Varnish/Breeze server cache (built in) 1,163 ms 44 ms 4%
WPX Hosting logo WPX Hosting WPX Cloud CDN (built in, optional) 1,397 ms 161 ms 11%
Nexcess (Liquid Web) logo Nexcess (Liquid Web) server cache (built in) 634 ms 358 ms 56%
WP Engine logo WP Engine EverCache server cache (built in) 1,045 ms 369 ms 35%

Both columns are measured from Ashburn and include the trip to the server or edge. Kinsta's cached pages come from Cloudflare's edge near the test, so they don't travel to the origin at all. WP Engine's cached pages still travel to Taiwan, so about 183 ms of its 369 ms is distance. On WPX, one of the three sites used the WPX Cloud CDN; the other two were served from WPX's LiteSpeed servers.

Slowest 5% of requests

This shows how steady each host was: the uncached server time that 95% of requests beat during the light 2-minute test.

Host Slowest 5% server time Grade
Kinsta logo Kinsta 323 ms A
Nexcess (Liquid Web) logo Nexcess (Liquid Web) 689 ms B
WP Engine logo WP Engine 958 ms C
Cloudways logo Cloudways 1,491 ms D
WPX Hosting logo WPX Hosting 1,720 ms E

Under load: 1 to 50 visitors

For all five hosts I also ran a heavier test on 2 or more sites that I have permission to test: k6 raised the visitors from 1 to 50 over 2 minutes, and every request skipped the page cache. Grades use fixed limits on server time at 40 to 50 visitors: A under 0.5 s, B under 1 s, C under 2 s, D under 4 s, E 4 s or more, more than 1% failed requests, or a test k6 had to stop.

Host Sites Server time at 1-10 users At 40-50 users Grade
Kinsta logo Kinsta 2 211 ms 241 ms A
WP Engine logo WP Engine 2 660 ms 666 ms B
Nexcess (Liquid Web) logo Nexcess (Liquid Web) 2 653 ms 767 ms B
Cloudways logo Cloudways 6 1,499 ms test stopped at 25-42 users E
WPX Hosting logo WPX Hosting 2 2,377 ms test stopped at 30-32 users E

The Cloudways sites run on servers their owners chose, two of them on a 1 vCPU, 2 GB RAM server shared with 8 other WordPress sites, so that grade reflects small Cloudways servers as much as Cloudways. The full results and charts per site are in the Cloudways, WP Engine and WPX Hosting reviews.

How I tested

The method is the same as on the main benchmarks page:

  • Tool and location: Grafana k6 from Grafana Cloud's Ashburn, US load zone, 5 virtual users at most 1 request per second, 2 minutes per site, in November 2026.
  • Cached and uncached: every other request added a random query string, so it skipped the page cache and the server had to build the page.
  • Sites: live WordPress sites whose hosting I verified (headers, DNS and network checks), with a dynamic homepage of 30 to 500 KB. Sites behind a CDN their owner added in front of the host are left out; a CDN the host includes for every customer counts.
  • Excluded runs: runs with more than 10% failed or blocked requests, and sites where the cache still answered the uncached requests.
  • Grades: the 5 hosts are split into five groups by server time and by slowest 5% server time; the load test uses the fixed limits above. The rating is the average of a host's grades.

Which hosts are on this page

Kinsta, WP Engine and Nexcess are managed WordPress platforms. Cloudways is managed cloud hosting where most customers run WordPress, and all its tested sites are WordPress sites. WPX sells managed WordPress hosting; on the main benchmarks page it is ranked with shared hosting, because its plans share servers between customers. Wix is ranked as managed hosting on the main page but isn't WordPress, so it isn't here.

What these results don't tell you

  • Plans are unknown. For sites I don't own, I can't see the plan, the server size (on Cloudways) or the site's plugins, and all of them change the result.
  • One round of tests. Each site was tested once on one day; a busy or quiet moment can move a result.
  • Up to 3 sites per host. That's enough to spot a pattern, not to describe every server a host runs.
  • Speed isn't everything. Support, backups, staging and price matter as much on managed hosting; the reviews cover those.

FAQ

Which managed WordPress host is the fastest?

In this round, Kinsta had the lowest server time (227 ms) and the best load grade (A). Each figure comes from up to 3 real sites, so the order can change between rounds.

Does a built-in CDN make a host faster?

For pages the cache can serve, yes: Kinsta's and Cloudways' cached pages arrived in under 50 ms from Ashburn. It doesn't help pages the cache can't serve, such as carts, checkouts and logged-in pages, which is why I rank on uncached server time.

Why is WP Engine ranked third when its sites are in Taiwan?

The ranking removes the network round trip, so the distance from Ashburn to Taiwan doesn't count against it. Its server time was slower than Kinsta's and Nexcess's, and one of its three sites was much slower than the other two.

Is managed WordPress hosting faster than shared hosting?

Not always. On the main benchmarks page, the median managed host was slower on uncached pages than the median shared host. What managed hosts usually add is caching, staging, backups and WordPress-specific support, plus steadier results under load on the better platforms.

How often are these results updated?

I retest when I add hosts or sites, and every result keeps its test date. More managed WordPress hosts will join this page as I verify their sites.