StatusCake

The Cost of Website Downtime

With Black Friday and Cyber Monday just behind us and the Christmas and January sales on the horizon, the cost of downtime is a question that should be of concern to all business owners and e-commerce managers. It should be a concern, but is website downtime always given the consideration it deserves in your business?

A company website is a critical component of any modern business, but for businesses who rely on online sales, it really is of paramount importance. The continued success of your business depends upon the ability of your website to remain fully operational, to be able to deliver the seamless experience that your online visitors have come to expect from your website.

Once your website fails to meet those expectations, however briefly, the ramifications for your business can be significant, resulting in revenue loss, damage to your brand reputation, and even a decline in search rankings.

In this article, we’ll take a look at how we calculate website downtime and how that translates into meaningful data for your business.

How is Website Downtime Calculated?

Before we attempt to understand the cost of website downtime, it may be helpful to look at how downtime itself is calculated. Here at StatusCake, we specialise in website monitoring and have unparalleled experience in analysing website downtime across different industries and sectors.

Website uptime is generally measured as a percentage. This percentage is calculated by the number of times the availability of a particular website was tested, divided by the number of times an error was recorded. For example, a website which was available every time it was tested would return a website uptime average of 100 percent, while a domain that was down every time a test was performed returns an average website uptime of 0 percent.

Calculating the Cost of Website Downtime

Using the aforementioned calculation, we are able to measure how often websites are online as a percentage, but how can that be converted into units of time, and later, sales and revenue? As website uptime specialists, we have created our own Uptime and Downtime Cheat Sheet, a resource which we can use to translate uptime percentages into monthly and yearly downtime in days, hours, and minutes.

Here’s how average uptime scores translate periods of downtime on a monthly and yearly basis:

  • 99 percent uptime: 7 hours, 12 minutes downtime. 3 days, 15 hours, and 36 minutes of yearly downtime.
  • 98 percent uptime: 14 hours, 25 minutes downtime. 7 days, 7 hours, and 12 minutes of yearly downtime.
  • 97 percent uptime: 21 hours, 36 minutes downtime. 10 days, 22 hours, and 48 minutes of yearly downtime.
  • 96 percent uptime: 1 day, 4 hours, and 48 minutes of monthly downtime. 14 days, 14 hours, and 24 minutes of yearly downtime.
  • 95 percent uptime: 1 day, 12 hours of monthly downtime. 18 days, 6 hours of yearly downtime.

In these calculations, you can clearly see how a short period of website downtime can quickly add up over a period of weeks and months into a significant period of time in which your website is out of action. 99.9 percent uptime is generally considered to be a very competitive average, but even this level of downtime results in 8 hours and 46 minutes of downtime over the course of a year. Is your website meeting that target, or are you falling below it?

It is often said that time is money, and nowhere is that more applicable than in the world of online sales. Website downtime truly does come at a high cost, with the cost incurred to your sales, reputation, and search engine rankings increasing exponentially the longer your website is offline.

When it comes to calculating potential revenue lost following a period of downtime, the picture is slightly more complex. Here, there is no absolute figure which can be used to accurately determine an average and will vary hugely according to the duration of downtime, the time of day, and the date. Website downtime which occurs in the early hours of a Sunday morning, for example, will not be as catastrophic for your bottom line as downtime during peak hours of the Black Friday sales.

The volume of sales generated by your website is also another variable to consider. For example, if you generate an average of £1,000 in revenue per hour, then every minute your website is offline is an average cost of £16.66 in lost sales. In this calculation, lost revenue increases rapidly for larger businesses, with any sustained period of downtime quickly adding up to eye-watering amounts. To take one of the most extreme examples of this fact, a period of downtime for e-commerce giant Amazon on ‘Prime Day’ is estimated to have cost the retailer as much as $100 million in lost sales!

Clearly, armed information presented in this article, the uptime of your website should not be considered as an afterthought, but as a pressing priority that could make or break your business. Seen in this context, the cost of a dedicated website monitoring service such as that provided by StatusCake should be seen as a long term investment rather than an unnecessary expense. Time is money online, and few businesses can afford to leave money on the table due to unscheduled website downtime.

Share this

More from StatusCake

When Code Becomes Cheap: The New Reliability Constraint in Software Engineering

4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,

Buy vs Build in the Age of AI (Part 3)

5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t

Buy vs Build in the Age of AI (Part 2)

6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff

Buy vs Build in the Age of AI (Part 1)

5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything

Alerting Is a Socio-Technical System

3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting

Designing Alerts for Action

3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.