Skip to content
ArticleOct 2026·10 min read

Why is WooCommerce so slow, and what should you fix first?

A slow WooCommerce store usually comes down to a few causes. Here’s what to check first, from server response to past-due actions, and how to fix each one.

SmartWP teamThe people who build our plugins
Flat illustration of a cart dragging heavy blocks under a dial reading slow

WooCommerce is usually slow for one of a few reasons: a server that takes too long to build pages, cart and checkout pages that can’t be cached, plugins that run on every page, too much data loading with every request, a backed-up background queue or oversized images. Start with the server, because a slow server slows every page.

Most WooCommerce speed optimization advice starts with a caching plugin. A cache helps, but the pages where shoppers pay can’t use it, so measure before you add anything. Each check below begins with the tools WordPress and WooCommerce already include.

Server response

Aim for 0.8 seconds or less to the first byte, and test the cart as well as a product page.

Cart and checkout

Keep them out of the page cache, and stop cart fragments running on pages without a mini-cart.

Plugins

Measure them with Query Monitor on staging, then fix or replace the heaviest.

Autoloaded options

Site Health warns when they pass 800 KB. Start with the largest.

Scheduled actions

A few past-due actions are normal. Several more than a day old are a warning sign.

Images

Resize before you upload, and use WebP or AVIF.

Slow admin

Move orders to High-performance order storage (HPOS).

Why is WooCommerce so slow compared with a normal WordPress site?

A blog post looks the same to every visitor, so a page cache can save one copy and hand it out thousands of times. A store can’t do that everywhere. The cart, checkout and My Account pages show each shopper their own items and details, so WooCommerce builds them on every visit, running PHP and asking the database for prices, stock, tax and shipping each time.

That’s why a store can feel quick on the home page and slow at checkout. It’s also why the server and the plugins matter more to a store than to a blog, since nothing is cached on the pages where people pay.

A server stack with a clock and a long line to a browser window
If the server answers slowly, everything after it waits too.

Is your hosting the problem? Check the server response time

Time to first byte (TTFB) is how long your server takes to start sending a page. Google’s web.dev guidance calls 0.8 seconds or less good. Measure two pages: a product page, which your cache can serve, and the cart, which it never does. The cart shows how fast your server builds a page on its own.

Terminal
# Time to first byte for a cached page and an uncached one
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}sn" https://example.com/product/sample-product/
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}sn" https://example.com/cart/

Run each line a few times, because the first request can be slow while caches warm up. WordPress checks some of this for you too: under Tools → Site Health, the page cache test flags a slow server response, and another test tells you whether a persistent object cache would help. The Server section of its Info tab shows your PHP version.

If the product page is fast but the cart is well over that mark, start with the server. Ask your host for the newest PHP version your plugins support, and for a persistent object cache such as Redis or Memcached, which keeps database results in memory between requests. If your host offers neither, look at hosting built for WooCommerce. If the cart stays slow on hosting that should cope with your traffic, plugins are the next place to look.

Why is the WooCommerce cart so slow?

Your caching plugin should leave the cart, checkout and My Account pages out of its cache. Many caching plugins that support WooCommerce do this for you, but check the exclusions anyway: a cached cart can show one shopper’s items to another. Some setups also skip the cache for anyone with something in their cart, so from the first Add to cart onwards every page they open is built fresh.

Then look for cart fragments. It’s an older WooCommerce script that keeps a mini-cart up to date by asking your server for the latest cart, a request no page cache can answer. Since WooCommerce 7.8, it only loads with the classic Cart widget, or when a theme or plugin asks for it, so some stores still run it on every page.

To check, open a product page in a private window with your browser’s developer tools open, go to the Network tab and filter by wc-ajax. A get_refreshed_fragments request means cart fragments are running on that page. If you don’t show a mini-cart, ask the developer of your theme, or of the plugin that loads the script, how to turn it off. If you do, WooCommerce recommends the Mini-Cart block, which doesn’t use cart fragments.

Checkout also gets slower with every script that loads on it, from payment buttons to chat widgets. Our guide to speeding up the WooCommerce checkout has more on what slows it down.

Free ebook, 42 pagesThe Ultimate Checklist to WooCommerce OptimizationGet the checklist
A power strip full of plugs with one standing out
Switch plugins off one at a time on staging to find the heavy one.

Which plugin is slowing down WooCommerce?

Each plugin can add database queries and files to pages that don’t need them, so what each one does matters more than how many you have. To find the heavy ones, install Query Monitor on a staging copy of your store and open a product page, the cart, checkout and the admin screen that feels slow. It groups database queries by the plugin or theme responsible, with how long they took.

When one plugin stands out, confirm it first: deactivate it on staging and measure the same pages again. Then look in its settings for a lighter option or ask its developer about it, and replace it if neither helps. Change one thing at a time, or you won’t know which change helped.

It’s fair to ask any plugin maker what their plugin costs your store, and we publish our answer. With every power-up switched on, Admin Powerups adds 0 database queries to the storefront, cart and checkout, and CartPresets adds none to the storefront either. The test notes for Admin Powerups and CartPresets list every measurement.

“Autoloaded options could affect performance”: what it means

WordPress loads every autoloaded option in the wp_options table on every request, admin pages included. Plugins keep their settings there, and some leave them behind when you delete the plugin. Since WordPress 6.6, Tools → Site Health shows “Autoloaded options could affect performance” once they add up to more than 800 KB.

If you or your developer can use WP-CLI, these two commands show the total and the largest options:

WP-CLI
# Total size of autoloaded options, in bytes (what Site Health measures)
wp db query "SELECT SUM(LENGTH(option_value)) AS bytes FROM $(wp db prefix)options WHERE autoload IN ('yes','on','auto-on','auto');"

# The 20 largest autoloaded options
wp db query "SELECT option_name, LENGTH(option_value) AS bytes FROM $(wp db prefix)options WHERE autoload IN ('yes','on','auto-on','auto') ORDER BY bytes DESC LIMIT 20;"

Start with the biggest. An option that belongs to a plugin you removed can usually go. One that belongs to an active plugin can stop autoloading if the plugin only needs it on a few screens, and WordPress then loads it when the plugin asks for it. If the plugin reads it on every page, that adds a query to every page instead. Take a database backup before you change either.

If you’d rather not touch SQL, the Autoloaded options tool in Admin Powerups lists the 100 largest with a probable owner for each. You can stop autoloading one and undo it later, and it only deletes options left by inactive or removed plugins and themes, after you type a confirmation.

A queue of task cards piling up under a clock
A long queue of background tasks can slow the admin and delay emails.

Is a backed-up background queue slowing your store?

Action Scheduler is the job queue that comes with WooCommerce. It handles work that shouldn’t keep a shopper waiting, such as webhook deliveries and subscription renewals, and WP-Cron starts it at most once a minute. When it falls behind, jobs pile up in the database and admins see a notice like “Action Scheduler: 12 past-due actions found; something may be wrong.”

Go to Tools → Scheduled Actions (also under WooCommerce → Status) and open the Past-due and Failed lists. The Action Scheduler FAQ says some past-due actions are normal, while several more than a day old may mean something is wrong. The hook name on each row usually tells you which plugin owns the job.

A common cause is WP-Cron not running. It only fires when someone visits, and it needs your server to be able to call itself. Check the loopback request result in Tools → Site Health. If it fails, or your store is quiet for hours at a time, ask your host to run WP-Cron from a real server cron every minute. A developer can also clear a backlog by hand:

WP-CLI
# Run every WP-Cron event that is due now
wp cron event run --due-now

# Work through the Action Scheduler queue
wp action-scheduler run

In recent WooCommerce versions, the same queue deletes expired shopper sessions twice a day, so when it stalls, the woocommerce_sessions table keeps growing. WooCommerce → Status → Tools can clear expired transients, but leave Clear customer sessions alone on a live store: it deletes every session, including carts that shoppers are still filling.

Admin Powerups has a tool for each of these. Its Scheduled action monitor counts overdue, failed and stuck actions and shows how big the actions tables have grown, with retry and purge buttons. Database clean-up scans for expired sessions and transients and shows a count before it deletes anything. Our guide to past-due scheduled actions walks through the fixes step by step.

Are your product images too big?

Product photos are often the heaviest thing on a page. Run a product page and a category page through PageSpeed Insights on mobile and look at Largest Contentful Paint. On a product page, that’s usually the main photo.

Resize photos to the largest size your theme shows before you upload them, and save them as WebP. AVIF files are often smaller still, and WordPress accepts them from version 6.5 when your server supports the format. If an optimization plugin lazy-loads every image, exclude the main product photo, which should load first. A CDN helps most when your shoppers are far from your server.

Why is the WooCommerce admin so slow?

A slow admin usually has the same causes as a slow storefront, plus one more: how your orders are stored. High-performance order storage (HPOS) keeps orders in tables of their own, built for finding and filtering orders. It has been the default for new stores since WooCommerce 8.2, but older stores may still keep orders in the WordPress posts tables, next to every page and product.

Go to WooCommerce → Settings → Advanced → Features and look at Order data storage. If it says WordPress posts storage, plan the switch. Plugins that don’t support HPOS block it, and the View and manage link lists them, so update or replace those first. Then tick compatibility mode, wait for WooCommerce to copy your orders into the new tables, and switch to HPOS. Compatibility mode keeps both copies in step while you check that everything still works. Once you’re sure, switch it off, because keeping two copies in step is extra work on every order. WooCommerce’s HPOS guide has the details.

After that, open the slow admin screen with Query Monitor running. Plugins that add heavy columns or dashboard widgets to busy screens like Orders show up there. Autoloaded options and the background queue affect the admin as well, so the checks above help here too. Keep WooCommerce itself up to date, since recent releases have made its admin screens lighter, and follow our notes on how to update WooCommerce safely.

How to speed up WooCommerce and keep it fast

Work through these checks in order, and measure the same pages after every change. A fix that helps one page can slow another, and the numbers tell you which. Once the store is fast, open Site Health and the Past-due list once a month, so a stalled queue or a new heavy option doesn’t go unnoticed for long.

If you’d like those checks in one place, Admin Powerups adds the Scheduled action monitor, Autoloaded options and Database clean-up under WooCommerce → Powerups. Each tool stays off until you switch it on. Our free WooCommerce optimization checklist (PDF) goes further into scaling and stability, with a to-do list at the end of each chapter.

Keep reading