Ask most business owners what an hour offline costs and you get a shrug. It feels like an inconvenience rather than a number.
It is a number, and it is usually larger than expected — because website downtime has costs that arrive weeks after the site comes back up.
The obvious cost
Start with the arithmetic you can do in a minute.
Take your monthly revenue from the website, divide by the hours you actually trade. For an online store trading around the clock, divide monthly revenue by 730. For a service business where enquiries come in during office hours, divide by the hours you are open.
A store turning over £30,000 a month loses roughly £41 for every hour offline. Half a day is close to £500.
That is the floor, not the total.
The costs people forget
Enquiries that never come back
For a service business this is usually the biggest line. Someone searching for a plumber, a solicitor or a security service at 8pm does not bookmark your broken site and return tomorrow. They click the next result.
You never see that loss in any report. It appears as a slightly quieter month.
Paid traffic you still pay for
If ads are running while the site is down, you are buying clicks that land on an error page. The spend continues, the conversions do not. Overnight outages are particularly costly here because nobody pauses the campaigns.
Search damage
A short outage does little harm — search engines retry. Sustained downtime is different. Repeated failed crawls reduce crawl frequency, and prolonged unavailability can affect rankings.
The recovery is slow and asymmetric. Losing positions takes days. Regaining them takes months.
Trust
Hard to quantify, real nonetheless. A customer who tried to reach you and could not carries that impression. If they were about to make a first purchase, they now have a reason to hesitate.
Your time
An outage consumes a working day: diagnosing, chasing the host, answering customers, and doing none of the work you planned. That is a genuine cost even though no invoice records it.
What actually causes it
In rough order of frequency:
- A failed update — a plugin or theme update breaks the site, usually applied without staging
- Hosting problems — server failures, resource limits, or account suspensions
- An expired certificate or domain — entirely preventable, and surprisingly common
- Compromise — either the attack itself or the host suspending the account because of it
- Traffic spikes — a campaign or press mention overwhelming a small server
- Database failures — corruption or connection limits
Notice how many are preventable with routine work rather than clever engineering. Expired domains and untested updates cause more outages than anything sophisticated.
The detection problem
Here is what makes downtime much worse than it needs to be: most small businesses find out because a customer tells them.
A site that breaks at 7pm on a Friday and is discovered on Monday morning has been offline for 60 hours. The same fault caught by monitoring at 7:05pm is a 30-minute problem.
The fault was identical. The cost differed by two orders of magnitude. That difference is entirely about detection, not about the technical severity of the problem.
Uptime monitoring is inexpensive and it is the highest-return item on this page.
Reducing it, in order of value
- Uptime monitoring with alerts that reach a phone, not just an inbox
- Test updates on staging before applying them live
- Backups you have tested restoring, so recovery is minutes rather than hours
- Adequate hosting for your actual traffic
- Certificate and domain expiry alerts — these outages are pure carelessness
- Security monitoring, since compromise-driven suspensions are among the longest outages
- Knowing who to call before you need to
That last one matters more than it sounds. A great deal of downtime is not repair time — it is the hours spent working out who can help.
Compromise causes the longest outages
Worth separating out. When a host suspends an account for malware, the site stays down until it is cleaned, verified and the suspension lifted. That is commonly a day or more.
Add a Google warning on top and the effective outage extends further — the site is technically online while a red interstitial stops nearly every visitor. Our guide to the deceptive site ahead warning covers that scenario.
This is why security and uptime are the same conversation, not separate ones.
What level of uptime is realistic
Perfect uptime is not a sensible target for a small business site. Some maintenance is necessary and some host incidents are outside your control.
What is achievable: 99.9%, which is under 45 minutes a month. Most of that should be planned rather than a surprise. If you are experiencing hours of unplanned downtime regularly, the problem is not bad luck — it is hosting, maintenance practice, or both.
The comparison worth making
Put a monitored, maintained site next to an unmonitored one over a year. The unmonitored site is not necessarily less reliable. It simply stays broken longer each time, because nobody knows.
Monitoring and maintenance cost a predictable monthly amount. A single long weekend outage often costs more than a year of it.
If you want that handled
Our managed website plans include uptime monitoring with real alerts, updates tested on staging, tested backups, and someone who responds when something goes wrong.
If your worry is specifically the security-driven outages — suspensions and blacklisting — our security monitoring service targets that directly.
Get in touch and tell us what your last outage looked like. That usually tells us where the actual gap is.
Get Shielded
We build, host, secure and monitor business websites — cleaning up hacks and keeping sites online for clients across the UK, USA, Australia and the UAE.
