Performance
Is your WordPress host slow? How to tell before you move
8 August 2026 · 6 min read
On this page
Hosting is the largest single factor in WordPress performance and the one people address last, because moving is disruptive and buying a plugin is not.
Before you spend a weekend optimising images, spend ten minutes finding out whether the server is the problem. If it is, nothing else you do will fix it.
The number that tells you
Time to first byte. How long the server takes to start sending the page, before the browser has done anything with it. It isolates server performance from everything else.
Under 200ms: excellent. 200–500ms: fine. Look elsewhere for your performance problem. 500–800ms: slow. Worth investigating. Over 800ms: this is your problem, and no plugin fixes it.
How to measure it properly
GTmetrix or WebPageTest both show TTFB in the waterfall as the first bar. Test from a location near your actual visitors, not near you.
Chrome DevTools: Network tab, click the document request, look at "Waiting for server response".
Three rules for measuring honestly:
- Test a page that is not cached. A cached homepage tells you about your cache, not your server. Add a query string —
?nocache=123— to bypass it. - Test three times and take the median. Single measurements vary enough to send you chasing noise.
- Test at different times of day. Shared hosting is slowest when your server neighbours are busiest, which is exactly when your visitors are too.
Other signs the host is the problem
- The admin is slow even though the front end is cached. The admin is never cached, so it reflects raw server speed.
- Performance varies wildly between tests without your site changing.
- You are on a plan costing under $10 a month. Not a rule, but at that price you are sharing a server with hundreds of sites.
- The host caps PHP workers or memory and you regularly hit the limit.
- Your host runs an old PHP version and has not offered an upgrade path. PHP 8.x is meaningfully faster than 7.x, before any other change.
What is not a hosting problem
Be honest about this before you move, because migrating solves nothing if the cause is on your side:
- A 4MB hero image is not the server's fault
- Thirty plugins each loading scripts is not the server's fault
- No caching configured is a decision, not a hosting limitation
- 5,000 expired transients in your database is your database
If your TTFB is 250ms and the site still feels slow, the problem is on the page, not underneath it.
Is it worth moving?
Yes, if TTFB is consistently over 800ms, the host cannot offer current PHP, you are hitting resource limits regularly, or support cannot answer technical questions.
Probably not, if TTFB is under 500ms and you have not yet done caching and images. Fix your side first — you may find the hosting was fine.
The honest cost: decent WordPress hosting starts around $20–30 a month. Against $3 hosting, that is $300 a year for what is often a 30–60% improvement in server response. Compared to what people spend on optimisation plugins and consultants trying to work around a slow server, it is usually the cheaper answer.
Moving host is genuinely the highest-leverage performance change available to most slow WordPress sites, and the one nobody wants to do. That reluctance is why so many sites are optimised to death on infrastructure that cannot deliver.
If you do move
Do it properly: migrate to staging first, verify everything, cut DNS over at a quiet hour, keep the old host running for a week as a fallback, and do not forget email DNS.
Our host migration is $249 with all of that included, including keeping the old host live for seven days. Or do it yourself — most decent hosts will migrate you free as part of signing up, and that offer is worth asking about before paying anyone.