WooCommerce Speed Checklist Before Cyber Monday Traffic

Cyber Monday 2026 falls on November 30, which leaves about three weeks to get a WooCommerce store ready for the heaviest traffic of the season. Google’s “good” Core Web Vitals targets are an LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, measured at the 75th percentile of real visits. WooCommerce stores often miss them because of uncached cart and checkout pages, a database that grows with every order, and plugins that load code on every page.

This WooCommerce speed checklist covers what to fix, in what order, and what to leave alone once the freeze begins.

What should a WooCommerce speed checklist cover?#

A WooCommerce speed checklist should cover seven areas, in this order: baseline measurement, hosting capacity, object caching, page cache rules, database health, plugin audit, and checkout performance. Fixing them in sequence matters, because each layer affects how much load the next one carries.

How do you set a baseline before changing anything?#

Measure real-user performance on your homepage, a category page, a product page, the cart, and checkout, on mobile first. Without a baseline you cannot tell whether a change helped.

1. Check the Core Web Vitals report in Google Search Console for URL groups that fail.
2. Run PageSpeed Insights on one URL from each template and note the field data (real users) separately from lab data.
3. Record LCP, INP, and CLS, plus server response time.
4. Place a test order and time each step manually.

Search Savvy’s Core Web Vitals developer checklist goes deeper on diagnosing each metric once you know which pages fail.

What hosting do you need for WooCommerce traffic spikes?#

You need hosting that can serve many simultaneous uncached requests, because carts, checkout, and logged-in accounts cannot be fully cached. Shared plans with limited PHP workers are the most common failure point on sale days.

Ask your host these questions in writing:

• How many PHP workers are allocated, and what happens when they are exhausted?
• Is a persistent object cache such as Redis or Memcached available?
• Which PHP version is running, and is it currently supported?
• Can resources be scaled temporarily for November 27 to December 1?
• Is a CDN included, and does it respect WooCommerce cache exclusions?

If the answers are vague, plan a migration after the sale, not during it. Changing hosts in the final two weeks adds more risk than it removes.

How do you set up object caching for WooCommerce?#

Install a persistent object cache, usually Redis, so WordPress and WooCommerce stop re-querying the database for data they just fetched. WordPress’s object cache only lasts for a single request unless a persistent backend is added.

1. Confirm with your host that Redis or Memcached is running.
2. Install a compatible object cache plugin and enable the drop-in.
3. Confirm the connection in the plugin’s status screen.
4. Test on staging first: cart, checkout, coupon, and login flows.
5. Watch for stale data after product or stock updates.

How do you know object caching is working?#

Check the plugin’s hit-rate statistics and compare server response time on uncached pages before and after. If hit rates stay low or response times do not move, the cache may not be connected or may be flushing constantly.

How should you configure page caching and cart fragments?#

Cache public pages aggressively and exclude anything customer-specific. Never cache the cart, checkout, or my-account pages, and bypass the cache for visitors with WooCommerce cart cookies (such as woocommerce_items_in_cart).

Cart fragments need attention too. WooCommerce’s wc-cart-fragments script runs an AJAX request (wc-ajax=get_refreshed_fragments) to update the mini-cart, and on many themes it fires on pages that never show a cart. Options:

• Dequeue the script on pages other than shop, cart, and checkout, if your theme does not need it
• Use a caching plugin’s built-in WooCommerce handling
• Test the mini-cart after any change, since disabling it completely can break the experience

Claims about exactly how much cart fragments slow a store vary widely, so measure the effect on your own store.

How do you optimize the WooCommerce database?#

Focus on four areas: order storage, autoloaded options, expired data, and scheduled-action logs. Always back up first and run heavy cleanup on staging or off-peak.

Is HPOS worth enabling before Cyber Monday?#

High-Performance Order Storage (HPOS) moves orders out of the generic posts tables into dedicated ones. WooCommerce’s documentation says it has been enabled by default for new installations since WooCommerce 8.2 in October 2023. Existing stores can switch under WooCommerce > Settings > Advanced > Features, after synchronizing the tables in compatibility mode.

If you are already on HPOS, confirm it is active. If not, test on staging for plugin compatibility now. WooCommerce’s guide for large stores recommends staged testing and monitoring before disabling synchronization, so do not attempt the migration in sale week.

Other database tasks:

• Autoloaded options: find oversized wp_options entries from deleted plugins, since they load on every request.
• Transients and sessions: clear expired transients and old session data.
• Action Scheduler: review WooCommerce > Status > Scheduled Actions for large piles of completed or failed actions.
• Revisions and spam: remove old revisions and spam comments.

How do you run a plugin bloat audit?#

List every active plugin, identify what each one loads on the front end, and remove or replace anything that costs more than it earns. Start with the Query Monitor plugin on staging to find slow queries and scripts by plugin.

1. Export the plugin list and mark each as essential, useful, or unknown.
2. Deactivate “unknown” plugins on staging and test key flows.
3. Look for overlap: multiple SEO, popup, analytics, or slider plugins.
4. Check which scripts load on the homepage, then on checkout.
5. Replace heavy plugins with lighter ones or small code snippets where practical.

Search Savvy’s WordPress speed optimization checklist covers general WordPress tuning that applies here too.

How do you speed up the WooCommerce checkout page?#

Remove everything from checkout that is not needed to take payment. Checkout cannot be page-cached, so every script and request counts, and delays here lose orders directly.

• Load chat widgets, heatmaps, and review popups only on non-checkout pages
• Keep fields to the minimum your shipping and tax rules require
• Reserve space for payment elements and notices to avoid layout shifts
• Test each payment method on mobile
• Check responsiveness when applying coupons and selecting shipping

Slow interactions after tapping a button usually point to heavy JavaScript. Search Savvy’s INP optimization checklist explains how to find and fix them. For product imagery, see image optimization for Core Web Vitals.

What is a realistic timeline before Cyber Monday?#

A load test simulating realistic traffic should include browsing, adding to cart, and checkout, not just the homepage. Fix what breaks, then freeze.

What mistakes should you avoid?#

• Caching cart or checkout pages, which creates wrong-cart bugs
• Installing several caching plugins, which conflict
• Changing things during sale week, after the freeze
• Optimizing only for a lab score, while real users still fail Core Web Vitals
• Skipping backups before database work
• Ignoring mobile, where most checkout friction appears

The bottom line#

For most stores, the biggest gains come from a persistent object cache, correct cache exclusions, a lean plugin list, and a light checkout, all validated by a load test before a firm freeze. Do the measurements first, change one thing at a time, and leave sale week for monitoring. If you want an outside review, Search Savvy’s website speed optimization services cover performance audits for stores like yours, and the Black Friday SEO checklist for Indian D2C brands covers the search side of the same season.

FAQ#

How fast should a WooCommerce store load?#

Aim for Google’s good thresholds: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less at the 75th percentile of real visits. Product and checkout pages on mobile deserve the closest attention.

Do I need Redis for WooCommerce?#

Not strictly, but a persistent object cache helps stores with many products or orders because it reduces repeated database queries. Check with your host whether Redis or Memcached is available.

Should I disable cart fragments completely?#

Usually no. Disabling them everywhere can break the mini-cart. Limit the script to pages that need it, then test adding, removing, and updating items.

Can I enable HPOS right before Cyber Monday?#

It is risky. WooCommerce recommends staged testing and monitoring, and plugin compatibility must be checked. If you are not already on HPOS, test now on staging and migrate after the sale.

How do I load test my WooCommerce store?#

Use a load testing tool to simulate visitors browsing, adding to cart, and checking out on a staging copy of the production setup. Increase traffic gradually and note where response times or errors rise.

How do I find slow plugins?#

Use Query Monitor on staging to see which plugins produce slow queries, scripts, and hooks. Then deactivate suspects one at a time and retest key pages.