WooCommerce stores: why they slow down and what fixes it

Why WooCommerce stores slow down

Every page in WooCommerce is put together on the server each time someone opens it, from a database that grows with every order. A category with fifty products means fifty images and filters that reload the page.

Then come the plugins: payment gateway, delivery, reviews, discounts, languages. Each makes sense on its own, but each adds code that loads, often on every page.

Measure the right pages

The front page is rarely the problem. Measure a category page and a product page in PageSpeed Insights, on mobile. If the time until the server first answers is long, the problem is on the server and in the database. If it is short but the page still takes long to appear, the problem is in images and code.

Fixes that work on the store you have

Scale images down to the size they display at. Remove plugins nobody uses any more. Use caching for product and category pages, but never for the cart and checkout. Move the store to hosting made for WooCommerce. These are the cheapest fixes, and they often deliver a lot.

When fixes are not enough: a new front end

If the store is still slow after that, it is the structure itself. Then you can keep WooCommerce for products, stock, orders and payments, but build the front end visitors see separately. It reads the products from WooCommerce and shows them at once, and payment still completes in the same system.

What does not change

Staff keep working in the same WooCommerce dashboard. The payment gateway, deliveries and accounting connections stay. Orders arrive as before. The only thing the customer notices is that the store has become fast.