WooCommerce Speed Optimisation: How to Fix a Slow Store

Why is my WooCommerce store slow?

WooCommerce runs on WordPress, so every page is built by PHP and the database unless something serves a stored copy. A slow store usually comes down to a few causes, often stacked on top of each other:

• No page caching, or caching switched off because it once broke the cart.
• Heavy product images, uploaded straight from a camera or phone and shown at full size.
• Too many plugins, each adding its own CSS, JavaScript and database queries to every page.
• A heavy theme with sliders, page-builder layers and features the store never uses.
• A cluttered database full of revisions, expired transients and years of order data in the general posts tables.
• Slow hosting, where the server takes a long time to send the first byte.

The point of measuring first is to find out which of these you actually have, so you fix the cause rather than install another plugin.

Measure before you change anything

WooCommerce's guide recommends testing regularly with tools such as Google PageSpeed Insights, GTmetrix or WebPageTest. Test at least four pages while logged out: the homepage, a category page, a product page and the cart. A store can have a fast homepage and a slow category page, and the category page is where buyers spend their time.

Run each test a few times and write the results down, so you can compare before and after on the same settings. If you're not sure which tool to trust or why their scores differ, our guide to website speed test tools compared explains what PageSpeed Insights, Lighthouse and GTmetrix each measure and the order we run them in.

Set up caching without breaking the cart

Caching is step one in WooCommerce's guide because it serves stored copies of pages instead of building each one from scratch. You can cache at the server, with tools such as Varnish, NGINX FastCGI Cache or Redis, often switched on through your host, or with a WordPress caching plugin such as WP Rocket, W3 Total Cache or WP Super Cache.

The WooCommerce part is what most stores get wrong. WooCommerce's caching configuration guide says three pages must stay dynamic because they show information specific to each customer:

• Cart
• My Account
• Checkout

It also lists the cookies WooCommerce uses to track carts, such as woocommerce_cart_hash, woocommerce_items_in_cart and wp_woocommerce_session_, which you can exclude from caching, and suggests excluding _wc_session_ if your system offers database caching. A few plugin-specific notes from the same page:

• WP Super Cache: WooCommerce tells it not to cache the cart, checkout and account pages by default.
• WP Rocket: make sure the cart, checkout and account pages are excluded, and WooCommerce recommends avoiding JavaScript minification.
• Host-level caching: if customers get stuck in a password reset loop, the My Account page is being cached and your host needs to exclude it.

After switching caching on, add a product to the cart, log in, check out with a test order and reset a password. If any of those misbehave, fix the exclusions before you move on.

Shrink, size and lazy-load product images

Images are step two in WooCommerce's guide, and on fashion and catalogue stores they are usually the heaviest thing on the page. The guide gives four rules:

1. Pick the right format: JPEG for photographs, PNG for graphics that need transparency.
2. Compress before uploading, with a tool such as TinyPNG or ShortPixel.
3. Lazy-load images so the ones further down the page load only when needed.
4. Serve responsive images, so phones get a smaller file than a large desktop screen.

This matters most where the photos sell the product. When we built the Kalamohini WooCommerce store for hand-crafted tissue-silk and mirror-work sets, each product page needed multiple high-resolution images, so optimised image loading was part of the build to keep mobile browsing fast. Rich photography and a quick store are not a trade-off if the images are sized and loaded properly.

Cut plugin and theme weight

Step six in WooCommerce's guide is choosing a lightweight theme designed for WooCommerce and checking how much each plugin slows the store. It names Query Monitor and WP Hive as tools for analysing a plugin's performance impact, so you can remove or replace the ones that slow the store down.

In practice, list every active plugin and ask what it does for a buyer or for your team. Sliders, duplicate analytics scripts, unused page-builder add-ons and abandoned plugins are the usual candidates. Remove one at a time on a staging copy and re-test, so you know which change helped.

The guide also suggests minifying HTML, CSS and JavaScript, inlining critical CSS and deferring non-critical JavaScript, with plugins such as Autoptimize, WP Rocket or W3 Total Cache. Treat JavaScript changes with care on a shop: deferring or minifying the wrong script can break the cart, variation pickers or payment buttons, so test checkout after every change.

Clean the database and move orders to HPOS

WooCommerce's guide recommends regular database clean-ups, removing spam comments, post revisions and expired transients, with a plugin such as WP-Optimize, WP-Sweep or Advanced Database Cleaner. Take a full backup before any clean-up.

The bigger change for stores with a long order history is High-Performance Order Storage (HPOS). WooCommerce explains that orders were traditionally stored as WordPress posts and post meta, which comes with performance issues. HPOS stores orders in dedicated tables with their own indexes, which means fewer read and write operations and fewer busy tables. Since WooCommerce 8.2, released in October 2023, HPOS has been enabled by default for new installations, so older stores are the ones most likely to still be on the posts tables.

You can check and switch under WooCommerce, Settings, Advanced, Features. If a plugin isn't compatible, the HPOS option is disabled and WooCommerce lets you view the list of incompatible plugins. Do this on a staging copy first, update or replace those plugins, then switch the live store.

Serve files from a CDN and turn on compression

A content delivery network serves your images, CSS and JavaScript from servers spread around the world, which helps when your buyers are far from your host. WooCommerce's guide names Cloudflare, Fastly and Amazon CloudFront as examples; check each provider's own site for plan details.

The guide also recommends GZIP compression for HTML, CSS and JavaScript, either through a plugin such as WP Rocket, W3 Total Cache or WP Super Cache, or directly in your server settings (the .htaccess file on Apache, nginx.conf on NGINX). Many hosts already have it switched on, so check before adding another plugin for it.

The order we work through on a slow WooCommerce store

The same thinking applies on other platforms; our guide to Shopify speed optimisation covers the equivalent fixes for Shopify's apps and themes. And because speed slips as plugins update and catalogues grow, monthly checks are part of our website maintenance service.

Frequently asked questions

Which WooCommerce pages should never be cached?

WooCommerce says the cart, checkout and My Account pages must stay dynamic, because they show information specific to the current customer. Some caching plugins exclude them automatically; WP Super Cache does by default. Always check, then test a full order after switching caching on.

Will a caching plugin alone fix a slow WooCommerce store?

Usually not. Caching helps pages that can be stored, but heavy images, slow plugins and a cluttered database still slow the store, and cart and checkout pages are never cached. Treat caching as the first step, not the whole fix.

Is it safe to switch an existing store to HPOS?

It is a supported WooCommerce feature, but test it on a staging copy first. If a plugin isn't compatible, WooCommerce disables the HPOS option and shows you the incompatible plugins, so update or replace those before you switch. Keep a full backup whatever you do.

Do I need to rebuild my WooCommerce store to make it fast?

Rarely. Most of the gains come from caching set up correctly, lighter images and fewer plugins, all of which work on the store you already have. A rebuild makes sense only when the theme itself is the bottleneck or the store has outgrown its setup.