What Does Website Downtime Cost You?
By CodexierPublished 5 min read
Every hosting sales page quotes a dramatic figure for what downtime costs the average business. There is no average business. A webshop on a Friday evening, a consultancy whose site is a brochure, and a clinic whose booking runs through the site lose completely different things when the site goes down. This guide gives you a worksheet to price an hour of outage for your own company, and then compares that figure with what prevention costs.
Lost sales and leads per hour
Start with what the site does for the business. If it sells, take the revenue of the last three months, divide by the hours in that period, and adjust for when outages tend to happen; an evening hour for a consumer shop carries more than a weekday morning, and your analytics show the pattern. If it generates enquiries, count the leads per hour instead and multiply by the share that become customers and the value of a typical customer. Not every lost visitor is lost forever; some return. But the ones who were comparing suppliers and found your site dead have usually chosen someone else.
Staff time and recovery
The second cost is internal and often larger than the lost sales for a small business, because it lands on the people who are most expensive per hour: the owner and whoever knows the website.
- Time to notice: without monitoring, outages are discovered by a customer, sometimes hours or a weekend later. Add those hours to the outage.
- Time to diagnose: finding out whether it is the host, the domain, a plugin update or an attack, often by people who do not do this regularly.
- Time to fix or restore: fast if a tested backup exists, very slow if it does not, and expensive if an emergency call to an agency is needed.
- Time to clean up afterwards: answering customers, re-sending orders that failed, checking that forms and payments work again.
Price each of these at the hourly value of the people involved, not their salary cost, because the owner's hour was going to be spent on something that earns money.
Reputation and search effects
A single short outage has almost no lasting effect. Repeated or long outages do, through two mechanisms. Customers who hit a dead site twice stop trusting the company behind it, and a business partner who sees it during a due-diligence check draws conclusions. Search engines, meanwhile, tolerate brief errors but treat a site that returns server errors for days as possibly gone, crawl it less and can drop pages from the index; recovering that visibility takes weeks after the site is back. Neither cost fits neatly in a worksheet, so record it as a multiplier on the sales figure that grows with the outage length and frequency.
Your own downtime worksheet
Fill in each line from your own numbers. The result is the cost of one typical outage, which is what you compare prevention against.
| Line | Your input | Calculation |
|---|---|---|
| A. Revenue or lead value per hour | From analytics and accounts, for the hours outages tend to occur | Revenue per hour, or leads per hour times conversion share times customer value |
| B. Hours to notice | Honestly: minutes with monitoring, hours or a weekend without | As is |
| C. Hours to fix and clean up | From the last incident, or an estimate with your current backups | As is |
| D. Staff hourly value | Value of the involved people's time | D times the people-hours spent across B and C |
| E. Reputation and search multiplier | 1 for a rare short outage, higher for repeated or long ones | Applied to A times the outage hours |
| Cost of one outage | A times (B plus C) times E, plus the staff cost from D |
Then multiply by the number of outages you honestly expect per year with your current setup. Sites without maintenance and monitoring typically see several.
What prevention costs in comparison
Prevention is three things, and each one attacks a line in the worksheet. Uptime monitoring turns hours to notice into minutes and costs almost nothing. Tested backups with a documented restore turn a day of recovery into an hour. A maintenance routine that applies updates safely, watches security and checks the site after each change reduces the number of outages in the first place. Put the yearly cost of those three next to the yearly outage cost from the worksheet. For a site that carries real revenue or bookings, the prevention side usually wins by a wide margin; for a site that is a brochure updated once a year, it may not, and that is a legitimate result.
When you do not need this: a brochure site with no revenue or leads flowing through it can accept occasional downtime and a manual restore. When the worksheet says otherwise, a website health audit tells you exactly how exposed your current setup is and what to fix first, and a free call is enough to walk through your worksheet together. Package prices are on the pricing page.
Frequently asked questions
How much downtime is normal for a small business website?
A well-hosted, maintained site should see only minutes of unplanned downtime a year, usually from the host's own incidents. Sites that break after every plugin update or run on neglected servers are the ones that see hours or days. The difference is maintenance, not luck.
Does my host's uptime guarantee protect me?
Only against the host's own failures, and usually with compensation limited to a credit on the hosting fee. It does not cover outages caused by your site's own code, updates, expired domains or attacks, which are the most common causes for small sites.
What is the fastest thing I can do today?
Set up free uptime monitoring that alerts your phone, and check that a backup from the last week actually exists and can be opened. Those two steps shrink the hours-to-notice and hours-to-fix lines more than anything else.
Want to run the worksheet with someone who has seen the outages?
Bring your revenue or lead figures and the story of your last outage. In fifteen minutes we can fill in the worksheet with you and tell you which of the three prevention measures matters most for your setup.
Book a free 15-minute call