Hosting is usually chosen once, on price, during the week the site is built — and then never thought about again. Which is unfortunate, because WordPress hosting quietly determines more about your site's speed, security and uptime than any plugin you will ever install.
Why it matters more than people assume
Your host controls the server resources available to you, how quickly the server starts responding, what happens when traffic spikes, how isolated you are from other sites, whether backups exist and how far back they go, and how fast someone answers when things break at 9pm.
You can optimise a website extensively and still be limited by all of the above. There is a ceiling, and cheap hosting sets it low.
The types, honestly described
Budget shared hosting
Hundreds of sites on one server, sharing resources. Cheap, and genuinely fine for a small brochure site with modest traffic.
The problems appear as you grow. Your site competes with everyone else's traffic spikes. Resource limits are strict. Support is often a script. And on poorly configured servers, a compromise on a neighbouring account can affect you.
Managed WordPress hosting
Servers tuned specifically for WordPress, usually with caching, staging, automatic core updates and better support built in.
More expensive, and worth it for most business sites. The trade-off is less flexibility — some plugins are banned, and you have less server-level control.
VPS or cloud
Dedicated resources, full control. Appropriate for high-traffic or complex sites, but it needs someone who can administer a server. Unmanaged means genuinely unmanaged: security patching, configuration and monitoring are yours.
What to actually look for
Server response time
The most useful single indicator. Time to first byte under 200ms is good, 200 to 500ms acceptable, and consistently over 600ms is a problem no plugin will fix.
Ask a prospective host for a demo site and measure it yourself rather than trusting marketing claims.
A current PHP version
If a host is still defaulting to an unsupported PHP version, that tells you how they think about security generally. Unsupported versions stop receiving patches.
Real backups with real retention
"Daily backups" can mean two days of retention and a fee to restore. Ask three questions: how far back do they go, can you restore yourself, and does restoring cost extra?
Keep your own independent backup regardless. Host backups share a fate with the host.
Staging
A one-click copy of the site for testing updates. Without it, every major update is applied directly to the live site and hoped for. This feature alone prevents a category of outages.
Support that understands WordPress
The gap between hosts is enormous here. Test it before committing — send a moderately technical pre-sales question and judge the answer. A host who says "that's an application issue, not a hosting issue" to everything will be unhelpful on your worst day.
Isolation between accounts
On shared hosting, ask how accounts are isolated. Good hosts containerise. Poor ones do not, and a neighbouring compromise becomes your problem.
What matters less than the marketing suggests
"Unlimited" anything. Nothing is unlimited. There are limits in the terms of service, and you find them at the worst moment.
Free domains and email. Pleasant, but small savings. Tying your domain registration to your host also makes leaving harder than it needs to be.
Uptime guarantees. Read what the compensation actually is. It is usually a small credit, which does not cover a day of lost sales.
Data centre location alone. It matters for latency, but a content delivery network handles most of the distance problem. Server quality matters more than geography.
Signs it is time to move
- Time to first byte consistently over 600ms with a well-optimised site
- The site slows noticeably during normal traffic, not just spikes
- You hit resource limits regularly
- Support cannot answer WordPress questions
- Frequent unexplained downtime
- Still on an outdated PHP version with no upgrade path
- No staging environment
- You have been compromised more than once with no clear cause on your side
That last point deserves attention. Repeated compromises with good site hygiene sometimes point to the hosting environment rather than the site.
Moving without breaking things
Migrations go wrong in predictable ways, and all of them are avoidable.
- Take a complete backup — files and database — before touching anything
- Set up the site on the new host and test it thoroughly before changing DNS
- Lower the DNS time-to-live a day in advance so the switch propagates quickly
- Migrate email separately and carefully — this is where most migrations cause real pain
- Keep the old host running for at least a week afterwards
- Check redirects, forms, checkout and the certificate after the switch
- Watch Search Console for crawl errors for a fortnight
Cancel the old hosting a week after the move, not the same day. It is the cheapest insurance available.
The cost question
The difference between budget hosting and good managed hosting is often a modest monthly amount. Set that against a day of downtime, a compromise caused by a shared server, or the conversions lost to a site that takes four seconds to load.
For a site that generates enquiries or sales, hosting is rarely the right place to economise. For a genuinely low-stakes brochure site, budget hosting is a perfectly reasonable decision.
Not sure where you stand?
Our managed website plans include performance monitoring and optimisation, so if hosting is the limiting factor we will tell you plainly rather than optimising around a problem that needs a different fix.
Send us your web address and we will measure what your server is actually doing, with numbers rather than opinions.
Get Shielded
We build, host, secure and monitor business websites — cleaning up hacks and keeping sites online for clients across the UK, USA, Australia and the UAE.
