A slow store loses sales, especially on mobile. WooCommerce isn’t slow by nature, but it asks more of the server than a business website does, because the cart, stock and orders are dynamic. Here are the 8 changes that make a difference.

Why is WooCommerce slow?

Many pages can’t be cached (cart, checkout, customer account), and every store plugin adds database queries. Entry-level hosting hits its limits quickly.

The 8 optimisations that matter

  1. Suitable hosting, with recent PHP and an object cache (Redis or Memcached).
  2. Page caching for the catalogue, excluding the cart, checkout and account.
  3. HPOS: high-performance order storage, turned on after checking your plugins are compatible.
  4. A clean database: expired sessions, transients and overdue scheduled tasks.
  5. Product images at the right size, in WebP or AVIF.
  6. Fewer plugins: every filter and payment module adds weight.
  7. Scripts loaded only where they’re needed (no cart script on a blog post).
  8. Efficient search and filters on large catalogues.

How do you speed up the cart page?

It can’t be cached, so everything depends on server speed and the number of queries. An object cache, fewer plugins active on the cart and efficient shipping calculations make the difference.

Which hosting for WooCommerce?

Hosting with guaranteed resources, a recent PHP version and an object cache. Entry-level shared hosting suits a small store, and rarely anything bigger.

How do you optimise the database?

Delete expired sessions and stale transients, check the scheduled task queue (Action Scheduler) and limit revisions. Always take a backup first.

Should you use caching on WooCommerce?

Yes for catalogue, product and content pages, which are the same for every visitor. No for the cart, checkout and customer account, which have to be generated on each visit. Good caching solutions know these exclusions; check them after every configuration change.

WooCommerce scripts across the whole site

Depending on the theme and plugins, cart scripts can load on every page, blog posts included. Limiting them to the store pages lightens the rest of the site and makes it more responsive.

Measure before optimising

  1. Measure a product page, the cart and the checkout, as well as the home page.
  2. Find slow queries with a tool like Query Monitor on a staging site.
  3. Check the scheduled task queue under WooCommerce › Status › Scheduled Actions.

What now?

What you can do today:

  • Measure a product page and your cart page with PageSpeed Insights.
  • Count your active WooCommerce plugins and what each one really does.
  • Check whether your host offers an object cache.

Dig deeper: WooCommerce Development and Optimisation