Hosting is the part of a website nobody wants to think about, right up until the morning it goes down. The comparison articles do not help much either — they are mostly affiliate scoreboards, and the cheapest option always wins on a chart that only measures price.
A more useful way to choose: work out which of three questions actually applies to you, then pick for that.
Question one: what happens when it breaks at 6am?
This is the question price comparisons never cover, and it is the one that will matter most. Not “is there support” — everybody claims support. The real questions are who answers, how fast, and whether they can actually fix a WordPress problem or only confirm that the server is powered on.
A budget host with a ticket queue is fine when your site is a brochure. It is not fine when your site takes bookings, and an outage on a Saturday means a lost weekend of revenue. Match the response you are paying for to the cost of an hour of downtime in your business. If that number is meaningful, buy support, not disk space.
Question two: who is responsible for updates?
Every WordPress site needs core, theme and plugin updates, and someone has to own that. Hosting plans divide neatly by who that someone is:
Shared hosting
You rent space on a server with hundreds of other sites. It is inexpensive and perfectly adequate for a small site with modest traffic. Updates, backups and upkeep are yours to manage, and a badly behaved neighbour can slow you down.
Managed WordPress hosting
The host handles updates, caching and backups, and tunes the server for WordPress specifically. Costs more, removes a category of work, and sometimes restricts which plugins you may install — usually the ones that would have caused the trouble anyway.
VPS or cloud
You get isolated resources and near-total control, and you inherit near-total responsibility. Worth it when you have an application, real traffic, or specific software requirements. Overkill for a nine-page site, and a genuine liability if nobody on your side administers servers.
Hosting bundled with management
The arrangement most small businesses actually want: someone hosts the site, keeps it updated, watches it, and answers when you write. It is what our own hosting and management plans are, and the reason they are usually sold together is that hosting without maintenance is where neglected sites come from.
Question three: how hard is it to leave?
Ask before you sign, not after. Can you export the site and database yourself? Is the site built in a proprietary page builder that only exists on that platform? Are you on a multi-year prepayment? A host confident in its service will answer these plainly. Anything evasive is the answer.
About that uptime number
Everyone advertises 99.9%. That is roughly 43 minutes of downtime a month — acceptable, if it is true and if it lands at 3am rather than during your busiest hour. The number to be suspicious of is the one with no monitoring behind it. If nobody is watching your site independently of the host, you will learn about an outage from a customer, which is the expensive way.
Independent uptime monitoring costs nothing to modest amounts and is worth setting up regardless of who hosts you.
The upkeep short list
Sites rarely fail because of anything exotic. They fail on the same handful of neglected basics:
- An outdated plugin. The overwhelming majority of WordPress trouble begins here. Update, or have someone update.
- A reused admin password. Use a password manager, and turn on two-factor sign-in for administrator accounts.
- Unlimited login attempts. Rate-limit them, so automated guessing stops being viable.
- No SSL certificate. They are free and automatic now, and browsers visibly flag sites that lack one.
- Backups nobody has ever restored. A backup you have not tested is a hope, not a plan.
Notice that only one of these is really the host’s job. Reliability is mostly maintenance, which is why the two arrive together.
Moving hosts without breaking things
Migrations go wrong in predictable ways, and the order matters:
- Take a full backup of files and database, and keep a copy off the old server.
- Build the site at the new host and test it there before any DNS changes — forms, checkout, logins, email.
- Lower the DNS TTL a day ahead so the switch propagates quickly.
- Freeze content changes during the cutover, or you will lose whatever was published in the gap.
- Point DNS, then keep the old host running for a week. It costs one month’s fee and buys a safety net.
- Confirm email still flows — this is the step people forget, and website moves break mail more often than they break websites.
If any of that reads as a weekend you would rather not spend, migrations are a normal part of what we do, and the site stays live throughout. Our backup service exists for the same reason step one exists.