How do I calculate the cost of website downtime for my business?

Use this formula: (hourly revenue + hourly ad spend) multiplied by hours down, then multiplied by a trust multiplier between 1.2 and 1.5 to account for customers who do not come back. To get hourly revenue, divide your monthly online revenue by 720. To get hourly ad spend, divide your monthly Google and Meta spend by 720. Run the formula for a realistic outage length like 2 hours and for a worst case like 8 hours, so you can see the range.

Is website downtime really that expensive for a small business?

It adds up faster than most owners expect. A small Shopify store doing 30,000 dollars a month in revenue loses about 42 dollars an hour in direct sales, plus any ad spend burning during that window, plus the long tail of customers who bounce and never return. A two hour outage at peak time can easily clear 200 to 400 dollars once you include wasted ads and trust damage. Over a year, even a 99.5 percent uptime site is offline for roughly 44 hours.

Does website downtime hurt SEO rankings?

Short outages under a few hours are usually tolerated by Google. Longer or repeated outages are not. If Googlebot hits your site and gets 5xx errors or timeouts for more than a day, Google can temporarily drop affected pages from the index until it confirms they are stable again. Google's own guidance says to return a 503 status code for planned maintenance so the crawler knows to come back, rather than letting pages fail with a generic error.

Why do my ad campaigns make downtime more expensive?

Google Ads and Meta Ads keep spending your budget the entire time your site is down. Every click still costs you, but zero of those visitors can convert. On a 50 dollar a day ad budget, an 8 hour outage during peak hours can burn 30 to 50 dollars on clicks that land on an error page. The ad platforms also factor landing page experience into ad quality, so a bad outage can affect your scoring until the platform re-evaluates.

What kinds of outages does a basic ping monitor miss?

A basic ping monitor only checks that your homepage returns a 200 status code. It cannot tell you that your checkout is broken, that your login page is returning a blank screen after a plugin update, that Stripe.js failed to load, or that your cart is silently rejecting submissions. These partial failures are the most expensive kind of downtime because the site looks fine from the outside while customers cannot actually buy anything. You need content assertions and browser login monitors to catch them.

Can I monitor my website for free without a credit card?

Yes. Velprove offers a free plan with no credit card required that runs HTTP checks, content assertions, multi-step API monitors, and browser login monitors that log into session-based sites like WordPress, WooCommerce, and WHMCS. You get email alerts and a public status page. Checks run every 5 minutes on free, down to 30 seconds on paid plans. For a small business, the free plan is usually enough to catch the outages that would have cost you hundreds of dollars.

Guide

Website Downtime Cost: What It Really Costs a Small Business

April 14, 20269 min read

The true website downtime cost for a small business is almost always three to five times what owners estimate. Most assume two things about downtime. First, that it is rare. Second, that when it does happen, the cost is small because you can just fix it and move on. Both assumptions are wrong, and the gap between what owners think downtime costs and what it actually costs is one of the most expensive blind spots in running a small business online.

The reason is simple. When your site goes down, the damage is not a single number. It is four separate costs stacking on top of each other at the same time, and most owners only ever see one of them. This post walks through all four, gives you a formula to plug your own numbers into, and shows you how to stop paying that bill for free.

The four real costs of website downtime

When a small business site is down for an hour, the invoice you never see looks like this.

1. Lost transaction revenue

This is the obvious one. If your store normally does 30,000 dollars a month in online sales, you are clearing about 42 dollars an hour, every hour, on average. At peak hours that number is two or three times higher. Every minute your checkout is broken is a minute of revenue that does not land in your account, and in most cases it does not come back later. A customer who hits a broken cart does not usually come back in an hour to retry. They go to a competitor.

This cost is actually the smaller piece of the puzzle for most small businesses. The other three are where the real damage lives.

2. Wasted ad spend

Here is the part that blindsides almost everyone. Google Ads and Meta Ads do not pause when your site goes down. Your campaigns keep running, your budget keeps burning, and every click you pay for lands on an error page instead of a product page. A small business spending 50 dollars a day on ads is spending about 2 dollars per hour all day long, and closer to 4 or 5 dollars per hour during peak traffic windows. An 8 hour overnight outage during a holiday sale can burn through 20 to 40 dollars in clicks with zero conversions.

It gets worse. Google and Meta both factor recent landing page experience into ad quality. A burst of clicks landing on an error page can hurt your landing page experience score until the platform re-evaluates after things recover. The ad bill from a single bad night can quietly echo into the following week.

3. SEO damage on prolonged outages

Google tolerates short outages. If your site is down for 20 minutes and Googlebot happens to hit it, the crawler will back off and try again later. No harm done. The problem is when outages last hours or repeat often. If Googlebot keeps getting 5xx errors or timeouts across a day or more, Google can temporarily drop the affected pages from search results until it confirms they are stable. Google Search Central recommends returning a 503 status code for planned downtime so the crawler treats it as temporary instead of a hard error.

For a small business that relies on organic search for leads or sales, a ranking drop is the single most expensive kind of downtime. You do not just lose the sales during the outage. You lose the sales for the two or three weeks it takes your rankings to recover.

4. Customer trust erosion

This one is the hardest to measure and the easiest to underestimate. Your customers do not know whether your site is down because of a hosting issue, a plugin conflict, or your credit card on file with the domain registrar expiring. They just know it did not work when they tried to use it. If they were already shopping, they go to a competitor. If they were a repeat customer, they start to wonder if you are still in business. If they came from an ad, they remember the brand as the one with the broken website.

Analyst firms like Gartner and IBM have published downtime cost estimates for enterprise IT for years, and the numbers vary wildly depending on company size and industry. The useful takeaway for a small business is not a headline figure. It is the pattern. Every serious study finds that indirect costs, trust, brand, and follow-on customer loss, are larger than the direct revenue loss during the outage itself. That is why the formula below uses a trust multiplier.

A simple formula you can run on your own numbers

How much does website downtime cost?

Website downtime cost is the sum of lost transaction revenue, ad spend that burned on clicks to an error page, SEO damage from prolonged crawl errors, and the long tail of customer trust loss. Any small business owner can estimate it in 60 seconds on the back of a napkin with this formula.

Downtime cost = (hourly revenue + hourly ad spend) × hours down × trust multiplier

The trust multiplier captures the customers who bounced and never came back, plus any ranking and quality score damage. A reasonable range is 1.2 for a short mid-day outage to 1.5 or higher for a long peak-hour outage on a site that depends on ads or SEO. Here are three worked examples.

Example 1: A Shopify store doing 30k per month

Hourly revenue: 30,000 / 720 hours = about 42 dollars
Hourly ad spend (50 dollars per day): about 2 dollars
Outage length: 2 hours at peak time
Trust multiplier: 1.4
Cost: (42 + 2) × 2 × 1.4 = about 123 dollars

That is the cost of one short outage. A store that has four of those a year is leaving roughly 500 dollars on the table annually, from something a monitor would have caught in the first few minutes.

Example 2: A lead-gen site for a local services business

Hourly revenue: treat the average lead value as 80 dollars, and the site produces 1 lead per hour on average, so 80 dollars
Hourly ad spend (Google Local Services, 100 dollars per day): about 4 dollars
Outage length: 4 hours overnight
Trust multiplier: 1.2 (overnight, lower traffic)
Cost: (80 + 4) × 4 × 1.2 = about 403 dollars

Example 3: A small SaaS on a monthly plan

Direct MRR loss during a 90 minute outage is small in absolute terms, but paying customers are unforgiving and a SaaS lives or dies on trust. Treat the cost as a churn risk estimate rather than a formula run, because the formula was designed for transactional sites.

MRR base: 5,000 dollars per month
Outage length: 90 minutes during a workday
Estimated incident cost (lost MRR from churn risk plus support load): 200 to 400 dollars per incident

Notice the pattern. Even conservative numbers land between 100 and 500 dollars per incident for a small business. Three or four of those a year is a new laptop, or a month of rent on an office, or a year of your accounting software.

Why "I'll just notice" is not a plan

Almost every small business owner we talk to has the same fallback. They say they will notice if the site goes down, because they check it a few times a day. This does not hold up for two reasons.

First, most outages do not happen when you are looking. They happen at 2 a.m. on a Sunday when a plugin auto-updates, or during a deploy, or when a DNS record expires on a weekend, or when a server reboots for a kernel patch. The cost of downtime is not spread evenly across the week, and neither is your attention.

Second, and this is the bigger one, partial failures do not look like downtime to a human spot check. The homepage loads. The nav works. The product pages look fine. But the checkout button throws a JavaScript error, or the login page accepts your password and then redirects in a loop, or the cart submits and silently drops. A quick glance at the site will not catch any of that. A basic ping monitor that only looks at HTTP 200 codes will not catch it either. These are the most expensive outages because they can run for hours with nobody noticing until a customer emails support, and by then the ad spend is already gone.

How free monitoring closes the gap

The good news is that every cost in this post is preventable with a decent monitoring setup, and you do not need to pay for one. Velprove offers a free plan, no credit card required, that covers exactly the failures a small business site has.

No other free monitoring tool offers this. The feature that matters most for partial failures is our browser login monitor. Instead of just pinging your homepage, Velprove launches a real browser behind the scenes and does what your users do. It loads your login page, types in a test account, clicks submit, waits for the redirect, and verifies that authentication actually worked. If your WordPress dashboard, WooCommerce checkout, WHMCS portal, or custom SaaS login ever breaks, you know in minutes, not the next time a customer emails you. That is the single highest-leverage monitor a small business can set up, and on Velprove it is free forever, no credit card.

On top of that, the free plan includes HTTP checks with content assertions so you can verify the checkout button is actually on the page, a public status page your customers can bookmark, and email alerts that fire as soon as a check fails. Most small business sites need three monitors. One for the homepage, one for the checkout or contact page with a content assertion, and one browser login monitor for your customer or admin login area. That is usually enough to eliminate every cost in the formula above.

Where to go next

If you are brand new to this, start with our website monitoring guide for beginners. It walks through exactly what to monitor and why, with no jargon.

If you run a Shopify store, the playbook is in how to monitor your Shopify store for uptime and broken product pages. If you run WooCommerce, the silent revenue killer you need to catch is the checkout, and we have a full guide on monitoring the WooCommerce checkout so broken payments never cost you a sale.

Whichever platform you are on, the math is the same. A small business site that is down even 0.5 percent of the year, which is the industry baseline for shared hosting, is offline for roughly 44 hours annually. At 120 dollars per incident, that is real money. At zero dollars per month for a monitor that actually catches it, the decision is straightforward.

Create a free Velprove account and set up your first monitor in 2 minutes. No credit card, no trial clock, no downgrade surprise.