Say a customer finally decides to give you their business. They pull up your website on their phone to check your hours or find your contact form, and nothing loads. No page, no menu, no way to reach you. Many of them will not email to tell you something is broken. They will quietly move on to the next result and may forget you were ever an option. That is website downtime, and for a small business the real cost is rarely the technology. It is the customer you never hear from.
Downtime is not only a server that crashes. A site can go dark because a hosting bill lapsed, because a security certificate expired, because an update collided with something on the page, or because the account it all sits under got locked. The cause matters less than one question you can answer today: when it happens, who fixes it?
What does website downtime actually cost a small business?
The bill for an outage does not arrive as an invoice. It shows up quietly, in ways that are easy to miss:
- Enquiries you never see. Every hour the contact form is unreachable is an hour a customer could not send it. You cannot follow up on a message that was never delivered.
- The impression you leave. A visitor who meets a broken page has no way to know it is temporary. To them it can simply read as a business that is not quite running, and that impression can stick.
- Wasted momentum. If you are paying for ads, handing out cards, or posting a link that points to a dead page, that effort tends to leak away while the site is down.
None of this is guaranteed to be catastrophic. A short blip when your business is quiet may cost you almost nothing. The problem is that downtime rarely picks a convenient moment, and you often do not choose when it lands.
Who actually fixes a broken website?
This is where your setup decides your night. Compare the two paths not on price, but on who does the work when something breaks.
- A do-it-yourself builder. When the platform itself has an outage, its own team works to bring it back. But for everything on your side, the content, the settings, an expired domain, a lapsed bill, an update that breaks the page, you are the support team. You are the one who has to notice, work out what failed, search the help docs, and wait in a queue, usually while trying to run the actual business. The tools can be capable, but working out what went wrong, and whether it is even yours to fix, still lands on you.
- A managed, done-for-you site. A human team is responsible for keeping it online. When something breaks, the job of diagnosing and repairing it is theirs, not yours. You may not even be the first to know, because noticing the problem is part of what they do.
There is a structural difference underneath this, and it is worth naming plainly. With a builder you rent and run yourself, you are often the single person the whole thing depends on. With a maintained site, that dependency moves to a team whose job is to be available when you are not.
Is the real hosting question price or people?
Hosting often gets shopped like a commodity, where cheapest wins. That framing hides the part that actually costs you. The non-obvious tradeoff is this: the cheapest hosting can turn out to be the most expensive, because the hidden price is your own time and the customers lost while you are figuring it out. A low monthly fee looks like a saving right up until the afternoon you spend on a support chat instead of serving people.
So the useful question is not "what does hosting cost?" It is "who answers when the site breaks, and how long am I on my own?" Price is easy to compare. People are the part that decides how a bad day actually goes.
Run this five point downtime readiness check on your own setup
You do not need to guess where you stand. Answer these five questions honestly about your current website. They are all things you can check today.
- Contact. If your site went down this minute, do you know exactly who to reach, without searching for it first?
- Detection. Is anyone other than you responsible for noticing an outage, or would you find out only when a customer complains?
- Maintenance. When the site needs an update or a repair, does a human apply it for you, or does that job land on your desk?
- Portability. Could your site be moved to another host if you ever needed to, or does it live locked inside one platform you do not control?
- Response. When something breaks, do you get a person who can act, or a help queue and a page of articles?
There is no pass mark here. The point is simpler: the more of these that come back as "that is on me," the more downtime is a problem you have quietly agreed to solve alone.
Which setup fits your business?
Neither path is wrong. They fit different owners. Find yourself in one of these branches.
- If you enjoy the technical side and have time to spare, a do-it-yourself builder can be a genuinely good fit. You want the controls, you are willing to be on call, and tinkering does not feel like a chore. Choose the builder and keep your five point check current.
- If your website is a nice extra rather than where customers find and judge you, a lighter self-run setup may be all you need. Low stakes means a slow fix is tolerable. The builder path can work.
- If customers find you, size you up, and contact you through the site, and you have no wish to be the emergency support desk, a managed done-for-you site tends to fit better. You are buying the human who answers, not just the space the site sits on.
- If you have zero interest in maintenance and every hour belongs to running the business, hand the upkeep to a team on purpose. The value is not the hosting. It is never having to become the person who fixes the hosting.
Imagine a plumber whose whole day is on the road. If his website drops offline mid-morning, the do-it-yourself path asks him to pull over, open a laptop, and troubleshoot between jobs. The managed path asks him to do nothing, because that call is not his to take. Same outage, two very different mornings. The right choice is simply the one that matches how much of that morning you can afford to give up.
Downtime is a people problem before it is a price problem
Any website can go down at some point. That is not a failure of one host or one builder, it is just the nature of software that runs every day. What separates a minor blip from a lost customer is not the price on the hosting plan. It is whether a capable human is already handling it, or whether that human has to be you. Before you compare what a website costs to keep online, get clear on who is responsible when it is not. Once you can answer that with a name, you have made the decision that actually matters.