Choosing WordPress Hosting: What Actually Matters

• PHP 8.x with OPcache enabled. PHP 8 is substantially faster than 7.4 for typical WordPress work, and OPcache removes the cost of recompiling your code on every request.
• A persistent object cache available — Redis or Memcached. This is the difference between a fast admin and a slow one, and it matters enormously on stores and membership sites.
• Enough MySQL memory to keep your working set in RAM. A database that fits in memory is a different machine from one that reads from disk.
• Server-level page caching, which is faster than a plugin doing the same job in PHP.
• HTTP/2 or HTTP/3, and modern TLS. These are table stakes now, but not universal on cheap plans.
• Enough PHP memory and execution time that imports, backups and bulk operations don't time out.

• Unlimited bandwidth and disk space. Neither is unlimited, and neither is your bottleneck.
• '99.9% uptime guarantee'. That's about nine hours of downtime a year, and the guarantee usually pays out in hosting credit.
• A free domain for the first year, which is a discount rather than a feature — and sometimes a lock-in if transferring away is awkward.
• 'Optimised for WordPress' with no specifics. Ask which of the things in the previous section they actually provide.
• Page speed scores in marketing material, which are measured on an empty install of a default theme.

These are four different products and the right one depends far more on your traffic shape than on your traffic volume.

• Shared hosting: cheapest, and genuinely fine for a brochure site or a small blog where nearly everything can be page-cached. Struggles when uncacheable traffic grows, because you're competing for CPU with other sites.
• VPS: guaranteed resources and full control, in exchange for being responsible for updates, security patches and configuration. Sensible if you have someone to administer it; a liability if you don't.
• Managed WordPress hosting: server tuning, caching, staging, backups and updates handled for you, at a higher price and with restrictions on what you can install. The right default for most business sites.
• Cloud platforms: the most control and the best scaling, and the most operational work. Worth it for high traffic or genuinely variable load.

The value isn't raw speed — a well-configured VPS can beat managed hosting on benchmarks. It's the operational work you don't do: server-level caching that's already correct, staging environments that exist without setup, backups that run, security patching at the platform level, and support who know WordPress rather than reading a script.

The restrictions are the trade-off. Managed hosts commonly ban certain caching plugins (because they do it at the server level), restrict some PHP functions, and limit what you can put in the filesystem. For most sites those restrictions cost nothing. For a site doing something unusual, check before committing.

Server location affects the round trip for the initial HTML — the time to first byte. For an Indian business serving Indian customers, a server in India or Singapore is meaningfully better than one in the US.

Everything after that first request is best solved with a CDN, which serves your static assets and often your cached HTML from a location near the visitor regardless of where your origin is. So pick a region close to the majority of your audience, then put a CDN in front for everyone else.

There are occasionally non-technical reasons to care about location — data residency requirements, or a client policy about where data is stored. Those are worth establishing before you choose, because migrating later is avoidable work.

Stores have a different profile from content sites: cart, checkout and account pages can't be page-cached, so a meaningful share of your traffic hits PHP and MySQL every time.

• Persistent object caching is not optional. It's the single biggest factor in store performance.
• Ask how the host's page caching handles WooCommerce exclusions, and verify it yourself after launch.
• Look for adequate database resources specifically — store queries are heavier than blog queries.
• Check that scheduled tasks run reliably; WooCommerce depends on them for order processing and emails.
• Find out what happens under a traffic spike. A sale that takes the store down is an expensive way to learn the answer.

• Is there a real staging environment, with one-click push to and from production?
• What backups exist, how far back do they go, and can you restore one yourself without a support ticket?
• Is there SSH and WP-CLI access? Some tasks are impractical without them.
• Can you get a free SSL certificate, renewed automatically?
• Is there a migration service, and is it free? Moving a site yourself is doable but tedious.
• What are the actual support hours, and are they WordPress people or general hosting support?
• How much does renewal cost? Introductory pricing on hosting is often a fraction of the ongoing rate.

Marketing claims are cheap; measurement isn't. If a host offers a trial or a money-back window, put a real copy of your site on it — same theme, same plugins, same content — and measure the time to first byte on the pages that matter, logged out and logged in.

Compare that against your current host on the same pages at the same times of day. A host that's fast at 3am and slow at 8pm is telling you something about how oversubscribed the machine is.

Before moving, be sure the host is actually the bottleneck. If the time to first byte is low and the page still feels slow, the problem is in the browser — images, scripts, render-blocking CSS — and a new host will change nothing.

Equally, a plugin running a slow query or making a remote API call on every page load will be slow on any host. Migrating a badly built site to better hosting buys you a faster version of the same problem, at a higher monthly cost.