Black Friday Website Monitoring: The 2026 Checklist for Online Stores

Black Friday website monitoring means checking more than whether your homepage loads: it means checking, every hour of the busiest week of the year, that a shopper can add a product to the cart, pick a shipping method and pay. In 2026 Black Friday falls on 27 November and Cyber Monday on 30 November. I run IThandy Monitor from Warsaw, Poland, for stores on PrestaShop, WooCommerce, Magento and Shopify, and this is the checklist I use with my own clients.

If you are reading this at the end of October, you have exactly four weeks. That is enough to do everything calmly.

Why Black Friday week is the worst time for an outage

An outage during Black Friday week costs many times more than the same outage on an ordinary Tuesday, because traffic, paid campaigns and buying decisions are all concentrated into a few days. A shopper who cannot pay you will pay a competitor within seconds.

What last season looked like:

• US shoppers spent $11.8 billion online on Black Friday 2025 and $14.25 billion on Cyber Monday, with $44.2 billion across Cyber Week. Between 8 and 10 p.m. on Cyber Monday they were spending $16 million every minute (Adobe).
• Across the whole 2025 holiday season (1 November to 31 December) US online spending reached $257.8 billion, and 56.4% of transactions happened on a smartphone (Adobe holiday recap).
• In Poland, one of the markets I work in, shoppers made nearly 30 million BLIK mobile payments worth almost 5 billion PLN over Black Weekend 2025, with the online peak on Cyber Monday (BLIK). Every market has a payment method like this: lose it at checkout and most buyers leave.
• In Baymard's survey of US shoppers who abandoned a checkout, 17% named website errors or crashes as the reason (Baymard).

What breaks in an online store under peak load

Peak traffic rarely creates new problems. It exposes weak spots that were already there, and rushed pre-sale changes add a few more.

The causes I see most often before and during Black Friday:

1. Pages that cannot be cached. Cart, checkout, search and logged-in pages always run PHP and hit the database. On shared hosting the worker limit runs out exactly there, while the cached homepage still looks perfect.
2. Third-party services inside checkout. Payment gateways, pickup-point maps, shipping rate calculators and pay-later widgets slow down when the provider is under peak load too. A module without a sensible timeout can freeze the entire checkout step.
3. Last-minute changes. A new promotions plugin, new cart rules, a theme update or a payment module update the day before launch. This is the number one source of avoidable Black Friday website crashes.
4. Bot protection set too aggressively. Cloudflare "Under Attack" mode, strict rate limits or a CAPTCHA at checkout can stop real customers and block payment gateway callbacks. I explain safe settings in my guide to PrestaShop bot protection with Cloudflare.
5. Cache hiding the outage. A server or CDN cache can keep serving the homepage long after PHP has stopped responding. Homepage-only monitoring will not notice.
6. Vanishing shipping and payment methods. New carrier rules, an order-total limit in a payment module, or a promoted product assigned to a single carrier. Causes and fixes are in my guide on payment or shipping methods missing at checkout.
7. Certificates and domains. Since 15 March 2026 public SSL certificates can be valid for at most 200 days (DNSimple, CA/Browser Forum), so renewals happen more often. A failed renewal in November means a browser security warning in the middle of your sale.

A 200 OK is not enough: what to monitor for Black Friday

A store can return HTTP 200 and still take no orders. That is why, for peak season, I monitor the whole customer journey layer by layer, not just whether the server answers.

The median tells you how the store behaves normally; the 95th percentile tells you how it behaves at its worst. During Black Friday week I watch the latter, because it rises first. More on how speed turns into revenue in my article on site speed and ecommerce conversion rates.

Black Friday checklist: four weeks, one week and one day before

The best time to prepare is late October, while you can still change configuration safely and let monitoring learn what "normal" looks like before the peak. Work through these steps in order.

Four weeks before (by about 30 October)

1. Turn on full monitoring: availability, product page, cart and checkout test. The first successful checkout test records a baseline of shipping and payment methods that every later test is compared with.
2. Allow the monitoring bot through your firewall (Cloudflare, hosting WAF), so a block is never mistaken for an outage.
3. Ask your host about limits: PHP workers, database connections, and what happens when they run out. If you can, load test a staging copy.
4. Check SSL certificate and domain expiry dates. Renew anything that expires before mid-January now.
5. List the payment and shipping methods your store cannot live without and mark them as required.

One week before (by about 16-20 November)

1. Start a code freeze: critical fixes only from now on. Schedule promotions to start and end automatically.
2. Test promotions on a staging copy, especially cart rules and free-shipping thresholds.
3. Add the products you are promoting to the pool that monitoring checks on the product page and in the cart.
4. Send a test alert and confirm the e-mail reaches whoever is on call, also on their phone.
5. Write down phone numbers and account IDs: hosting, payment provider, carrier, store developer. At 2 a.m. on Saturday there is no time to search for them.
6. Take a full backup of files and database and confirm you can actually restore it.

The day before launch

1. Place a manual test order on a phone, with your most popular payment and shipping method, up to the payment step.
2. Clear the cache after price changes and spot-check a few sale products.
3. Review rate limits and bot rules: make sure login, cart and payment gateway callbacks are not being blocked.
4. Confirm in the monitoring dashboard that every check is green and the payment and shipping baseline is current.

What to do during Black Friday week

During the sale you deploy nothing; you watch and respond according to alert severity. A response plan written in advance saves the most minutes.

• Critical alert (store down, cart broken, a required payment method gone): act immediately. Identify the stage first (server, cart, shipping, payment), then call the right person.
• Warning (slower server, certificate due for renewal): look at it within the hour, not in the middle of the night.
• Payment gateway down on the provider's side: hide the broken method, add a short notice for shoppers and mark the change as intended in monitoring. Once it is fixed, restore the method and confirm it is back in the baseline.
• Check orders stuck without payment status. If your firewall blocks the gateway's callback, the customer pays but the order stays "awaiting payment". A synthetic test cannot see that, so during the peak look at your order list every few hours.

Alerts go out by e-mail. Every outage is confirmed by a second check, so a single lost packet does not wake you at 3 a.m.

Cyber Monday and the day after

Cyber Monday is still the biggest online spending day of the season in the US, so do not relax after the weekend. Once the sale ends, check the store as carefully as you did before launch.

1. Confirm prices are back to normal and the promotions have switched off.
2. Confirm shipping and payment methods match the baseline again if you changed anything for the sale.
3. Review orders without payment status from the whole week.
4. Write down what happened: which alerts fired, how long they lasted, what worked. The monthly monitoring report shows availability and response times for the period.
5. Plan December. I cover the next peak in my guide to holiday season ecommerce monitoring.

How much does an hour of downtime cost on Black Friday?

You can estimate the cost of an hour of downtime with one formula: visitors per hour times conversion rate times average order value. Then add the ad spend that keeps sending people to a broken store.

Example (illustrative numbers, use your own analytics): a store with 2,000 visitors an hour at peak, a 2% conversion rate and a 100 EUR average order sells about 4,000 EUR in that hour. A full outage takes all of it. A partial outage, such as a missing payment method, takes the share of shoppers who wanted to pay that way and did not switch.

For comparison, the Shop Pro plan with an hourly checkout test costs 85 EUR a month (net). All plans are on the pricing page.

How I set this up in IThandy Monitor

Monitoring runs from outside your store, with no plugin or module to install. A scan detects the platform, page cache, Cloudflare and checkout type, and I switch checks on according to the plan.

• Start (12 EUR/month): availability every minute, origin check with cache bypassed, SSL, domain, response time, e-mail alerts.
• Shop (35 EUR/month): plus product page and add-to-cart every 5 minutes with product rotation, login page.
• Shop Pro (85 EUR/month): plus an hourly checkout test with shipping and payment methods, a method baseline and a monthly report with evidence.

The full checkout test runs for PrestaShop checkout monitoring, for WooCommerce as a guest and for Magento on the Luma theme. Shopify stores are checked up to the cart. The 14-day free trial covers the Start plan, so if you begin now you are covered before Black Week: try it on your store.

Sources

• Adobe: Cyber Monday hits record $14.25 billion (2025)
• Adobe: 2025 holiday shopping recap (PDF)
• BLIK: Record-breaking Black Weekend 2025
• Baymard Institute: Cart Abandonment Rate (updated 22 September 2025)
• DNSimple: SSL certificate validity changes 2026-2029 (CA/Browser Forum SC-081)
• UptimeRobot: pricing and free plan