Hosting is usually chosen on price, once, and then never thought about until something breaks. That is understandable — it is the least interesting line in the budget. It is also the layer everything else sits on, and the wrong choice shows up later as a slow site, a support queue nobody answers, or a backup that does not exist.
What the tiers actually mean
- Shared hosting. Your site sits on a server with hundreds of others and shares its resources. Cheap, and genuinely fine for a brochure site with modest traffic. A busy neighbour can slow you down.
- VPS. A reserved slice of a server. More predictable, more control, and someone has to administer it — that someone is you or whoever you pay.
- Managed WordPress hosting. Shared or VPS underneath, with updates, caching, staging and backups handled. Costs more; removes work you would otherwise do or forget.
- Cloud or dedicated. For real scale or real compliance requirements. If you are reading this to pick hosting for a small business site, you do not need it yet.
Most small business sites are well served by good shared or managed hosting. Paying for a VPS you do not administer properly is worse than shared hosting that someone else maintains.
The renewal price is the real price
This is the single most common trap. The advertised figure is an introductory rate for the first term, often with a long commitment, and the renewal is frequently several times higher.
- Find the renewal price before you sign, not in the email a year later.
- Check what the term is — a very low monthly figure often requires paying three years upfront.
- Check whether the free domain renews free. It usually does not.
- Check whether SSL, backups, email and migration are included or sold separately.
Compare hosts on the second-year cost with everything you actually need included. On that basis the cheap option is often not the cheap option.
What matters more than price
- Where the servers are. Physical distance affects speed. If your customers are in one country, host near them or use a CDN.
- Backups. How often, how far back, and — the question people forget — can you restore one yourself without opening a ticket?
- Support that answers. Test it before you buy: send a pre-sales question at an awkward hour and see what comes back and how fast.
- Staging. A one-click copy of the site to test changes on. Once you have used it you will not go back.
- Migration. Will they move your existing site for you, free, and without downtime?
- Getting out. Can you take a full export — files and database — whenever you like? A host that makes leaving difficult is telling you something.
Signs your current hosting is the problem
Before blaming the website, check whether the server is the bottleneck:
- The server takes a long time to send the first byte, even on a simple page.
- The site is noticeably slower at busy times of day.
- It goes down occasionally and comes back without explanation.
- The admin area is sluggish even though visitors are few.
- You hit resource limits and are told to upgrade rather than told what used them.
If those describe your site, image optimisation will not save it — the fix is a move. Our guide to checking and improving website speed covers how to tell the difference between a slow server and a slow page.
Keep the accounts in your own name
This matters more than which host you pick. The hosting account and the domain registration should be in the business's name, with you as the contact, even when an agency manages them day to day.
Businesses lose control of their own websites this way more often than you would expect — the developer who set it up moved on, the account is in their name, and the renewal notice goes to an address nobody reads. We covered the consequences in who owns your website after launch, and it belongs in the agreement from the start, as a design contract should set out.
Security, honestly
Hosting security is shared: the host secures the server, you secure what runs on it. A good host provides free SSL, server-level firewalling, isolation between accounts and prompt patching. None of that protects you from an outdated plugin or a reused password.
Ask specifically whether accounts are isolated from each other on shared hosting — cross-contamination between sites on the same server is a real way small sites get compromised, as we covered in what to do if your website is hacked.
Email: host it somewhere else
Most hosting plans bundle email, and most businesses should not use it. Mail sent from a shared web server is more likely to be filtered as spam, the storage is small, the webmail is usually poor, and your email and your website then fail together whenever the server has a bad day.
Keep email on a dedicated provider and the website on a host. They are different problems and bundling them saves a few dollars at the cost of messages that quietly never arrive — which matters most when the message is a quote or an order confirmation.
Moving host without breaking anything
Migration is where sites get damaged, usually in avoidable ways. The order that works:
- Copy the site to the new host and test it there, on a temporary address, before anything points at it.
- Check the forms actually send from the new server — this is the most common thing to break and the least likely to be noticed.
- Lower the DNS record's time-to-live a day ahead, so the switch takes minutes rather than two days.
- Switch DNS, then keep the old hosting running for a week. It costs one more month and saves you if something was missed.
- Re-issue the SSL certificate on the new host and confirm there are no mixed-content warnings.
- Check Search Console for crawl errors in the days afterwards.
Done this way a migration is invisible to visitors. Done by switching DNS first and testing afterwards, it is a day of downtime and a week of small broken things.
When managed hosting is worth the premium
Managed hosting costs more and removes work. Whether that trade is worth it depends on one question: who was going to do that work otherwise?
- If nobody in the business updates the platform and plugins, managed hosting that does it is cheaper than the clean-up after a compromise.
- If you have a developer on retainer already, you are paying twice.
- If the site takes payments or holds customer data, the staging environment and the tested backups are worth the difference on their own.
Questions to ask before you buy
- What does this cost in year two, with everything I need included?
- Where are the servers, and is a CDN included?
- How often are backups taken, how long are they kept, and can I restore one myself?
- Is there a staging environment?
- Will you migrate my existing site, and is that free?
- What is the support response time, and is it staffed around the clock?
- Can I export everything and leave whenever I want?
- On shared hosting, are accounts isolated from each other?
A host that answers these clearly before taking your money will usually answer clearly afterwards too, which is most of what you are buying.
We host and maintain the websites we build, so these decisions are part of the work rather than something handed to you at launch. To talk it through, contact us.
