A WooCommerce store slows down during a sale because hundreds of shoppers hit the cart and checkout at the same moment, and those pages can’t be served from cache. Each one makes your server do real work, while order emails, stock updates, bots and extra sale plugins compete for the same resources. The fix is preparation: check capacity, trim the site, test checkout under load and freeze changes before the sale starts.
Key takeaways
- Cart, checkout and account pages are built fresh for every shopper, so sales traffic lands on your server, not your cache.
- Most slowdowns come from a sudden spike, background jobs and sale add-ons, not from total visitor numbers.
- Start three to four weeks out: capacity, clean-up and test orders first, then a change freeze 48 hours before.
- Card testers and scraper bots love sale days. Block them before they eat the capacity your shoppers need.
Why does a WooCommerce store slow down during a sale?
Sales concentrate demand. Australians spent $1.5 billion online over Black Friday and Cyber Monday 2025, with 3.1 million households shopping that weekend (Australia Post). In 2026, Black Friday falls on 27 November and Cyber Monday on 30 November. Five things usually cause the slowdown.
1. Shoppers move to pages that can’t be cached
On a normal day, most visitors browse product and category pages, which your cache serves almost instantly. During a sale, far more of them add to cart and check out. Those pages are unique to each shopper, so every view runs PHP and queries the database. Our guide to WooCommerce hosting in Australia explains why that split matters.
2. Everyone arrives in the same few minutes
A sale email or social post sends a wave of people at once. Your server can only build a certain number of uncached pages at the same time, roughly tied to its CPU cores and PHP workers. Past that point, requests queue, pages hang and some shoppers see errors.
3. Background jobs pile up
Every order triggers emails, stock updates, payment webhooks and often syncs to accounting or shipping software. WooCommerce also runs scheduled tasks for things like sale prices. If those rely on WP-Cron, they fire on page visits and add load at the busiest moment (WordPress Developer Resources).
4. Bots and card testers join in
Scrapers crawl your discounted catalogue, and card testers use your checkout to check stolen card numbers. Stripe warns that card testing “can overburden your infrastructure and disrupt legitimate activity” (Stripe). It also hurts your decline rate with banks.
5. New sale extras weigh the pages down
Countdown timers, pop-ups, upsell plugins and extra tracking scripts often go live the week of the sale, untested under load. Some make a background request on every page. WooCommerce stopped loading its cart fragments script on every page in version 7.8 for this reason, saying it could “severely impact the load on the server” for busy stores (WooCommerce Developer Blog).
The pre-sale checklist
Work through this in order. Most of it is quick, but the first stage needs time to fix whatever it turns up.
Three to four weeks before
- Check your capacity. Ask your host how many CPU cores and how much memory your store gets, and whether you can upgrade temporarily for the sale.
- Run a supported PHP version. WooCommerce asks for PHP 8.3 or newer.
- Remove what you don’t use. Deactivate and delete idle plugins, and cut tracking scripts nobody reads.
- Consider HPOS. High-Performance Order Storage keeps orders in dedicated tables built for store queries. It’s the default for new stores since WooCommerce 8.2, but older stores must switch it on (WooCommerce). Check plugin compatibility and test first.
- Move scheduled tasks to a real server cron so they run on time instead of on shopper visits.
- Prove your backups. Restore one to a staging copy. A backup you’ve never restored is a hope, not a plan.
One to two weeks before
- Load sale prices and coupons early, with scheduled start and end dates, and check them on staging.
- Load test a staging copy. Your host or developer can simulate dozens of shoppers adding to cart and checking out at once.
- Place real test orders with every payment method and shipping option. Our article on WooCommerce checkout speed covers the payment side in more detail.
- Turn on bot and card-testing protection. Add a CAPTCHA or rate limit to checkout, and use your payment gateway’s fraud tools. If you take cards, our guide to PCI compliance for small business explains what you’re responsible for.
48 hours before
- Freeze changes. No plugin updates, theme edits or new add-ons until the sale ends, unless it’s an urgent security fix.
- Take a fresh, off-site backup and note how to restore it.
- Warm the cache by visiting key product and category pages after any price change.
- Tell your host the sale times, and save their emergency contact in your phone.
On sale day
- Stagger email sends to different segments over an hour or two, rather than one blast.
- Watch the signals: orders coming in, failed payments, page load time and uptime alerts.
- Keep one person free to check the store as a customer would, every hour.
What if the store slows down mid-sale?
- Check it’s not just you. Load the site on mobile data and ask your host whether the server is under strain.
- Look for bots. A surge of failed payments or one country hammering the site points to an attack, not shoppers.
- Pause the extras. Turn off pop-ups, live chat widgets or an upsell plugin before you touch anything core.
- Ask for more resources. On plans with clear allocations, a temporary upgrade is often the fastest fix.
- Hold the next email until the site recovers, so you don’t send a second wave into a queue.
Speed matters here. Deloitte found a 0.1-second faster mobile site lifted retail conversions by 8.4% (web.dev). On a sale day, those seconds are worth the most.
Is it the hosting or the store?
Usually both. Hosting sets the ceiling: how many shoppers can check out at once. The store decides how much of that ceiling each shopper uses. Good WooCommerce hosting gives you clear CPU and memory, Australian servers and room to grow. To compare tiers and support hours, see our hosting plans.
The store side is ongoing work: plugin updates, clean-ups and checkout tests after every change. Our WooCommerce maintenance covers that, so your next sale starts from a tidy, tested store.
Frequently asked questions
Why is my WooCommerce checkout slow but the rest of the site is fast?
Product and category pages come from cache, but cart and checkout are built fresh for every shopper. They run PHP, query the database and often call payment, shipping and tax services. Heavy plugins on those pages, an old PHP version or too few CPU cores all show up there first.
How much traffic can my WooCommerce store handle?
It depends on how many shoppers check out at the same time, not on daily visitors. A load test on a staging copy is the only reliable answer. Ask your host or developer to simulate a realistic sale-day spike and watch where response times start to climb.
Should I update plugins right before Black Friday?
Update two to three weeks before, test, then freeze changes 48 hours out. The exception is an urgent security fix for a plugin under active attack. Apply it, but test checkout straight away and keep a fresh backup ready.
Can a CDN stop my store slowing down during a sale?
A CDN helps with images, scripts and cached pages, which frees up your server. It can’t cache the cart and checkout, so it won’t fix a server that runs out of capacity when shoppers pay. You still need enough CPU, memory and a lean store.
When should I start preparing for a big sale?
Three to four weeks ahead is comfortable. That gives you time to check capacity, upgrade PHP or hosting if needed, clean up plugins and run a load test. For Black Friday on 27 November 2026, start by early November.
Sources
- Aussies set a new cyber weekend record, Australia Post, 9 December 2025
- Hooking WP-Cron into the system task scheduler, WordPress Developer Resources
- Protect yourself from card testing, Stripe Docs
- Best practices for the use of the cart fragments API, WooCommerce Developer Blog, 16 June 2023
- High-Performance Order Storage, WooCommerce Developer Docs
- Milliseconds make millions, web.dev (Deloitte research, 2020)