WooCommerce Speed Optimisation: The Complete Guide

Standard WordPress caching strategies don't work well for WooCommerce. Product pages with variable pricing, cart contents that change per user, and checkout flows that must never be cached all create complexity that generic caching plugins struggle with.

WooCommerce also generates significantly more database queries than a standard WordPress site. Product catalogues, order histories, customer data, and inventory management all add database load.

The key to WooCommerce caching is knowing what to cache and what not to cache. Product catalogue pages, category pages, and static content pages can be aggressively cached. Cart pages, checkout pages, and account pages must always be served dynamically — configure your caching plugin to exclude them, and test with a real item in the basket.

For the dynamic pages you cannot cache, the biggest win is a persistent object cache. WooCommerce makes thousands of repeated database lookups per request; Redis keeps those results in memory so PHP stops asking the database the same questions. On G7Cloud you can attach a managed Redis 7 instance to your store as an add-on — no server administration required.

The other half of the equation is isolation. A checkout spike is exactly the wrong moment to discover you share PHP workers with fifty other sites. Every G7Cloud store runs in its own dedicated container, so Black Friday traffic on someone else's shop is not your problem.

WooCommerce stores an enormous amount of data in the WordPress database. Over time, post revisions, transient data, and orphaned metadata accumulate and slow down queries.

Regular database maintenance — cleaning up revisions, optimising tables, and removing expired transients — significantly improves WooCommerce query performance. On G7Cloud each store gets its own MariaDB database (never shared tables), with phpMyAdmin and WP-CLI available for exactly this kind of housekeeping: a monthly wp transient delete --expired costs nothing and pays for itself.

Product images are typically the heaviest assets on a WooCommerce site. A catalogue with 500 products might have 2,000+ images across different sizes. Without optimisation, these images consume gigabytes of bandwidth.

Compress product photography before upload, serve modern formats like WebP where your theme supports them, and make sure below-the-fold product grids lazy-load. On large catalogues, an hour spent batch-compressing images often beats a week of server tuning.