The Website Downtime Cost Calculator: How Much One Bad Hour Really Costs

One bad website hour can cost more than a year of maintenance.

That sounds dramatic until you run the numbers. Atlassian’s incident management guide estimates small-business downtime at $137 to $427 per minute. Uptime Institute’s 2025 outage analysis says power remains the leading cause of impactful outages, IT and networking issues reached 23% of impactful outages, and nearly 40% of organizations had a major outage caused by human error over the prior three years. IBM’s 2025 breach research found operational disruption affected 31% of studied breached organizations.

Most business owners still treat downtime like a hosting problem. It isn’t. It’s a sales problem, a payroll problem, a trust problem, and sometimes a legal problem.

This calculator gives you a practical way to price one hour, one day, or one weekend of downtime. You don’t need enterprise monitoring software. You need honest inputs and a willingness to count the costs that usually get ignored.

The Simple Downtime Cost Formula

Use this as your starting point:

Total downtime cost = lost revenue + lost leads + wasted payroll + ad waste + support cost + recovery cost + trust damage

For a small business, the number is often lower than scary enterprise averages but higher than the owner expects. A local contractor might not lose $300,000 in an hour. But if a website outage kills three quote requests, wastes paid traffic, triggers ten confused customer calls, and makes a referral prospect question whether the company is still in business, the damage is real.

Here’s the worksheet version:

Don’t worry if a few fields are estimates. A rough number beats pretending the outage was free.

Step 1: Calculate Lost Revenue

If your site takes payments, books appointments, sells subscriptions, or accepts deposits, start with direct revenue.

Lost direct revenue = average online revenue per hour × downtime hours

Example: an e-commerce store does $36,000 per month in online sales. Using a 30-day month, that’s about $50 per hour across the full month. A six-hour outage looks like $300 in lost sales.

That number is probably too low because downtime rarely spreads evenly. A two-hour outage during a Tuesday lunch rush, a Friday sale, or a seasonal buying window hurts more than a quiet Sunday morning. If you know your peak conversion hours, calculate downtime against those hours instead of the monthly average.

Cart behavior matters too. Baymard Institute’s running cart-abandonment benchmark puts average cart abandonment around 70.22% across 50 studies. If your checkout breaks while shoppers are already nervous about shipping, tax, or payment security, many won’t come back later just because the site is fixed.

For service businesses, direct revenue is usually less obvious. A broken booking form, quote form, financing application, or payment link can still create lost revenue. If your website is the front door for sales conversations, downtime blocks the door.

Step 2: Calculate Lost Lead Value

Lead value is where small-business downtime gets expensive.

Lost lead value = missed leads × close rate × average deal value

Let’s say your site normally generates 90 leads per month. That’s 3 leads per day. Your close rate is 30%, and your average new customer is worth $4,500. A full-day outage could cost:

3 missed leads × 30% close rate × $4,500 = $4,050 in expected revenue

That doesn’t mean exactly $4,050 vanished from the bank account that day. It means the outage removed expected sales pipeline value. If your sales cycle is long, the loss may show up next month, not this week.

This is why lead tracking matters. If you don’t know how many forms, calls, chats, or booking requests your site creates, you can’t price downtime accurately. Portent’s site speed research found that a site loading in 1 second has a conversion rate 3x higher than a site loading in 5 seconds. A fully down site converts at zero. Slow is a leak. Down is a shutoff valve.

The same logic applies to phone calls. Many prospects visit your website first, then call. If the site is down, the call never happens because the prospect never gets the phone number, service details, or confidence they needed.

Step 3: Count Wasted Payroll

Downtime often ties up people who were supposed to be doing higher-value work.

Wasted payroll = blocked staff × loaded hourly cost × blocked hours

Loaded hourly cost means wages plus taxes, benefits, software, management overhead, and the real cost of having that person unavailable. If a $30-per-hour employee costs closer to $42 per hour fully loaded, use $42.

Common examples:

• Sales staff can’t access the CRM form submissions they use for follow-up.
• Customer service takes calls from people asking whether the business is open.
• Marketing pauses campaigns and writes apology emails.
• The owner spends the morning texting the web person instead of closing work.

Uptime Institute’s 2025 analysis is useful here because it points directly at process risk. It found that 85% of major human-error outages stemmed from staff failing to follow procedures or flaws in the procedures themselves. In plain English, many outages are not freak accidents. They happen because updates, access, backups, DNS, plugins, hosting, or deployment steps were not controlled tightly enough.

If your team spends four hours cleaning up something that a maintenance plan should have prevented, that payroll belongs in the downtime cost.

Step 4: Count Paid Traffic Waste

If ads keep running while the site is broken, you’re paying to send people into a locked building.

Ad waste = paid clicks during outage × average cost per click

Example: you spend $6,000 per month on Google Ads. That’s about $200 per day. If your site is down for one business day and campaigns keep running, at least $200 is wasted before you count lost conversions.

The bigger issue is quality. If a searcher clicks your ad, sees an error page, and goes back to Google, you’ve paid for a bad first impression. Google’s own mobile page-speed research found that as page load time rises from 1 second to 10 seconds, the probability of a mobile visitor bouncing increases 123%. An outage is worse than a slow page because the visitor gets no useful answer at all.

Build this into your incident plan: if the site is down for more than a few minutes and paid traffic is material, pause campaigns or route ads to a working backup landing page.

Step 5: Count Support Load

Downtime creates contacts your team wouldn’t otherwise handle.

Support cost = extra calls, emails, chats, or tickets × cost per interaction

A broken login page creates password-reset requests. A failed checkout creates order-status questions. A down service page creates phone calls from prospects who just want to know whether you serve their area.

IBM’s customer service cost research cites average human support interaction costs of $8.01 for a phone call, $4.50 for live chat, and $1.00 for self-service. Your numbers may differ, but the principle holds: when the website stops answering simple questions, your people have to answer them manually.

Support load also slows recovery. The same person who could be testing forms, checking DNS, or communicating with the developer is now explaining the outage one customer at a time.

Step 6: Count Recovery Cost

Recovery is not just the invoice from your developer.

Recovery cost = internal labor + outside labor + tools + emergency fees

Include:

• Developer or agency emergency time
• Hosting support upgrades or restore fees
• Security cleanup if the outage came from malware
• Copywriting and email time for customer updates
• Testing time after the fix
• Monitoring or backup tools purchased after the fact

IBM’s 2025 breach report says breaches involving data spread across multiple environments cost an average of USD 5.05 million, compared with USD 4.01 million for data breached on premises. Most small-business website incidents are not million-dollar breaches. Still, the lesson is relevant: complexity raises recovery cost. A simple site with documented hosting, backups, DNS, plugins, passwords, and deployment steps is cheaper to fix than a mystery stack nobody has touched in two years.

If your web setup depends on one freelancer, one old password, one expired credit card, or one plugin nobody updates, your recovery cost is higher than it looks.

Step 7: Put a Number on Trust Damage

Trust damage is the hardest line item, but ignoring it makes the calculator too optimistic.

A prospect who sees a broken website may not submit a complaint. They just leave. Forrester’s 2025 customer experience coverage reported that 21% of brands declined in its global CX rankings while only 6% improved. Webex’s 2026 customer experience roundup cites Futurum Group data that 72% of customers switch after three or fewer poor interactions.

That doesn’t mean one outage automatically loses 72% of your customers. It means customers have a limited tolerance for friction. A down website, a broken form, a slow response, and a vague follow-up can stack into a reason to choose someone else.

Use a conservative estimate. If a serious outage likely costs you one returning customer, one referral, or one deal that was already on the fence, add that expected value.

A Worked Example: The One-Hour Outage

Here’s a realistic example for a local service business that gets most new work through its website.

Business profile:

• 120 website leads per month
• 25% close rate
• $3,800 average first-project value
• $2,500 monthly ad spend
• 3 office staff affected
• $38 loaded hourly staff cost
• $125 per hour emergency developer rate

A one-hour outage during business hours might look like this:

That is one hour. Not a holiday weekend. Not a hacked checkout. Not a migration gone wrong.

If the outage lasts six hours, the cost doesn’t always multiply cleanly because prospects may retry later. But it can also get worse because staff interruptions, customer frustration, and recovery time compound.

The Downtime Prevention Checklist

You can’t prevent every outage. Uptime Institute notes that operators face external risks including power grid constraints, extreme weather, network provider failures, and third-party software issues. You can control the basics.

Use this checklist before the next bad hour:

1. Monitoring: uptime checks every 1 to 5 minutes, with alerts to more than one person.
2. Backups: automated daily backups, stored off the server, with a tested restore process.
3. Update process: plugin, theme, CMS, and dependency updates handled on a schedule, not randomly before a holiday.
4. DNS access: current registrar login, two-factor authentication, and documented nameserver settings.
5. Hosting access: owner-controlled billing and admin access, not trapped in a former vendor’s inbox.
6. Form testing: weekly test submissions for lead forms, checkout, booking, and contact forms.
7. Paid ads plan: clear rule for pausing campaigns or routing traffic if the main site fails.
8. Incident contact list: developer, host, domain registrar, payment processor, and internal decision maker.
9. Status message: prewritten customer update for outages that affect orders, appointments, or logins.
10. Post-incident review: what failed, what detected it, what fixed it, and what prevents a repeat.

The key is ownership. If nobody owns uptime, everyone assumes someone else is watching.

When Downtime Means You Need a Rebuild

A single outage may just mean something broke. Repeated outages usually point to a deeper website problem.

Consider a rebuild or serious technical cleanup if:

• Updates regularly break the site.
• Backups exist, but nobody has tested a restore.
• The site depends on abandoned plugins or an unsupported theme.
• Hosting support blames the developer, and the developer blames hosting.
• Forms fail silently.
• Page speed is poor even when the site is technically up.
• Nobody can explain how DNS, hosting, CMS, backups, and email fit together.

Google’s Core Web Vitals documentation focuses on LCP, INP, and CLS as field metrics for user experience. Those metrics are not uptime checks, but they point to the same business reality: technical quality affects whether visitors can use your site.

A fragile website is not cheaper. It’s deferred maintenance with interest.

FAQ

What counts as website downtime?

Downtime includes more than a blank screen. It can mean the site won’t load, checkout is broken, forms fail, DNS is misconfigured, SSL has expired, malware warnings appear, or key pages return errors.

How much does downtime cost for a small business?

Atlassian estimates small-business downtime at $137 to $427 per minute, but your actual number depends on lead value, revenue model, paid traffic, staff interruption, and recovery cost.

Is slow website speed a form of downtime?

Not technically, but financially it can act like partial downtime. Portent found 1-second load sites converted 3x higher than 5-second load sites, and Google’s mobile research found bounce probability rises sharply as load time increases.

What’s the first thing to fix?

Start with monitoring and backups. You need to know when the site fails, and you need a tested way to restore it. After that, clean up updates, hosting access, DNS ownership, and forms.

Want a Website That Doesn’t Quietly Leak Money?

If your website has had outages, broken forms, slow pages, mystery plugins, or hosting nobody really owns, don’t wait for the next bad hour.

Your Web Team can audit the setup, fix the weak points, and build a maintenance plan that protects leads instead of reacting after they disappear. Get started here.