Cheap hosting is cheap because there’s nobody there

Hosting is one of the few things a business buys where the cheap option and the good option look identical on the invoice line. Both say “hosting.” One is $4 a month and one is $60, and the website loads either way, right up until the morning it does not.

About this piece

  • Article
  • Cloud & Microsoft 365
  • Written by Nicholas Backwell · Founder, Redsilicon
  • Updated 2026-08-24

What you are actually buying at the top end is a person who answers the phone. Everything else is secondary.

The short version

  • Budget shared hosting packs hundreds of sites onto one machine. Your site’s speed depends on strangers.
  • Support quality is the real difference between price tiers, and it is the hardest thing to check before you buy.
  • “Unlimited” always has a limit written somewhere in the terms.
  • Most hosts back up for their own recovery, not for handing you a specific version of your site from a specific date.
  • The number that matters is not uptime. It is how long a problem takes to get fixed.

What $4 a month actually buys

Shared hosting works by putting a lot of websites on one server and hoping they do not all get busy at once. Usually they do not, which is why it works at all.

The consequences are structural rather than malicious:

Your speed is somebody else’s traffic. A site sharing your server gets mentioned somewhere popular and consumes the CPU. Yours slows down. You have no visibility into this and no recourse.

Resource limits are enforced by stopping you. Every budget host has caps on processes, memory, database connections and script execution time. Hit them and requests fail. The site does not go down cleanly, it goes slow and throws intermittent errors, which is harder to diagnose than an outage.

Support is a queue. Priced at a few dollars a month, a host cannot afford a technician reading your ticket properly. You get a first-line responder working from scripts, and the first three replies are asking you to clear your cache.

None of that matters for a personal blog. It matters when your site is where people find your phone number.

The question that tells you everything

Before you sign up anywhere, ask the sales chat this: “If my site goes down at 4pm on a Friday, who looks at it, and how do I reach them?”

Read the answer carefully. “Submit a ticket and we aim to respond within 24 hours” is a real answer, and it is fine if you accept it knowingly. What you must not do is discover it on the Friday.

The follow-up worth asking: “If the problem turns out to be my WordPress site rather than your server, will you still help?” Most budget hosts will not. Their responsibility ends at the server, and a plugin conflict is your problem. That boundary is where most real outages actually live.

Managed WordPress is a support product wearing a hosting label

Managed WordPress hosting costs more because someone is doing work: keeping PHP current, applying core updates, running a staging copy, and knowing what to do when an update breaks a page.

That last point deserves attention, because it is the actual risk in running WordPress. Updates are necessary, since an out-of-date plugin is one of the most common ways small sites get compromised. Updates also occasionally break a layout or a form. The value in managed hosting is a staging environment where the update runs first and someone looks at the result.

If your site is on unmanaged hosting and nobody is applying updates, you have chosen the compromise risk. If someone is applying updates blindly on the live site with no staging, you have chosen the breakage risk. Both are choices, and most businesses have made one without noticing.

E-commerce raises the stakes on the same point. WooCommerce lives in the same site as the content, so an update that breaks checkout does not just look bad, it stops orders. Nobody should be updating a store on the live site while orders are coming in.

"Unlimited" and other words with terms attached

Unlimited storage, unlimited bandwidth, unlimited email accounts. The limit exists, it is in the acceptable use policy, and it is usually expressed as a resource cap rather than a storage number. Which is fine, but read it, because the enforcement is what you will experience.

Two other line items worth checking:

SSL certificates. Should be free and automatic. Any host still charging annually for a basic certificate is telling you something about how current their platform is.

Migration. Most hosts will move your site for free to win the business. Ask specifically whether that includes email, and whether they handle DNS.

Where email should not live

A lot of cheap hosting plans include mailboxes. It is tempting, because it is free with something you are already buying.

Run your business email somewhere built for email instead, whether that is Microsoft 365 or Google Workspace. Deliverability is the reason. A shared hosting IP address sends mail alongside every other site on the box, and one spammer among them affects whether your quotes reach anyone’s inbox. You will not know that is the problem. You will just think people are ignoring you.

There is also a practical benefit in separating them: moving your website later becomes a much smaller job when the mail is not tangled up in it.

Backups: theirs versus yours

Most hosts take backups. Read what they are for.

A host’s backup exists so they can restore their platform after their own failure. It may be daily, it may be weekly, it may live on the same server as your site. When you ask for your site as it stood eleven days ago because someone made a bad edit, the answer is often that the retention does not go back that far, or that restoring means overwriting everything rather than pulling out one page.

The version you want is your own copy, held somewhere other than the host, on a retention period you chose. Same principle as Microsoft 365, where the platform’s redundancy is not your recovery.

And the same test applies. Restore something once, to a staging location, and confirm it works. A backup nobody has restored from is a line on an invoice.

The metric that actually predicts your experience

Hosts advertise uptime percentages. Ignore them, for two reasons.

The percentages are close to meaningless at the margin. 99.9% permits about 43 minutes of downtime a month. 99.99% permits about four. Both look like a decimal point and feel completely different if the 43 minutes happens at 10am on your busiest day.

More importantly, uptime measures whether the server responds, not whether your site works. A site that loads a database error in six seconds is up. Uptime monitoring says everything is fine.

What predicts your experience is how quickly a competent person engages when something is wrong. Nobody publishes that number. The proxy is what happens when you ask the Friday afternoon question above.

What this means for your building

For a trades business in Port Perry with a five-page site and a phone number, budget hosting is defensible. The site is a business card. If it is down for two hours on a Sunday, nothing happened. Buy cheap, keep your own backup, and put your email somewhere else.

For a clinic in Oshawa taking appointment requests through a form, the calculation changes. A form that silently stops sending is worse than a site that is visibly down, because nobody notices for a week and the enquiries are gone. That needs someone watching, and a test submission on a schedule.

For a retailer running WooCommerce, cheap hosting is a false economy in a way that is easy to quantify against your own average order value. Downtime and checkout errors have a dollar figure. Staging is not a luxury at that point.

What to do about it

  1. Find out where your site is actually hosted. A surprising number of owners do not know, because it was set up by someone who has moved on. Your domain registrar and your host may be two different companies.
  2. Confirm who holds the logins. Registrar, host, WordPress admin. If a former contractor holds any of them, fix that before anything else.
  3. Ask the Friday afternoon question of your current host, in writing, and keep the answer.
  4. Check when your site was last updated. In WordPress, the plugins page shows what is out of date. If it is a long list, that is the finding.
  5. Take one backup you control, off the host, and try restoring it somewhere.
  6. Match the tier to the consequence. If a day of downtime costs you nothing, buy cheap deliberately. If it costs you real money, stop buying on price.

Hosting and maintenance on our own infrastructure is what we do, and it sits alongside the website and marketing side when both are the same job.

Want this scoped for your site?

Tell us the building and what you’re trying to achieve. We’ll tell you what it takes, and whether you actually need it.

Before you call

Is Canadian hosting better than American hosting?

For speed, barely, at these distances. Where it can matter is if you have a contractual or policy requirement to keep data in Canada, which some clients and some sectors impose. Ask whether you have such a requirement before paying a premium for it.

Our site is fine. Why change anything?

Then don’t. The two things worth doing regardless are confirming who holds your logins and having one backup you control. Both are free and both matter the day something goes wrong.

Can you host our site if somebody else built it?

Usually yes, and that is a common arrangement. What matters is being honest with you about whether the build itself has problems that hosting will not fix.

What about the website builder platforms?

They are genuinely fine for a simple brochure site, and the hosting question disappears because it is included. The trade-off is that getting out later is difficult, and you have less control over how the site is structured for search. Worth knowing that going in rather than discovering it at year three.

\n
\n \n