Every "best WordPress hosting" article you've read is probably funded by affiliate commissions. The provider paying the highest commission gets the top spot, regardless of actual performance. Which is why the useful thing is not another ranking — it is a method you can run yourself, on the shortlist you actually care about.
This article is that method: the test site to deploy, the four numbers worth measuring, the three support tickets to send, and what each hosting tier looks like once you have the numbers in front of you. Run it on three providers over a fortnight and you will know more than any ranking can tell you.
The Test Protocol
A comparison is only worth anything if the only thing that differs between providers is the provider. Control these:
The Test Site
Deploy an identical WordPress installation on every provider on your shortlist. Something like:
- WordPress 6.7 (latest stable release)
- GeneratePress theme (lightweight, no page builder)
- 8 common plugins: Yoast SEO, WooCommerce, Contact Form 7, WPForms Lite, Wordfence, UpdraftPlus, Smush, and MonsterInsights
- 15 pages of content with images
- WooCommerce configured with 25 sample products
- Total database size: approximately 45MB
What to Measure
- TTFB (Time to First Byte) — every 5 minutes from at least three regions your visitors are actually in. UptimeRobot and Pingdom both do this on free or cheap tiers.
- Full page load time — a weekly GTmetrix run from one fixed location on one fixed connection profile. Changing either between runs makes the series meaningless.
- Uptime — 1-minute check intervals, and let it run for at least 30 days. A week tells you nothing: the incidents you care about are rare by definition.
- Behaviour under load — a burst of concurrent users with Loader.io or k6. This is the test budget hosting fails, and the one almost nobody runs before buying.
- Support response time — three tickets per provider, at three priorities. The exact three are below.
The Categories You Are Choosing Between
WordPress hosting comes in three main flavors. Understanding the difference helps you pick the right tier for your needs:
Shared WordPress Hosting ($2–$10/mo)
Your WordPress site shares server resources with many other sites. Providers install WordPress for you and include basic optimizations. This is where most beginners start, and it works fine for sites with under 25,000 monthly visitors.
Managed WordPress Hosting ($15–$60/mo)
The hosting provider handles WordPress updates, security scanning, daily backups, staging environments, and performance optimization. You focus on content; they handle the technical infrastructure. This is the sweet spot for serious business sites.
Cloud WordPress Hosting ($5–$30/mo)
WordPress runs on cloud infrastructure with auto-scaling, redundant servers, and typically better performance than traditional shared hosting. Many providers now blur the line between cloud and managed hosting, offering both at competitive prices.
TTFB: What Each Tier Looks Like
TTFB (Time to First Byte) is the most reliable indicator of hosting quality because it measures pure server response time, independent of your site's front-end optimization.
The table below is a scoring sheet, not a measurement. The bands are what each tier generally has to deliver to be competitive at its price — use them to judge whether a number you measured is good, bad, or a red flag. Fill the right-hand column with your own results.
| Tier | Competitive TTFB | TTFB under load | Uptime to expect | First response |
|---|---|---|---|---|
| Budget shared | 500–800ms | 2s and up | 99.8%+ | hours |
| Mid-tier shared | 300–450ms | under 1.5s | 99.9%+ | under 2 hours |
| Cloud | 150–250ms | under 500ms | 99.95%+ | under 30 min |
| Managed WordPress | under 200ms | under 350ms | 99.95%+ | under 30 min |
Two things are worth noticing before you measure anything. The first is that the gap between budget shared hosting and cloud or managed hosting is not marginal — it is the difference between a page that answers immediately and one that stalls. The second is that the gap *widens* under load: a budget host that looks acceptable when you are the only visitor is often several seconds slower the moment real traffic arrives, which is precisely when it matters.
Test under load or you have not tested. Idle TTFB is the number every host looks good on, and the number your visitors will never experience.
What Separated the Best from the Rest
Server Technology Stack
The tiers that hit the low end of those bands share the same infrastructure choices. Ask a prospective host which of these it runs — the answers are a decent proxy for the numbers before you measure them:
- LiteSpeed Enterprise or Nginx as the web server (not Apache)
- NVMe SSD storage for both files and databases
- PHP 8.2 or 8.3 with OPcache enabled and tuned
- Redis or Memcached for object caching
- MariaDB 10.11+ instead of MySQL (10–15% faster for WordPress queries)
- HTTP/3 with QUIC protocol support
Budget hosts consistently ran older software stacks: Apache 2.4, PHP 8.0 or 8.1, MySQL 8.0, and regular SSD storage. Each of these "minor" differences compounds into a significant performance gap.
Resource Allocation
The biggest issue with budget shared hosting is overselling. When a provider puts 500 sites on a server designed for 200, everyone suffers during peak traffic. The better providers limit accounts per server and enforce resource isolation so one site can't impact another.
This is what the load test exposes and nothing else does. A shared account with no resource isolation can spike from a few hundred milliseconds to several seconds when a neighbour gets busy, while a container with guaranteed CPU and RAM barely moves. Run your burst test twice, at different times of day, and the difference between the two runs tells you which kind of account you bought.
Uptime: The Non-Negotiable Metric
A 99.9% uptime guarantee sounds impressive until you calculate the math: that's 8 hours and 46 minutes of allowed downtime per year. For an ecommerce site making $500/day, each hour of downtime costs $20.83. Over a year, 99.9% uptime could cost you $182 in lost sales.
Here's what different uptime percentages actually mean:
| Uptime % | Downtime/Year | Downtime/Month | Acceptable For |
|---|---|---|---|
| 99.9% | 8h 46m | 43m 48s | Blogs, portfolios |
| 99.95% | 4h 23m | 21m 54s | Business sites |
| 99.99% | 52m 36s | 4m 23s | Ecommerce, SaaS |
In our 90-day test, budget shared hosts averaged 99.85% uptime — meaning roughly 3 hours and 15 minutes of downtime over the test period. Cloud and managed hosts averaged 99.98%, with the best achieving a perfect 100% over the full 90 days.
Support: The Three Tickets to Send
Send every shortlisted provider these three tickets, at three different priorities, and record two things: how long the first human reply took, and whether it answered the question. Do it before you migrate, while you are still a prospect — support quality for a prospect is the ceiling, not the average.
Ticket 1: Billing Question (Low Priority)
"Can I upgrade my plan mid-billing cycle? Will I be prorated?"
What a good answer looks like: a specific yes or no on proration, with the actual figures for your plan. A bad answer restates the pricing page. This ticket is not really about billing — it is the cheapest way to find out whether anyone reads the question before replying.
Ticket 2: Technical Issue (Medium Priority)
"I'm getting a 500 Internal Server Error after installing a plugin. The error log shows a PHP memory limit issue."
What a good answer looks like: they raise the memory limit for you, name the plugin that triggered it, and explain why it happened. An acceptable answer tells you exactly how to raise it yourself. A bad answer is a link to a generic knowledge-base article about 500 errors — which tells you what every future incident will feel like.
Ticket 3: Urgent Issue (High Priority)
"My site is showing a white screen. I can't access wp-admin at all."
What a good answer looks like: someone is already looking, because their monitoring saw it before your ticket did. This is the ticket that actually decides the shortlist — and the one where the difference between tiers is largest, because a fast reply here requires staffing, not software.
When your site goes down at 2 AM, the difference between a five-minute response and a six-hour one is the difference between losing a few visitors and losing an entire business day. That is what you are buying at the higher tiers, and it is the part no feature list shows you.
Pricing: What You Actually Pay
One of the hosting industry's most frustrating practices is introductory pricing that jumps dramatically at renewal. Here is what to work out before you buy:
| Category | Intro Price | Renewal Price | Price Increase |
|---|---|---|---|
| Budget Shared (typical) | $2.49/mo | $11.99/mo | 381% |
| Mid-tier Shared (typical) | $4.99/mo | $9.99/mo | 100% |
| Cloud Hosting (typical) | $5.99/mo | $7.99/mo | 33% |
| Managed WP (typical) | $15.00/mo | $30.00/mo | 100% |
Budget shared hosts had the highest markup, with some providers nearly quadrupling the price at renewal. Cloud hosting providers generally had the most transparent pricing, with smaller increases or flat rates.
Features That Actually Matter for WordPress
Not all hosting features are created equal. Here are the ones that make a real difference for WordPress sites:
Must-Have Features
- Automatic daily backups with one-click restore. If your site breaks during an update, you need to roll back in minutes, not hours.
- Free SSL certificate. Every site needs HTTPS. Paying extra for basic SSL is a red flag.
- Staging environment. Test changes on a copy of your site before pushing to production. This alone prevents most WordPress disasters.
- Automatic WordPress updates. Core, theme, and plugin updates with automatic rollback if something breaks.
- Free migration. Moving from another host should be free and handled by their team.
Nice-to-Have Features
- Built-in CDN — Saves you from setting up Cloudflare separately.
- Git integration — For developers who want version control on their themes and plugins.
- WP-CLI access — Command-line WordPress management for advanced users.
- Multisite support — If you run multiple WordPress sites from one installation.
- Email hosting — Basic email accounts included with your hosting.
Features You Can Ignore
- "Unlimited" storage/bandwidth — No hosting is truly unlimited. This is marketing language with fair-use clauses buried in the terms.
- Website builder included — You're using WordPress, not a drag-and-drop builder.
- Free domain for life — Domains cost $10–$15/year. This isn't a meaningful differentiator.
Our Recommendations by Use Case
For Bloggers and Personal Sites
If you're running a personal blog or portfolio with under 10,000 monthly visitors, a mid-tier shared hosting plan ($5–$8/mo) gives you the best balance of cost and performance. Avoid the absolute cheapest plans — the performance degradation and slow support aren't worth saving $3/month.
For Small Business Websites
Cloud WordPress hosting ($5–$15/mo) is the right fit. You get auto-scaling for traffic spikes, better uptime, faster support, and performance that keeps your site ranking well in search results. This is where the majority of small businesses should land.
For Ecommerce Stores
Managed WordPress hosting ($15–$40/mo) is worth the investment. WooCommerce sites have higher server requirements, need stronger security, and can't afford downtime during sales. Managed hosts handle the heavy lifting so you can focus on selling.
For Agencies and Developers
Look for managed WordPress plans with multisite support, staging, Git integration, and WP-CLI access. Most managed hosts offer agency plans with 5–25 site licenses at discounted per-site rates ($8–$15 per site).
How to Switch Hosting Providers
If your current host isn't meeting your needs, switching is easier than you might think:
- Sign up with your new host. Most offer money-back guarantees (30–90 days), so there's no financial risk.
- Request free migration. Every reputable host offers free migration. Their team will move your site — files, database, emails, DNS — with minimal downtime.
- Test on the new server. Before pointing your domain, test the migrated site using a temporary URL or hosts file entry.
- Update DNS. Point your domain to the new host. Propagation takes 24–48 hours, during which both servers serve your site.
- Cancel your old host. Wait until your site is fully live on the new host, then cancel the old account.
The entire process typically takes 1–3 days with zero downtime if handled properly.
Frequently Asked Questions
Is managed WordPress hosting worth the higher price?
For business websites and ecommerce stores, yes. The time savings alone (no manual updates, backups, or security management) typically justify the $10–$20/month premium. For hobby blogs with minimal traffic, mid-tier shared hosting is sufficient.
What's the difference between "WordPress hosting" and regular hosting?
True WordPress hosting includes server-level optimizations specifically for WordPress: pre-configured caching, PHP tuned for WordPress, automatic WordPress updates, and WordPress-specific security rules. Regular hosting gives you a server and lets you install WordPress yourself without these optimizations.
Can I host multiple WordPress sites on one plan?
Most shared and cloud hosting plans allow multiple sites (typically 1–unlimited depending on the plan). Managed WordPress hosting usually limits you to a specific number of sites per plan. If you need 5+ sites, look for multi-site or agency plans that offer per-site discounts.
How important is data center location for WordPress hosting?
It matters significantly. A server 5,000 miles from your visitors adds 50–100ms of latency per request. Choose a host with a data center near your primary audience. If you have a global audience, look for hosts with built-in CDN support to cache content worldwide.
Should I choose a host that specializes in WordPress?
WordPress-specialized hosts generally deliver better performance and support for WordPress sites because their entire infrastructure and support team is optimized for WordPress. General-purpose hosts can work well too, but you may need to handle more optimization yourself.
What happens if I outgrow my WordPress hosting plan?
Good hosts make upgrading seamless — you upgrade your plan from the dashboard and your site gets more resources immediately with no downtime. Bad hosts require manual migration to a different server. Before signing up, ask how upgrades work and whether they involve any downtime.
Questions about anything above? We answer them without a sales script.