The real cost of website downtime is almost always bigger than the handful of orders you can see slipping away — because most of the damage is quiet. Here is the plain business math, so you can put a number on it for your own shop and decide what it is worth to find out sooner.
Why downtime costs more than a few lost sales
When your website is down, the obvious loss is the customer who tried to buy and couldn't. But that is only the part you might notice. Around it sit several other costs that add up fast, and most of them never show on any invoice. Once you list them together, "the site was down for a bit" stops sounding harmless.
Here is what an outage actually costs you, piece by piece.
The five hidden costs of an outage
- Lost orders. Every visitor who arrives while the site is down is a sale that won't happen. Most of them don't come back later — they buy from someone else, right then.
- Wasted ad spend. If you run Google or social ads, you are paying for every click during the outage. Those visitors land on a broken page, so the money you spent to bring them there is simply gone.
- Support load. Confused customers email and call to ask if something is wrong. That is time you or your staff spend firefighting instead of selling — a real cost, even if it never gets counted.
- Lost trust. A visitor who hits an error page, or a "Not secure" warning, quietly wonders whether your shop is safe to buy from at all. Some never return, and you never hear from them.
- Search ranking (SEO). If Google's crawler visits while your site is unreachable, repeated or lengthy outages can chip away at how highly you rank in search over time — which means fewer visitors later, long after the site is back up.
Only the first cost is visible in the moment. The rest keep charging you quietly, which is exactly why downtime is so easy to underestimate.
A simple worked example
Let's put numbers on it. Imagine a small webshop that takes about £4,000 in orders on a normal day, spread fairly evenly across the 12 hours its customers are active. That is roughly £330 of orders every hour.
Now the site goes down for two hours on a busy weekday afternoon:
- Lost orders: 2 hours × £330 ≈ £660 in sales that don't happen.
- Wasted ad spend: if the shop spends £40 a day on ads, roughly £7 of that is spent sending people to a broken page during those two hours.
- Support time: a couple of hours of someone answering "is your site down?" messages instead of doing their actual job.
- Trust and SEO: harder to price, but not zero — some of those turned-away visitors won't come back, and a long outage is a small negative signal to Google.
So a "two-hour glitch" is really the best part of £700 in plain, countable losses — before you even try to value the trust you spent. Run the same sum for your own daily takings and you will have a fair estimate of what one hour of downtime costs you. Multiply by how many hours it usually takes you to notice, and the picture gets sharper still.
The downtime you can't see
Here is the trap that catches most business owners: your homepage can be loading perfectly while the part that actually makes you money is broken. If your checkout, your login, or your booking form has stopped working, a quick glance at your site tells you nothing is wrong — because the front page looks fine.
The same is true of the services sitting behind your website. If the mail server that sends order confirmations goes quiet, or a payment step times out, customers feel it long before you do. This kind of partial outage is the most expensive of all, precisely because it can run for hours or days while you carry on believing everything is fine.
The lesson: "the site is up" and "customers can actually buy" are two different questions, and only the second one pays your bills.
The number that really matters: time-to-know
You can't prevent every outage — even the biggest companies have them. What you can control is how long it takes you to find out. That gap, between the moment something breaks and the moment you know, is where the cost piles up.
If you find out about a problem from an angry customer, the meter has probably been running for hours. If you find out the instant it happens, you can start fixing it — or call your host or web agency — while the loss is still small. Cutting a four-hour outage down to twenty minutes doesn't just feel better; using the example above, it turns roughly £1,300 of lost orders into around £110. Shrinking time-to-know is the single most effective thing you can do about the cost of downtime.
How monitoring shrinks the time-to-know
This is what outside monitoring is for. Instead of you remembering to check the site, a service checks it for you around the clock and messages you the moment something stops working — often before a single customer has had the chance to complain.
Good monitoring doesn't just ping the homepage, either. It watches the things that actually make you money — the checkout, the login, the services behind the scenes — so a broken buy button can't hide behind a healthy-looking front page. When something breaks, you get told; when it recovers, you get told that too, so you know it's genuinely fixed.
Where WatchControl fits
WatchControl is the part of TrustCtrl that watches for exactly this. It checks that your site is up and how fast it responds, checks the services behind it (including your mail server), and every five minutes it walks through your login and checkout the way a real customer would — taking a screenshot the moment a step breaks, so you can see what went wrong. When something goes down or breaks, it emails you; when it recovers, it emails you again. There's nothing to install — it watches from the outside, the same as your customers do, and explains what it finds in plain language with a simple view for you and a technical view for your developer. It won't fix the outage for you, but it makes sure you're the first to know, not the last. To go deeper on why a basic "is it up?" check isn't enough, see uptime monitoring beyond a simple ping. TrustCtrl is free during early access.
How much does website downtime cost per hour?
For a small business, the simplest estimate is your average daily online revenue divided by the number of hours your customers are usually active. A shop taking £4,000 a day over a 12-hour active window loses roughly £330 of orders for every hour it is down — and that is before you add wasted ad spend, support time and lost trust. Work it out with your own figures and you will have a number that means something for your business.
How do I know if my website is down right now?
Checking it yourself is a start, but it only tells you about this exact moment — and a homepage that loads can hide a broken checkout or login. The reliable way is an outside monitoring service that checks your site continuously and messages you the instant something stops working, so you find out in minutes rather than when a customer finally tells you.
Can my website be down without me noticing?
Yes, and this is the most expensive kind of outage. Your homepage can load perfectly while your checkout, login, booking form or the mail server that sends order confirmations has quietly stopped working. Because the front page looks fine, these partial failures can run for hours or days unless something is actively testing the steps customers rely on.
Is website monitoring worth it for a small business?
If your website brings in orders, bookings or leads, then almost certainly yes — the cost of a single unnoticed outage usually dwarfs the effort of setting up monitoring. The value isn't in preventing every problem, which no one can do, but in shrinking the time between a problem starting and you knowing about it, which is where most of the money is lost.