Choosing WordPress Hosting for Speed: What Actually Matters

Hosting comparison tables list storage, bandwidth and the number of sites you may install. None of those decides how quickly your pages load. Fast WordPress hosting comes down to four things: how quickly the server finishes one PHP request, how many requests it can work on at the same moment, how much it can answer from cache without running PHP, and how far it sits from your visitors.

This guide explains each in plain terms, then gives you questions to put to a host and a way to test the answers. It names no providers. Plans change, and the right choice depends on the site far more than on the brand.

Shared, VPS, managed and cloud hosting compared

Type	What you get	Where speed runs out	Who runs the server	Suits
Shared hosting	A slice of a server used by many accounts	CPU and PHP limits per account, busy neighbors	The host	Small brochure sites and blogs
VPS	A virtual server with reserved resources	Whatever you configure, and your own tuning skill	You, or someone you pay	Teams with a sysadmin or a developer on call
Managed WordPress hosting	A stack tuned for WordPress, with caching, staging and backups built in	The PHP worker allowance of the plan	The host	Business sites, stores and course sites without server staff
Cloud infrastructure	Separate web, database and cache servers that can scale	Budget and architecture	You or an agency	High traffic, sharp peaks, several environments

The labels are loose. Some shared plans run a better stack than a badly configured VPS, and "managed" covers everything from real engineering to a control panel with a logo. Judge a plan by the points below.

PHP workers decide how many people you can serve at once

A PHP worker is a process that builds one page at a time. A page served from the page cache does not need one. Everything else does: logged-in pages, carts and checkouts, searches, admin screens, AJAX and REST calls, scheduled tasks.

When every worker is busy, the next request waits. Visitors experience a site that is fine most of the day and crawls, or returns 502 and 504 errors, during a campaign. How many workers you need depends on two things you can measure: how many uncached requests arrive per second at your peak, and how long each one takes. Halve the time per request and the same workers handle twice as many, which is why slow code makes good hosting look bad.

A blog with solid caching gets by on very few workers. A store, a membership site or an LMS needs many more, because its busiest visitors are the logged-in ones.

What fast WordPress hosting has under the hood

Two plans with the same CPU count can differ a great deal because of the software on them. Look for:

• A current PHP branch, and your choice of version. WordPress.org publishes its recommended server requirements, and PHP's supported versions page shows which branches still receive fixes. You should be able to switch version per site without raising a ticket.
• OPcache enabled, with enough memory for your set of plugins. On current WordPress versions you can confirm it is active under Tools > Site Health > Info > Server.
• A page cache at server level, with documentation of what it excludes and how to purge it.
• A persistent object cache (Redis or Memcached), included or as an add-on. For stores and logged-in sites this is close to essential.
• A recent MariaDB or MySQL on fast storage, with enough memory that the database is not reading from disk for every query.
• HTTP/2 or HTTP/3 and Brotli or gzip compression, switched on by default.

Storage and bandwidth figures rarely matter. Watch for the limits written small: inodes (the number of files), database size, execution time and "fair use" CPU clauses.

Server location and the CDN

Every uncached request travels to the origin server and back, so put the origin in the region where most of your customers are. A CDN shortens the trip for images, CSS and JavaScript, and with full-page caching for the HTML of public pages too. It cannot shorten a checkout or a logged-in lesson page, which always go to the origin.

If your audience is split across continents, choose the origin for the visitors who do the uncached things (buyers, members, learners) and let the CDN carry the public pages for everyone else. The layers involved are explained in WordPress caching explained.

Staging, backups and access

These do not make pages faster. They decide whether you can safely make the changes that do.

• Staging. A copy of the site on the same stack, created and refreshed without manual work, with a way to push changes back.
• Backups. Daily at least, kept off the web server, restorable by you, with on-demand snapshots before updates.
• SSH and WP-CLI. Without them, profiling and bulk maintenance are slow or impossible.
• Logs. The PHP error log, the access log and ideally a slow query log. You cannot fix what you cannot see.
• A real cron. The option to run WordPress scheduled tasks from the server and not from visitor traffic.
• Email. Many fast hosts do not send email at all. Plan for a separate transactional email service.

What to ask a host before you sign

1. How many PHP workers does this plan include, and are the CPU cores dedicated?
2. What happens when all workers are busy: do requests queue, and for how long before an error?
3. Which PHP versions can I choose, and how soon after release do new ones appear?
4. Is there a server-level page cache, and what does it exclude by default for WooCommerce and logged-in users?
5. Is Redis or Memcached included, and with how much memory?
6. Where are the data centers, and can I pick one?
7. How are backups stored, how long are they kept, and can I restore one myself?
8. Do I get SSH, WP-CLI, staging and log access on this plan?
9. Are any plugins banned, and what are the limits on files, database size and execution time?

A host that answers these precisely usually runs its platform well. Vague answers to the first two are a warning.

Test with your own site

Benchmarks of empty WordPress installs say little. Many hosts offer a trial or a refund period, so copy your real site across and measure what matters to you:

• server response time for an uncached page, such as the cart or a logged-in page, tested several times from your main region
• the same page while a small load test simulates your peak, so you see what happens when workers run out (our guide to load testing before launch shows how)
• the slowest admin screen your staff use every day
• Tools > Site Health, which reports on the page cache, the object cache and the PHP setup

Compare hosts with the same plugins and the same cache settings, or you are comparing configurations.

What hosting cannot fix

A move helps when the server is the limit: too few workers, an old PHP version you cannot change, no object cache, a data center on the wrong continent. It does not help when a single request is slow by itself because of a heavy plugin, an oversized options table or a theme that loads everything everywhere. That slowness moves with the site.

So profile before you migrate. Whether the money belongs in hosting or in the code is the first question our performance optimization audits answer. And when a move is the right call, a planned WordPress migration with a rehearsal on the new server keeps email, DNS and orders from going missing on the day.

Frequently asked questions

Is managed WordPress hosting worth paying more for?

For a business site without server staff, usually yes. You are paying for a tuned stack, staging, backups and support that knows WordPress, which would otherwise cost your time or a developer's. For a small personal site, good shared hosting is enough.

How many PHP workers does a WooCommerce store need?

Enough to cover the uncached requests at your peak. Estimate how many customers are in the cart and checkout at the busiest moment, measure how long those requests take, and add margin for the admin and scheduled tasks. A load test on a staging copy gives a firmer answer than any rule of thumb.

Is a VPS faster than shared hosting?

It can be, because the resources are yours alone. An untuned VPS with default PHP and database settings and no page cache is often slower than a well-run shared or managed plan. A VPS also makes security updates and monitoring your job.

Do I still need a CDN if the server is fast?

If your visitors are all near the server, the gain is small. For an audience spread across countries, a CDN cuts the delivery time of images and other static files, which a faster origin cannot do. Many also absorb traffic spikes and filter abusive requests before they reach PHP.