When and how to switch WordPress hosting
You have optimized your images, installed a caching plugin, deleted a few unused plugins, and worked through every speed tip you could find. Your site still takes three or four seconds just to start responding, and the score in PageSpeed Insights barely moves no matter what you do.
If that sounds familiar, there is a good chance you have been fixing the wrong layer. When a site is slow at the server level, no amount of front-end polish will rescue it. In most cases the real culprit is the hosting you are on, and the only durable fix is to move to a server that can actually keep up.
The short answer: check your TTFB
The single number that tells you whether your host is the problem is Time to First Byte (TTFB), the time between a browser asking for your page and the server sending back the first byte of data. Everything else, images, CSS, JavaScript, only happens after that first byte arrives.
As a rule of thumb:
- Under 200ms: excellent. Your server is not your problem.
- 200ms to 600ms: acceptable, but you are losing ground.
- Over 600ms consistently: your hosting is the bottleneck, and front-end fixes will not save you.
If your TTFB sits in that last bucket, read on. The rest of this post is about confirming it and deciding what to do next.
Why your host quietly caps your speed
Most slow-site advice assumes the server is fine and the problem lives on the page. On budget shared hosting, that assumption is often wrong.
Shared hosting puts hundreds of sites on the same physical machine, and they all share the same CPU, memory, and disk input/output. Your host sells you a slice, and that slice has hard limits. When you cross them, the platform does not warn you. It just quietly slows you down.
- CPU throttling: exceed your CPU allowance at peak and requests get queued instead of served.
- No object caching: on cheap plans every dynamic request hits the database directly, so logged-in users and carts crawl.
- Old PHP and slow disk: outdated PHP versions and heavily shared disk add hundreds of milliseconds to every request.
- Oversold “unlimited” plans: the resource is shared among more sites than it can comfortably serve at peak.
- Your site grew, your plan did not: a starter plan that was fine for ten posts struggles once you add real traffic, a page builder, and a store.
None of that shows up as an obvious red flag. It shows up as a site that feels slow no matter what you do to the front end.
How to confirm your hosting is the bottleneck
Run these checks in order. They take about ten minutes and will tell you whether switching hosts is actually going to help.
- Measure TTFB on your homepage and a blog post. In Chrome, open DevTools, go to the Network tab, reload, and look at the “Waiting for server response” value for the first request. Or use PageSpeed Insights and read the server response time. Do this three times across the day, because shared servers are faster at 3am than at 3pm.
- Test from more than one location. Run WebPageTest or GTmetrix from a second region. If TTFB is high everywhere, and high on nearly every page, the server is the common factor.
- See whether caching changes anything. Turn on full-page caching and re-test. If a fully cached page is still slow to respond, work is happening before WordPress even starts.
- Watch for throttling signals. Random 503 or 508 errors during traffic spikes, painfully slow wp-admin logins, and “CPU limit reached” emails from your host are all classic signs.
- Install a blank WordPress site on the same host and test it. If a site with zero plugins is also slow, your setup is not the problem. The host is.
- Ask your host for CPU, memory, and database usage numbers. If they cannot or will not show you, treat that as an answer. Performance hosts hand you this data.
If three or more of those point at the server, stop optimizing the page. You have confirmed a hosting problem.
The fix: what actually moves the needle
Work from free to premium. You may not need the last step, but you cannot know that until you finish the first two.
1. Do the free fixes first
These are worth doing regardless of where you end up, and they cost nothing:
- Install a full-page caching plugin such as LiteSpeed Cache, WP Rocket, or W3 Total Cache.
- Put a free CDN in front of the site. Cloudflare’s free plan is enough for most small sites.
- Update PHP to 8.3 or newer. Newer PHP is meaningfully faster on the same hardware, and 8.5 runs roughly 23 percent faster than 8.3 in real WordPress tests.
- Remove plugins you do not use and optimize your images. Less work per request means less time spent on a slow server.
If TTFB drops under 300ms after this, you are done. If it stays over 600ms, you have just proven the ceiling is the server, not your site.
2. Measure the real ceiling before you upgrade blindly
Before paying more, clone your site to a staging environment on the same host and run a simple load test at low concurrency. If a brand-new instance buckles under a handful of simultaneous visitors, a bigger plan may buy you headroom but not the speed you actually want. That is the moment people realize they are renting the wrong infrastructure, not the wrong size of it.
3. Move to hosting built for speed
This is the fix when steps one and two both fail. Managed WordPress hosts run better stacks by default: NGINX, server-level object caching, faster CPUs, and, on the premium tier, a CDN wired directly into the platform. You stop babysitting resource limits and start on a server that was designed to serve WordPress quickly.
The honest caveat: if your site is small, mostly static, and already sitting under 300ms TTFB, you do not need to move yet. Save the money and revisit when traffic or a store changes the math.
Quick comparison of the hosting options
| Option | Best For | Starting Price | Rating | Get Started |
|---|---|---|---|---|
| Budget shared hosting | Hobby blogs and first sites with light traffic | around $3 per month | 3/5 | See the guide |
| Managed WordPress (WP Engine) | Growing sites and agencies that need headroom | around $20 per month | 4/5 | View plans |
| Premium managed (Kinsta) | Business sites where speed and conversions matter | $35 per month | 4.5/5 | See Kinsta plans |
When it is worth paying
Put the decision in time and money terms. If you have spent more than a couple of weekends fighting a slow site, a managed plan often costs less than the hours you are already losing. If your site takes payments or ranks on speed-sensitive keywords, the cost of a slow server is a number you can actually see in your revenue and your rankings, not just in a benchmark.
If your hosting is the bottleneck: Kinsta keeps your site safe with automatic daily backups and one-click restore, so a bad update or a hack is a rollback, not a rebuild. Their support is top tier, and 24/7 live chat is staffed by WordPress engineers who will help fix the actual problem with you, so you are not stuck waiting on your developer to reply. Plans start at $35 per month.
Frequently asked questions
Check your Time to First Byte (TTFB). In Chrome, open DevTools, go to the Network tab, reload, and read the Waiting for server response value for the first request. If it is consistently above 600ms across several tests and locations, the server is the bottleneck, not your theme or plugins.
No. Caching reduces the work your server has to do, which helps, but it does not make slow hardware fast. If a fully cached page still takes a long time to respond, the delay is happening before WordPress runs, which points at the host.
It is worth it when speed affects your traffic or revenue and the free fixes did not bring TTFB under about 300ms. For a small, mostly static site with good TTFB, shared hosting is fine and you should keep the money.
Not if it is done properly. A migration that keeps the same URLs and adds no downtime is invisible to Google. Test on a staging copy first, then switch DNS once the new server is confirmed working.
The migration itself usually takes a few minutes to a couple of hours, and many managed hosts handle it for you for free. DNS propagation can take up to 24 to 48 hours, but typically resolves much faster.
Final thoughts: do this first
You do not need to switch hosts today. You need to know whether you should. Do these three things in the next ten minutes:
- Measure TTFB on your homepage and one post, using the browser Network tab or PageSpeed Insights.
- If it is over 600ms, turn on full-page caching, add a free CDN, and update PHP, then measure again.
- If TTFB is still high after all three, the server is your ceiling. That is the signal to move to managed hosting, and you can read the free speed fixes for everything else while you plan the move.
If the problem is not hosting at all, our Kinsta vs WP Engine comparison covers how to choose once you decide to switch. And if you want the short version of what “good” looks like, the best WordPress hosting guide walks through what to compare before you pay for anything.
This post contains affiliate links. If you buy through them, I may earn a small commission at no extra cost to you.

