StatusCake

Getting Ready for Black Friday – Month-by-Month Preparation

computer-screen

Black Friday will be here before you know it, ushering in four of the busiest days for online retailers. Most consumers view the period from Black Friday to Cyber Monday as an ideal opportunity to score some bargains, both in brick-and-mortar stores and online. Online shopping during this four-day shopping window has become especially popular, with traffic increasing by 20% to 25% each year for the past few years.

There is every reason to believe that this trend will continue this year, and it’s not too early to begin planning for this year’s onslaught. Last year, the websites of many online retailers experienced slow loading times during this period, and some even crashed for several hours. Here are a few steps that you can take to get ready to help you avoid becoming a casualty during this key shopping period.

One of the first things that you should do is look at your website’s infrastructure. May and June represent an excellent opportunity for you to evaluate how your website is performing and to carry out any routine maintenance required to ensure that your site is ready for the expected increase in traffic. Evaluate your infrastructure with the goal of avoiding any downtime for maintenance during the peak selling season. These two months are also an excellent time to install any new services.

July is the perfect time to test your website’s performance to look for any issues that might affect the loading time. Look at your historical traffic data for this four-day period, and evaluate your ability to handle Black Friday’s increased traffic loads, assuming that traffic will increase over last year. Also, see whether you have any applications that are particularly sensitive to increases in traffic. If you find any areas that present a challenge, this is the time to install the technology that will mitigate the problem.

In August, freeze the implementation of any updates to your website’s infrastructure. Then, look at your analytical data again to uncover any potential weaknesses remaining. Conduct load tests of your site to be sure that any changes that you made in July are performing as expected. Testing high loads in August gives you adequate time to make any changes before Black Friday arrives.

In September and October, evaluate any natural increase in traffic loads. You should start to see a natural increase in traffic loads by October, and analyzing real traffic data rather than the artificial traffic that you used for load testing can often uncover some surprises. Check your site daily to ensure that it is handling increased traffic loads efficiently. At this point, your preparations for Black Friday should be complete.

In November, continue your daily traffic analysis. If you’ve been checking your analytics during the past six months, you should only need to make minor adjustments as your traffic increases. Expect exceptionally large traffic loads on Black Friday, with spikes of up to 15 times the average traffic for a typical day during the rest of the year being possible.

Come December, evaluate how your site performed, and use the results of that analysis to help you plan for the peak shopping season in 2018.

Share this

More from StatusCake

A Notification List Is Not a Team

3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

When AI Speeds Up Change, Knowing First Becomes the Constraint

5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things

Make Your Engineering Processes Resilient. Not Your Opinions About AI

4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development.  For some teams, it’s an obvious productivity multiplier.  For others, it’s viewed with suspicion.  A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

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.