Hosting sets the ceiling for how fast your WordPress site can be. A good theme on a slow server will always feel slow, and no plugin can fully hide it. Below I explain what to look for in WordPress hosting for speed, the questions I ask before recommending a host to a client, and how to test whether your current host is really the problem before you go through a migration.
What your host actually controls
Hosting affects speed in ways that are easy to miss when you compare plans on price and storage.
- Server response time. How quickly the server starts sending a page, especially pages that aren’t cached.
- Processing capacity. CPU and the number of PHP workers decide how many uncached requests the server handles at once. When workers run out, visitors queue.
- Software. Current PHP versions, a modern web server, HTTP/3 support and server-level caching.
- Location. A server in Europe serving customers in Texas adds distance to every uncached request.
- Extras that affect speed: Redis or Memcached for object caching, a built-in CDN, and staging sites for safe testing.
What to look for in WordPress hosting for speed
Server-level page caching
Hosts that cache pages at server level, through LiteSpeed, Nginx or Varnish, serve cached pages faster than plugin-only caching. Ask how they handle cache exclusions for WooCommerce and logged-in users.
Enough PHP workers for your type of site
A brochure site with good caching needs few workers, because most visits hit the cache. A WooCommerce store, membership site or anything with logged-in users needs many more, because those requests can’t be cached. Ask how many workers your plan includes and what happens when they are all busy.
Current PHP and easy upgrades
Newer PHP versions are faster and still receive security fixes. A good host lets you switch versions per site in a few clicks and keeps older versions available long enough for you to test.
Object cache availability
For stores and membership sites, check that Redis or Memcached is available on your plan, not just on higher tiers.
Data center choice
Choose a data center close to most of your customers. A CDN helps with static files and cached pages, but uncached pages and checkout still come from the origin server.
Staging, backups and support
These aren’t speed features directly, but they decide whether you can safely test speed changes. Every change I make goes to a staging copy first. Good support matters too: when something is slow at 9 a.m. on a Monday, you want someone who understands WordPress, not a script.
Questions to ask before you sign up
- Which web server and page caching do you use, and how do I exclude pages from the cache?
- How many PHP workers does this plan include, and what happens when they are all in use?
- Is Redis or Memcached included on this plan?
- Which PHP versions can I choose, and how much notice do you give before retiring one?
- Where are your data centers, and can I choose one?
- Do you include staging, and how often are backups taken and kept?
- What resource limits apply, and how will I know if I hit them?
A host that answers these clearly, in writing, is usually a host that will be easy to work with later.
Types of hosting, in plain terms
- Shared hosting: many sites share one server. It is cheap and fine for small brochure sites, but performance depends on your neighbors and resource limits are tight.
- Managed WordPress hosting: tuned for WordPress, with caching, staging and support included. A good default for most businesses that don’t want to manage servers.
- Cloud VPS with a control panel: your own server resources, managed through a panel. Excellent value for performance if someone technical looks after it.
- Dedicated or custom infrastructure: for large stores and high-traffic sites with specific needs.
There’s no single best host. The right choice depends on the type of site, where your customers are, and who will look after the server.
How to test whether hosting is your problem
Before migrating, measure. Hosting gets blamed for problems that are really images, plugins or scripts.
- Check cached response time. Load a page twice and check the server response time in the DevTools Network tab. If cached pages are slow, the cache or the server is the issue.
- Check uncached response time. Add a random query string to the URL, for example
?test=123, which most caches skip, and compare. Very slow uncached pages point to either heavy plugins or a weak server. - Test from where your customers are. Use a testing tool that lets you choose a location near your audience.
- Watch the admin. A slow dashboard and editor, with no heavy plugins installed, often means the server is underpowered.
- Look for resource errors. 503 or 508 errors at busy times mean you’re hitting plan limits.
A useful trick: spin up a copy of the site on the host you are considering, using a temporary address, and run the same tests on both. That gives you a like-for-like comparison before you commit.
If the tests point to the host, migrate on a staging copy, test forms, checkout and tracking, then switch DNS at a quiet time. I handle hosting moves and ongoing server care as part of WordPress maintenance. If you want the host chosen and tuned as part of a wider speed project, that is speed optimization.
The short version
- Measure cached and uncached response times before blaming the host.
- Ask about server-level caching, PHP workers and object caching.
- Pick a data center near your customers.
- Make sure staging and daily backups are included.
- Run the current PHP version supported by your plugins.
- Migrate on staging and test before switching DNS.
Worth reading next: how to run a WordPress plugin audit for speed, step by step and WebP vs AVIF for WordPress, and the format I actually use.
Common questions
Is managed WordPress hosting always faster than shared hosting?
Not always, but it usually includes server caching, better resource limits and WordPress-aware support, which makes good speed easier to reach and keep.
Does a CDN replace good hosting?
No. A CDN speeds up delivery of static files and cached pages. Uncached pages, the admin and checkout still depend on your server.
How do I know if I need more PHP workers?
Look for slow or failing requests at busy times, especially on checkout or logged-in pages, while cached pages stay fast. Your host can show worker usage.
Will moving hosts hurt my SEO?
Not if the move is done properly: same URLs, same content, minimal downtime and a quick DNS switch.
Book a free website review, and I’ll test your server response times and tell you honestly whether moving is worth it.





