One WordPress Build, Seven Hosts, Thirty Days: What the Marketing Pages Never Mention
Photo: Ana Las Heras, CC BY-SA 4.0, via Wikimedia Commons
Every host's homepage has the same numbers: "up to 20x faster," "99.99% uptime," "TTFB under 200ms." These figures come from pristine lab conditions — a single visitor, a warm cache, no competition for resources.
We wanted to know what happens when conditions aren't pristine. So we built one WordPress site — same theme, same plugins, same 40-product WooCommerce catalog, same images — and deployed it across seven popular US hosting providers. Then we ran it for 30 days with synthetic monitoring every five minutes, scripted checkout tests, and one deliberately brutal traffic spike modeled on Black Friday conditions.
The Setup
- Identical build: WordPress 6.x, WooCommerce, same child theme, same image optimization settings
- Same tier: mid-level shared/managed plans at comparable price points ($15–$30/mo range)
- All US-hosted, tested from four US regions (East, West, Central, South)
- Metrics tracked: TTFB, full page load, checkout completion time, support first-response time
TTFB: The Warm Cache Lie
On a cold cache, the spread between the fastest and slowest host was nearly 3x. But here's what surprised us: after a week of warm caches, four of the seven hosts were within 100ms of each other. The differences that remained came down to two things — server-side caching architecture and PHP worker count.
The lesson: most TTFB benchmarks you read are measuring cache hits, not hosting quality. Ask a host what happens when the cache is cold and you'll learn more than any speed-test widget will tell you.
The Traffic Spike Separated the Field
We hit each site with a ramp simulating Black Friday traffic — concurrent users climbing until checkout times degraded past 5 seconds.
- Two hosts folded early, with checkout requests timing out at loads well below what their marketing pages imply
- Three hosts degraded gracefully — slower, but never broken
- Two hosts held steady, largely because they had enough PHP workers to absorb the queue
The pattern was clear: the hosts that survived the spike were the ones that published (and honored) their worker counts. The ones that collapsed were selling "unlimited everything" on oversold infrastructure.
Support: The Test Nobody Runs
We filed identical tickets to each host — a realistic "checkout is intermittently slow" report with diagnostic details attached. Results ranged from excellent to embarrassing:
- Best case: a substantive first response in 40 minutes, with a fix suggestion that actually worked
- Worst case: four days of canned replies, escalating to "have you tried clearing your browser cache"
One host's support agent proactively pulled our slow query logs and identified a plugin conflict before we'd finished describing the problem. That's the difference between a help desk and an operations team.
What We'd Tell You to Ask Instead
Skip the speed-test badges. When evaluating a WordPress host, ask:
- How many PHP workers on my plan, and what happens when they're all busy?
- What's your cold-cache TTFB, not your warm?
- Show me a load test on a WooCommerce checkout, not a static homepage.
- What's your median support first-response time with a real technical fix?
The Bottom Line
Thirty days and seven hosts later, the most expensive plan wasn't automatically the best, and the cheapest wasn't automatically the worst — but the hosts with transparent architecture and competent support consistently outperformed their spec sheets, while the hosts with the loudest marketing consistently underperformed theirs.
Benchmarks tell you how a host behaves on its best day. The spike test and the support ticket tell you how it behaves on your worst day. Choose based on the second one.
