Most WordPress speed comparisons are sponsored posts dressed up as benchmarks. A host pays for a review slot, the reviewer runs a single Pingdom test on a hello-world install, and suddenly that host is "the fastest on the market." I've been burned by that before — back when I was managing 200+ sites for an agency, a bad hosting decision meant 2 a.m. pages and client churn.
So when I set out to find the best WordPress hosting for speed in 2024, I used the same staging-to-production pipeline I built at the agency: identical WordPress 6.5 installs, identical themes (Kadence with no page builder), identical WooCommerce product catalogs (500 SKUs), and a k6 load test script that simulates 50 concurrent users for 5 minutes. No vendor-supplied demo sites. No synthetic "up to" numbers.
This article covers what I found — which hosts are genuinely fast, which ones rely on marketing smoke, and what you should actually do with this information.
How I Ran the Tests
Every host got the same setup:
- WordPress 6.5 with Kadence theme (free tier)
- WooCommerce 8.9 with 500 products, imported via WP All Import
- No caching plugins on the first pass (to measure raw server performance)
- Object caching enabled on the second pass (Redis or Memcached, whichever the host provides natively)
- PHP 8.2 where available, PHP 8.1 as fallback
- Test region: US East (closest to most hosts' primary data centers)
Metrics I cared about: Time to First Byte (TTFB), Largest Contentful Paint (LCP) from WebPageTest, and p95 response time under the k6 load (50 VUs, 300 seconds).
I tested five hosts over four weeks in April–May 2024: Kinsta, WP Engine, Cloudways (DigitalOcean 2GB), Rocket.net, and SiteGround GoGeek. Prices below reflect plans closest to $30–$50/month to keep the comparison fair.
The Benchmark Results
Here's the summary table. All TTFB figures are medians across 10 WebPageTest runs from Dulles, VA.
| Host | Plan ($/mo) | TTFB (no cache) | TTFB (with cache) | p95 @ 50 VUs | LCP (ms) |
|---|---|---|---|---|---|
| Kinsta | $35 (Starter) | 310 ms | 48 ms | 190 ms | 1,820 |
| Rocket.net | $30 (Personal) | 280 ms | 41 ms | 165 ms | 1,640 |
| Cloudways DO 2GB | $26 | 340 ms | 62 ms | 220 ms | 2,010 |
| WP Engine | $30 (Starter) | 390 ms | 55 ms | 245 ms | 2,180 |
| SiteGround GoGeek | $44.99 (renewal) | 480 ms | 88 ms | 310 ms | 2,650 |
A few things stand out immediately. Rocket.net beat Kinsta on every raw metric — which surprised me, because Kinsta's marketing is almost entirely built around speed. WP Engine's cached TTFB was competitive, but its uncached numbers were the worst of the "premium" tier. And SiteGround's renewal pricing at $44.99/month is genuinely hard to justify when it's the slowest of the five.
Why Rocket.net Came Out on Top
Rocket.net runs every site behind Cloudflare's Enterprise network — not the free or Pro tier, the actual Enterprise tier with Argo Smart Routing baked in. That's the infrastructure reason their TTFB is low. But the more interesting part is their full-page caching implementation: it's aggressive by default, and it handles WooCommerce cart and checkout exclusions correctly out of the box without you touching a config file.
I deliberately tested with a logged-in WooCommerce customer adding items to cart, which breaks caching on most hosts unless you configure exclusions manually. Rocket.net handled it cleanly. Kinsta required me to add wp-json and wc-ajax exclusion rules to the Nginx cache config — doable, but extra work.
The $30/month Personal plan limits you to one site and 50k monthly visitors. That's a real constraint. If you're running a multi-site agency setup, you'll be looking at their $125/month Agency plan, which changes the value calculation significantly.
Kinsta: Still Excellent, Just Not the Cheapest
Kinsta runs on Google Cloud Platform's C2 compute-optimized instances. Their infrastructure is genuinely good. The 48 ms cached TTFB is real — I reproduced it consistently — and their MyKinsta dashboard is the best control panel in this comparison by a wide margin.
Where Kinsta loses ground is raw uncached performance and price-to-performance ratio. At $35/month for the Starter plan, you get one WordPress install and 25k monthly visits. Rocket.net's $30 plan gives you 50k visits. And Kinsta's CDN (powered by Cloudflare, ironically) is an add-on that costs $0.10/GB after the first 100 GB — which adds up for media-heavy sites.
If you're already paying for Kinsta and it's working, I wouldn't switch just for a 7 ms TTFB difference. But if you're evaluating fresh, the numbers don't justify the premium over Rocket.net unless you specifically need Kinsta's staging workflow or their APM tooling.
Cloudways: Best Value if You're Comfortable with Configuration
Cloudways at $26/month (DigitalOcean 2GB droplet) is the most configurable option here. You get Redis object caching, Varnish, and Nginx FastCGI cache — all available, none of it fully automated. The 62 ms cached TTFB is solid. The 340 ms uncached TTFB reflects DigitalOcean's infrastructure, which is good but not GCP or Cloudflare-grade.
The real advantage of Cloudways is flexibility. You can switch to Vultr High Frequency (which in my separate tests shaved about 30 ms off TTFB) or AWS for the same control panel. You can also install custom Nginx rules, which matters for WooCommerce performance tuning.
Here's the Redis object cache config I use on Cloudways — drop this in wp-config.php after Cloudways enables Redis:
// Redis object cache — Cloudways
define( 'WP_REDIS_HOST', '127.0.0.1' );
define( 'WP_REDIS_PORT', 6379 );
define( 'WP_REDIS_TIMEOUT', 1 );
define( 'WP_REDIS_READ_TIMEOUT', 1 );
define( 'WP_REDIS_DATABASE', 0 );
Then install the Redis Object Cache plugin and hit "Enable Object Cache" in the plugin settings. That alone dropped my p95 response time from 310 ms to 220 ms on the Cloudways setup.
The downside: Cloudways has no built-in WordPress-specific features like automatic plugin update staging or one-click restore points. You're building those workflows yourself or paying for the Cloudways Bot add-on ($4/month per app).
WP Engine: Good Infrastructure, Frustrating Restrictions
WP Engine's uncached TTFB of 390 ms was the worst of the premium hosts. That's partly because their proprietary EverCache system is optimized for cached delivery — it's genuinely fast at 55 ms cached — but the uncached path goes through more middleware layers than competitors.
More frustrating: WP Engine blocks 35+ plugins by default, including some object caching plugins and certain security tools. You can see their current blocked plugin list in their support docs. I hit this restriction when I tried to install a custom Redis client — blocked. That kind of restriction is acceptable on a $10/month shared host. At $30/month, it's irritating.
WP Engine does have the best automated migration tool I've tested, and their 24/7 support response times were consistently under 3 minutes in my tests. If support responsiveness is your top priority, that matters. For raw speed, it's third in this group.
SiteGround: Avoid at Renewal Pricing
SiteGround's GoGeek plan is $6.99/month introductory, $44.99/month on renewal. At the renewal price, it's the most expensive option in my test and the slowest. Their SG Optimizer plugin is well-built, and their Ultrafast PHP implementation (based on SWOOLE) is interesting in theory. In practice, the 88 ms cached TTFB and 310 ms p95 under load don't compete with the other four.
I tested on SiteGround's US East data center. Their European data centers may perform differently for EU-based audiences. But for US traffic, paying $44.99/month renewal for these numbers is hard to defend when Cloudways gives you better performance at $26/month.
If you're on SiteGround's introductory pricing and your site isn't under heavy load, it's fine. The moment your renewal hits, re-evaluate.
What Actually Moves the Needle on WordPress Speed
The host matters, but it's not the only variable. Here's what I consistently found makes the biggest difference, in rough order of impact:
- Full-page caching — The gap between cached and uncached TTFB is 5–10x across every host I tested. If your host doesn't have server-level caching, you're leaving the biggest win on the table.
- PHP 8.2 vs 8.1 — Switching from PHP 8.1 to 8.2 dropped median response time by 8–12% in my WooCommerce tests. Always use the latest stable PHP version your plugins support.
- Object caching (Redis/Memcached) — Especially important for WooCommerce and membership sites with lots of database reads. On Cloudways, enabling Redis dropped my database query time by ~40%.
- CDN proximity — Rocket.net's Cloudflare Enterprise advantage is real for global audiences. For a US-only site, it matters less.
- Image optimization — Not the host's job, but unoptimized images will negate any hosting speed advantage. I use Cloudflare Images or ShortPixel; both work well.
For a deeper look at the caching layer specifically, see my post on WordPress caching strategies — it covers when to use full-page cache vs object cache vs fragment caching, with config examples for each major host.
If you're running WooCommerce specifically, the database optimization side of performance is just as important as the hosting layer. My WooCommerce performance optimization guide covers index tuning and query caching in detail.
The Bottom Line
For the best WordPress hosting for speed at the $30/month price point, Rocket.net is my current recommendation — better TTFB, better LCP, and Cloudflare Enterprise included without extra configuration. Kinsta is a close second with a better dashboard and more mature tooling. Cloudways wins on value and flexibility if you're willing to configure it properly.
WP Engine is solid but overpriced for what you get on the Starter plan. SiteGround at renewal pricing is a bad deal.
What to do tomorrow: If you're not sure what your current host's TTFB looks like, run your site through WebPageTest from the Dulles, VA location right now. If your cached TTFB is above 200 ms, your host is the bottleneck — not your theme, not your plugins. That's the number to fix first.