Analysis
What Website Downtime Really Costs Your Business
Everyone knows downtime is expensive. But the numbers are worse than most people think — and the biggest cost isn't from servers going down. It's from sites that are "up" but broken: broken checkout flows, invisible signup forms, and missing product images that silently bleed revenue while your monitoring says everything is fine.
- Direct revenue impact by business type
- The hidden cost of "up but broken" failures
- How to minimize downtime cost
The numbers
Direct revenue impact of downtime
The cost of downtime depends on your business model, traffic volume, and how long the outage lasts. Here's how to think about it for different types of sites:
E-commerce sites
The math is straightforward: hourly revenue / uptime hours = cost per minute of downtime. A store doing $500K/year in online revenue loses roughly $57/hour or $0.95/minute. At $5M/year, that's $570/hour. And this is just the immediate transaction loss — it doesn't count abandoned carts, customers who leave and never return, or the SEO impact.
SaaS products
Downtime on your marketing site means lost signups. If your site converts at 2% and gets 1,000 daily visitors, an hour of downtime costs you roughly 83 potential visitors and 1-2 signups. At a $100 average contract value, that's $100-200 in lost pipeline per hour — compounding over the customer lifetime.
Lead generation sites
For businesses where the website drives leads (consultancies, agencies, B2B services), downtime means missed form submissions and phone calls. Unlike e-commerce, these leads don't come back to "retry" later — they go to a competitor.
Content and media sites
Ad-supported sites lose revenue directly proportional to lost pageviews. But the bigger risk is SEO: extended or repeated downtime signals to search engines that your site is unreliable, causing ranking drops that take weeks to recover from.
Beyond lost revenue
The hidden costs most people miss
SEO ranking damage
CriticalGoogle crawls your site regularly. If the crawler hits errors repeatedly, your rankings drop. A few hours of downtime can cause ranking losses that take weeks to recover. Extended "up but broken" failures are even worse — Google sees a page but the content is garbage.
Customer trust erosion
CriticalA customer hits your broken checkout page once. They retry. Twice. They leave and buy from a competitor. The lifetime value of that customer is gone. And they tell others. Trust is rebuilt much slower than it's lost.
Team time and opportunity cost
ModerateEvery outage pulls engineers away from feature work. The incident response, root cause analysis, post-mortem — a 30-minute outage easily costs 4-8 hours of engineering time. That's time not spent shipping product.
Brand reputation
ModerateFor public-facing products, outages become social media events. "Is [product] down?" tweets, Reddit threads, support ticket floods. The reputational cost far outlasts the technical incident.
The bigger problem
Why "up but broken" costs more than downtime
Here's the counterintuitive truth: a site that's "up but broken" costs more than a site that's completely down.
When your site is down, you know immediately. Your uptime monitor alerts you. Your team responds. MTTR (mean time to repair) is measured in minutes.
When your site is "up but broken" — the server responds 200 OK, but the JavaScript is broken, the checkout form doesn't render, or the payment script won't load — nobody knows. Your uptime monitor says everything is fine. Your users silently leave.
The detection gap
The average "up but broken" failure goes undetected for hours, not minutes. Often it's discovered when a customer emails support, a colleague happens to visit the site, or someone checks analytics and notices a conversion drop. By then, the damage is done.
Why it happens so often
Modern websites depend on dozens of individual assets — JS bundles, CSS files, third-party scripts, CDN-delivered images. Any one of these can fail independently while the server continues responding normally. A deploy changes a bundle hash. A CDN purge fails. A third-party provider has an outage. The page "loads" but doesn't work.
How to close the gap
The only way to catch "up but broken" failures quickly is to monitor at the asset level — not just the server level. This means fetching the page, parsing the HTML, and validating every linked resource. Combined with deploy-triggered checks, detection time drops from hours to minutes.
Minimizing cost
How to minimize the cost of downtime
Monitor beyond uptime
Uptime monitoring catches server outages. Website monitoring catches the "up but broken" failures that cost more because they go undetected longer. You need both layers.
Check after every deploy
Most outages happen right after a deploy. Deploy hooks that trigger instant website checks catch regressions in minutes, before customers notice.
Alert the right channel
An email alert at 3 AM doesn't help. Route alerts to Slack, Discord, or PagerDuty where your on-call team will see them immediately. Every minute of faster detection is money saved.
Have a rollback plan
When a deploy breaks something, the fastest fix is rolling back to the previous version. Ensure your CI/CD pipeline supports instant rollbacks and your team knows the procedure.
Downtime cost FAQ
Start with: (annual online revenue / 8,760 hours) = cost per hour. Then add indirect costs: engineering time ($150-250/hr per engineer), customer support time, SEO recovery time, and customer lifetime value for lost customers. The indirect costs typically 2-5x the direct revenue loss.
Yes, because detection time is dramatically longer. A total outage is typically detected in 1-5 minutes. An "up but broken" failure (broken JS, missing checkout form, failed payment script) often goes undetected for hours because uptime monitors show green. Longer detection = more revenue lost.
If monitoring catches even one "up but broken" failure per month 3 hours earlier than manual detection, and your site generates $500K/year, that's roughly $170 saved per incident. Sitewatch Pro costs $19/month ($190/year). One faster catch pays for a year of monitoring.
Downtime is expensive. Prevention is cheap.
Free plan available. Monitor your site before the next outage.