A brochure site is easy to make fast. A shop is not, because the pages that matter most cannot be cached — the basket, the checkout and the account area must stay personal. So when owners ask us to speed up WooCommerce, the honest answer is that caching alone will not do it. Here is the order of work that actually helps, without removing the features that sell.
Why WooCommerce feels slower than it should
Four things usually collide. First, dynamic pages run PHP and hit the database on every request. Second, cart fragment requests fire on pages that have no cart. Third, product images arrive far larger than needed. Fourth, plugin sprawl — a shop tends to accumulate twenty of them, each adding queries. Consequently the site feels heavy for logged-in customers even when the homepage scores well.
Start with the server, not the plugins
Because so much of a shop is dynamic, raw server capability matters more than on a blog. Therefore insist on three things: a current PHP version, object caching with Redis, and enough memory that PHP workers do not queue. In addition, keep the database close to the web server. Our guide to hosting for Greek visitors covers the geography side, and if your plan is a cheap shared box, that is your bottleneck rather than your theme.
Then the changes that speed up WooCommerce itself
- Enable high-performance order storage. WooCommerce can keep orders in dedicated tables instead of the post tables, which speeds up admin and order queries noticeably on busy shops.
- Cache everything cacheable — home, category and product pages — while excluding cart, checkout and my-account. Our caching comparison lists the safe exclusions.
- Disable cart fragments where there is no cart. That single change removes an uncached request from every page view.
- Fix the images. Product photography is usually the biggest payload; see image optimisation in 2026.
- Tame variable products. A product with 200 variations generates enormous data on load, so split it or load variations on demand.
- Clean the database. Expired transients, old sessions and abandoned carts accumulate quietly and slow every query.
Keep the features, cut the freeloaders
Speed work goes wrong when someone removes a feature that earns money. So audit by value instead. Look at each plugin and ask what it contributes: the review widget nobody reads, the second slider, the chat tool with four conversations last year. Then remove those, and keep the filter, the wishlist and the abandoned-cart email that customers actually use. Meanwhile replace heavy AJAX filters with an indexed alternative rather than deleting filtering altogether.
Measure the journey, not the homepage
Finally, test what customers do: category page, product page, add to basket, checkout — logged in, on a phone, on mobile data. Field data beats a single lab score, and your Largest Contentful Paint on a product page matters more than the homepage number. Google’s LCP guide explains what to look for. Then repeat monthly, since a shop drifts as products and campaigns pile up.
Done in this order, you speed up WooCommerce meaningfully without losing anything customers value. If your store is already large, or you are weighing platforms entirely, our comparison of WooCommerce and Shopify is a good next read — and our team can run the audit with your real traffic.
