Why Black Friday Is Different

Most WooCommerce stores experience their single highest traffic day of the year on Black Friday. For many, it accounts for 15-25% of annual revenue compressed into a 24-hour window.

The failure modes during this period are well-documented: servers that buckle under sudden concurrent load, checkouts that time out when payment gateways are overwhelmed, caching systems that serve stale stock levels, and support teams that can’t respond fast enough to incidents.

Every one of these failures is preventable with preparation. This checklist covers what to do in the weeks before, the days before, and on the day itself.

Four Weeks Before: Infrastructure

Confirm Your Hosting Plan Can Handle the Load

Start with an honest assessment of your expected traffic. Look at last year’s Black Friday data if you have it, or estimate based on your typical daily traffic multiplied by 5-10x for a conservative peak estimate.

Check your hosting plan’s PHP worker count. Each concurrent checkout occupies one PHP worker for the duration of the transaction (typically 2-8 seconds for payment processing). If you have 8 PHP workers and 20 customers hit checkout simultaneously, 12 of them are queuing.

Contact your hosting provider if you’re unsure whether your current plan is sized correctly. A managed host should be able to advise based on your usage patterns. On WP Pro Host, Scale and Elite plans include priority support and infrastructure pre-warming for anticipated peak periods.

Review Your Caching Configuration

WooCommerce caching is powerful but requires correct configuration to avoid checkout errors during peak load.

Verify that your caching plugin is correctly excluding:

  • Cart and checkout pages
  • Account and order pages
  • Any page with user-specific pricing (trade accounts, membership pricing)
  • REST API endpoints used by your dynamic blocks Test this by adding an item to your cart and confirming the cart count updates correctly across page navigation.

Enable Object Caching

If you’re not running Redis or Memcached object caching, set it up before Black Friday. Object caching dramatically reduces database load during concurrent requests — exactly the scenario you face during a sale.

Database query volume during a traffic spike without object caching can be 10-20× normal levels. With object caching, repeated queries for product data, pricing rules, and navigation are served from memory.

Tools like k6, Loader.io, or WP Load Tester can simulate concurrent user sessions against your staging site. Run a test simulating 2-3× your expected peak concurrent users and observe how the server responds.

Look for: PHP worker exhaustion (502 errors), slow database queries, and memory limit errors in your PHP error log.

Two Weeks Before: Application

Audit Your Active Plugins

Deactivate any plugin that isn’t actively contributing to the shopping experience during Black Friday. Every active plugin adds overhead to every request.

Common candidates for temporary deactivation:

  • Chatbot or live chat plugins (if you can’t staff them during the sale)
  • Complex analytics and heatmap scripts (collect data before and after, not during)
  • Social proof notification plugins (can generate high request volumes)
  • Review request plugins that trigger post-purchase emails in real time

Review and Optimise Images

Large, unoptimised product images are one of the most common sources of slow page loads. Run your product images through a tool like Squoosh or use a plugin like ShortPixel to ensure all images are properly compressed and served in WebP format.

Check that your CDN is correctly caching and serving product images — a cache miss on a high-traffic product page during peak load sends every image request to your origin server.

Update Everything — But Not on Black Friday

Apply all WordPress core, plugin, and theme updates at least one week before Black Friday. This gives time to identify any incompatibilities before they become problems on your highest-revenue day.

Do not apply updates on Black Friday or Cyber Monday. Even a routine update that introduces a minor conflict can be catastrophic during peak trading.

Test Your Checkout End-to-End

Run a complete test checkout using every payment method you offer. Include:

  • Standard card payment
  • PayPal/Apple Pay/Google Pay if offered
  • Coupon code application
  • Variable product selection
  • Guest and logged-in checkout paths Document the baseline checkout time (from clicking “Place Order” to seeing the confirmation page) so you have a reference point if performance degrades during the sale.

One Week Before: Monitoring

Set Up Enhanced Uptime Monitoring

If you don’t have uptime monitoring, set it up now. Uptime Robot (free) checks your site every 5 minutes. Better options for a critical trading period check every minute and monitor specific URLs — including your checkout page, not just your homepage.

Configure alerts to reach you via SMS, not just email. Email notifications can be delayed; SMS is immediate.

Create a Black Friday Incident Response Plan

Write down, in advance:

  • Who is responsible for monitoring on Black Friday
  • How to contact your hosting provider’s emergency support
  • The steps to take if your site goes down (who to call, what to check first)
  • A rollback plan if an issue can’t be resolved quickly (e.g., a static maintenance page with an email sign-up) Having this documented means you’re not making decisions under pressure when an incident actually happens.

Create a Staging Environment Snapshot

Take a snapshot of your staging environment with the exact configuration you plan to run on Black Friday. If an issue arises on the day, you can test fixes against staging rather than your live store.

The Day Before: Final Checks

Clear all caches and warm them by crawling your key product and category pages before traffic arrives. A warm cache serves content faster and reduces origin server load at the critical first minutes of your sale opening.

Check stock levels are accurate and that out-of-stock products are correctly set to prevent purchase.

Confirm your sale prices are active and displaying correctly in all combinations (variable products, bundled products, products with active coupons).

Test your payment gateway with a real transaction. Refund it immediately. Payment gateways occasionally have their own issues on high-volume trading days.

Brief your team on the monitoring plan and incident response process.

On the Day

Monitor your uptime dashboard and set it visible on a dedicated screen if possible.

Watch your checkout completion rate in WooCommerce Analytics. A drop below your baseline conversion rate is the earliest signal of a problem.

Don’t make changes unless there is a critical issue. The temptation to optimise something on Black Friday itself should be resisted. Every change is a risk.

Keep your hosting provider’s support contact accessible. If an incident occurs, every minute of response time costs revenue.

After Black Friday: Review

Document what happened: peak concurrent users, server resource usage, any incidents and their resolutions, checkout completion rate vs baseline.

Use this data to right-size your hosting plan for next year and identify any configuration changes that would reduce risk. The stores that consistently perform well on Black Friday are the ones that treat every year as a learning exercise.

Frequently Asked Questions

How should I prepare my WooCommerce store for Black Friday?

Preparation should start 4 weeks before: confirm PHP worker allocation matches expected peak concurrency, verify Redis object caching is active, check database performance under load, audit and remove unnecessary plugins. Two weeks before: optimise images, test checkout on staging under load, ensure cart and checkout pages are excluded from cache. One week before: configure monitoring alerts at 70% capacity, pre-warm the page cache by crawling key URLs. The day before: take a full database backup, verify all monitoring is active, and test a complete checkout flow.

How many PHP workers do I need for Black Friday traffic?

Calculate based on expected concurrent checkout sessions, not page views. A WooCommerce checkout occupies a PHP worker for 1-3 seconds due to payment gateway calls, tax calculations, and stock verification. If you expect 50 concurrent checkout attempts at peak, you need at least 50-75 PHP workers to handle them without queuing. Page views are largely served from cache and consume minimal workers — it is checkout concurrency that determines the true worker requirement during Black Friday.

Should I pre-warm my WooCommerce cache before Black Friday?

Yes. Pre-warming the cache before your Black Friday promotion goes live ensures the first wave of traffic hits cached pages rather than triggering PHP and database for every request simultaneously. Use a crawling tool to systematically request your most important URLs (homepage, category pages, top product pages) before opening the sale. On LiteSpeed with LSCWP, the built-in crawler can be triggered via WP-CLI: wp litespeed-crawler start. This is particularly important if you make price or content changes in the hours before the sale goes live.

How do I load test my WooCommerce checkout before Black Friday?

Use a load testing tool (k6, Loader.io, or Apache JMeter) to simulate concurrent checkout sessions. Test at checkout level specifically — not just homepage requests — since checkout involves real-time stock queries, payment gateway API calls, and database writes that are not served from cache. Test at 150-200% of expected peak traffic to confirm headroom exists. Run the test against a staging environment that mirrors production as closely as possible, ideally within the same hosting infrastructure. Identify and address bottlenecks before the live event.

What should I do if my WooCommerce store slows down during Black Friday?

Immediate actions during a slowdown: check your hosting monitoring dashboard for PHP worker saturation and database connection pool usage — these are the most common causes. If workers are saturated, contact your host to request temporary resource scaling. If the database is the bottleneck, check for lock contention from concurrent checkout writes. Enable query caching if not already active. As a temporary measure, reduce the complexity of checkout by temporarily disabling non-essential plugins that add processing overhead. After the event, conduct a proper performance audit to address root causes before the next peak period.

· WooCommerce Hosting · Infrastructure Pre-Warming on Scale & Elite Plans