Black Friday Website Readiness Checklist: 20 Checks

Black Friday readiness is about the whole transaction path, not the homepage. Shopify saw its 2025 peak of $5.1 million per minute at 12:01 p.m. EST on Black Friday. Assign owners, freeze changes, load test cart to confirmation, cache and monitor, plan outages so search crawling is not hurt, and rehearse support before Friday 27 November.

When traffic really peaks, and what that means

Black Friday readiness is about the whole transaction path, not the homepage, and the peak is probably earlier in the day than you think. Shopify reported that its merchants sold $14.6 billion across Black Friday and Cyber Monday in 2025, up 27%, and reached a peak of $5.1 million in sales per minute at 12:01 p.m. EST on Black Friday. The figures are approximate and unaudited, but they show how concentrated the surge is.

$5.1M Shopify merchants' peak sales per minute, reached at 12:01 p.m. EST on Black Friday 2025 (approximate and unaudited)

Infrastructure providers saw the same surge. Vercel reports more than 115.8 billion requests across its BFCM 2025 weekend, a peak of 518,027 requests per second, and over 56.9 billion requests served from its global cache. This year Black Friday is Friday 27 November and Cyber Monday is Monday 30 November, and Adobe forecasts $12.9 billion and $15.1 billion of US online sales on those days. The checklist below is built around 20 checks and a dated timeline, and it pairs with our BFCM 2026 playbook for the marketing side.

Set the freeze, the owners and the rollback plan

Most Black Friday incidents are caused by last-minute changes, so decide who can change what, and when, before the pressure starts.

  1. Name one owner for each part of the journey: storefront, cart, checkout, payments, inventory, fulfillment and support.
  2. Agree a soft freeze on Monday 16 November, when only reviewed fixes go in, and a hard freeze on Wednesday 25 November. These dates are our suggestion.
  3. Identify the last known good version of the site, and who is allowed to roll back to it.
  4. Agree the signals that trigger a rollback, such as error rate, checkout completion or payment failures.
  5. Confirm that everyone on call has the access they need, and test it before the day.

Vercel's guide adds a useful warning: a freeze reduces unnecessary risk, but teams should not only watch dashboards, so preparation has to give people the confidence to act when something breaks.

Test the whole transaction path, not the homepage

A fast product page does not prove checkout will hold. Vercel advises testing the path separately, and its list of steps is a good template.

Transaction path: what to test before the sale
StepWhat to testPass looks like
Promo codesStacking, expiry, single-use and bad codesEvery rule behaves as written
Cart recalculationQuantity edits, shipping thresholds, taxesTotals match your own calculation
Inventory checksLast-unit purchases and parallel buyersNo overselling; clear sold-out messages
Payment initiationCards, wallets, declines and retriesClear errors; no double charges
Fraud and tax servicesResponses under loadCheckout still completes within your target
Order creation and confirmationEmails, order numbers, receiptsEvery order is recorded and confirmed

Base the test size on your own history. Use last year's analytics, or the nearest comparable sale, to find where traffic, errors and abandonment peaked, and test at a level above it. Run at least two rounds, one early enough to fix what you find and one after the soft freeze. Our mobile checkout checklist covers the phone experience in depth.

Keep pages fast, cached and bot-aware

Speed protects both conversion and capacity. Google's Core Web Vitals thresholds, measured at the 75th percentile, are largest contentful paint within 2.5 seconds, interaction to next paint of 200 milliseconds or less and cumulative layout shift of 0.1 or less. Deloitte Digital, for Google, found a 0.1-second mobile speed gain raised retail conversion by 8.4%.

  • Cache high-traffic pages and assets. Vercel reports that about 49% of its BFCM 2025 requests, 56.9 billion of 115.8 billion, came from cache.
  • Move non-critical work, such as analytics calls and personalization, out of the checkout response path.
  • Audit third-party scripts and remove any that slow checkout without earning their place.
  • Review firewall and bot rules before the peak. Vercel counted over 7.5 billion firewall actions and over 415 million bots blocked over its BFCM weekend, so bot traffic is real load.
  • Check that a new rule does not block search or AI crawlers you want. Google asks you to confirm that your CDN and host allow crawling, and our AEO checklist explains which agents to allow.

Plan downtime so it does not cost you search visibility

An outage hurts sales first, and then it can hurt visibility. Google explains that 5xx and 429 errors make its crawlers slow down, that the drop in crawl rate is proportionate to the number of URLs returning errors, and that indexed URLs are preserved at first but eventually dropped if they persistently return server errors. Once your server returns normal responses, Google gradually raises crawling again.

So keep any outage short and narrow. The Google page does not say which status code to use for planned maintenance, so these are our recommendations rather than Google rules.

  • Prepare a static fallback page and a clear status message that you can switch on in minutes.
  • Avoid serving an error message with a normal success status, because search engines may treat it as real content.
  • Post status updates where customers look, such as your site banner and social accounts.
  • After the weekend, check Search Console for crawl errors and indexing changes.

Check checkout, payments and discount logic

Checkout is where traffic turns into revenue, and small friction costs a lot. Baymard finds 70.22% average cart abandonment, with extra costs the top reason at 40%, required account creation at 18%, card declines at 10% and too few payment methods at 9%. Digital wallets matter too: Shopify reported that 32% of orders in its 2025 BFCM period used Shop Pay.

  • Show the full total, including shipping and tax, before the last step.
  • Offer guest checkout and test every wallet you advertise on a real phone.
  • Write clear messages for declined cards and out-of-stock items.
  • Ask your payment provider how it communicates incidents and whether you have a second option for emergencies.
  • Test 10 discount combinations, including free-shipping thresholds and expired codes, before launch.

Prepare support, fraud checks and returns

The sale does not end at checkout. NRF and Happy Returns found that retailers expect 17% of holiday sales to be returned, that 82% of shoppers call free returns a major purchase factor, and that 9% of returns are fraudulent. Plan for the questions that follow every sale.

  • Write ready answers for "Where is my order?", shipping cutoffs, returns and promo-code problems.
  • Publish a returns policy with the window, who pays shipping and how refunds work.
  • Set simple fraud checks, such as order and card matching, that do not slow honest customers.
  • Staff support for the peak hours, and agree who handles escalations.

The 20 checks and a dated timeline

Use the table as your worksheet. Each area has four checks, and each check needs an owner and a date.

The 20 checks, by area
AreaFour checks
Ownership and change controlOwners named; soft and hard freeze dates set; rollback version and authority agreed; on-call access tested
Load and speedTransaction path tested twice; Core Web Vitals met on top pages; third-party scripts audited; caching confirmed
ResilienceMonitoring thresholds set; static fallback ready; status message drafted; bot and firewall rules reviewed
Checkout and promosTotals shown early; guest checkout and wallets tested; decline messages clear; discount combinations tested
Support and returnsAnswers written; returns policy published; fraud checks set; peak-hour staffing planned

Then put the work on a calendar. Illustrative sequence, counting from today, Thursday 5 November:

  1. Thu 5 Nov: name owners and pull last year's peak hours and error data.
  2. Mon 9 to Fri 13 Nov: run the first load test and fix the worst findings.
  3. Mon 16 Nov: soft freeze begins.
  4. Tue 17 to Fri 20 Nov: retest and fix; finish support answers and the status page.
  5. Mon 23 Nov: final test and on-call roster confirmed.
  6. Wed 25 Nov: hard freeze.
  7. Thu 26 Nov: Thanksgiving; keep someone on watch.
  8. Fri 27 Nov: watch closely through the late morning and lunch hours in your main time zone.
  9. Mon 30 Nov: Cyber Monday; repeat the watch.
  10. Tue 1 Dec: hold a short review and write down what to change next year.

If you want an outside team to run the tests, our web and app development team and conversion rate optimization team work with ecommerce brands on exactly this, and our wasted ad spend audit checks that your campaigns are not sending traffic to a page that will fail. Our Black Friday SEO and AEO guide covers visibility during the sale.

Sources and method

Shopify, Google, Baymard, NRF and Adobe are primary sources read in October 2026. Vercel figures and advice are the vendor's own platform data and guidance, not an industry standard. Adobe figures are forecasts. The freeze dates, the downtime recommendations, the 20-check structure and the timeline are our judgment.

  • Shopify, BFCM 2025 results (primary; approximate and unaudited)
  • Vercel, Black Friday preparation guide (vendor; own platform data)
  • Google Search Central, HTTP status codes and network errors (primary)
  • web.dev, Web Vitals (primary)
  • web.dev, Milliseconds Make Millions (Deloitte Digital for Google) (primary research)
  • Baymard Institute, cart abandonment rate statistics (primary research)
  • NRF and Happy Returns, 2025 returns report (primary)
  • Adobe, US holiday shopping season forecast, 28 September 2026 (primary; forecast)

Data last verified 28 October 2026. Researched with AI assistance from the primary sources linked here, then edited by the Eonixmedia team; figures are linked to their source.

Want a readiness review before 27 November? Talk to us and we will walk the transaction path with you.

Questions people ask

When is the busiest time on Black Friday for an online store?

Shopify reported that its merchants hit a peak of $5.1 million in sales per minute at 12:01 p.m. EST on Black Friday 2025. That suggests the lunchtime hours on Friday 27 November deserve your closest watch, although your own store may differ. Use last year's analytics to find your real peak hour.

How do I load test an ecommerce site before Black Friday?

Test the whole transaction path, not just pages. Vercel advises separate tests for promo codes, cart recalculation, inventory checks, payment initiation, tax, fraud checks, order creation and confirmation, because a fast product page does not prove checkout will hold. Run at least two rounds so you can fix and retest.

What should my site do if it goes down on Black Friday?

Keep the outage short and have a plan. Google says 5xx and 429 errors slow its crawling, and URLs that persistently return server errors are eventually dropped from the index. Prepare a status message, a static fallback page and a rollback to your last known good version, and decide in advance who can trigger it.

When should I freeze code before Black Friday?

There is no universal date. We suggest a soft freeze on Monday 16 November, with only reviewed fixes after that, and a hard freeze on Wednesday 25 November, the day before Thanksgiving. Vercel warns that freezes reduce risk but teams must still be ready to act on problems, so keep a rollback and an on-call roster.

Do digital wallets matter for Black Friday checkout?

They help. Shopify reported that 32% of orders in its 2025 BFCM period used Shop Pay, and that sales through it grew 39%. Baymard finds that not enough payment methods and a required account each cause some abandonment, so test wallets and guest checkout on real phones before the sale.

How do I protect search rankings during a Black Friday outage?

Reduce the number of failing URLs and the time they fail. Google says crawl rate drops in proportion to the number of URLs returning server errors and recovers gradually after the server returns normal responses. Avoid long outages, avoid blocking search crawlers with new firewall rules, and check Search Console after the weekend.

Related services

  • Web App Development
  • Conversion Rate Optimization
  • Analytics Revops

More from Eonixmedia Insights

  • Black Friday Landing Page and Mobile Checkout Checklist
  • Black Friday Pricing Strategy: Offers That Protect Margin
  • Black Friday SEO and AEO: Rank and Get Cited in 2026
  • Black Friday Email Marketing: 2026 Email and SMS Calendar