WooCommerce page speed optimisation is one of the highest-ROI technical investments a store owner can make. Google’s data consistently shows that each additional second of page load time reduces conversions by 7–12%. For a store doing £10,000/month, a two-second improvement in LCP can translate to £840+ in recovered revenue monthly — without spending a penny on advertising.

This guide addresses WooCommerce page speed optimisation in priority order — from the highest-impact server-level changes through to image delivery and database hygiene. Start at step one and implement sequentially. Each step is independent, so you can stop at any point and still have delivered a measurable improvement.

WooCommerce page speed optimisation stack — PHP OPcache, Redis, WebP images, CDN delivery, and database tuning by CodeAtoZ

PHP OPcache is the single biggest win in WooCommerce page speed optimisation and it costs nothing — it ships with PHP 7.0+ and just needs to be enabled. OPcache stores compiled PHP bytecode in memory so WordPress and WooCommerce do not reparse and recompile every file on every request. On a typical WooCommerce installation this reduces Time to First Byte by 30–50%.

Check whether OPcache is active by creating a temporary phpinfo.php file and searching for “opcache.enable”. If it shows as disabled, ask your host to enable it or add the following to your php.ini. Most managed WordPress hosts — Kinsta, WP Engine, Cloudways — enable OPcache by default. Shared hosting on cPanel often does not.

; Recommended OPcache settings for WooCommerce
opcache.enable=1
opcache.enable_cli=1
opcache.memory_consumption=256
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=10000
opcache.revalidate_freq=60
opcache.save_comments=1

Every WooCommerce page load executes dozens of database queries — product prices, stock levels, customer session data, transients, and widget caches. Without an object cache, every one of these queries hits MySQL on every page load. Redis eliminates this by storing the query results in memory. The second and subsequent page requests for the same data skip the database entirely.

The implementation for WooCommerce page speed optimisation via Redis has two parts: a Redis server (most managed hosts provide this or you can add a Redis instance via Render or Railway) and the object-cache.php drop-in file in wp-content/. The Rhubarbgroup Redis Object Cache plugin provides the drop-in and a GUI for monitoring cache hits. Expect a 40–70% reduction in database queries after enabling Redis.

• Provision Redis server — your host’s control panel or a standalone Redis instance
• Install Redis Object Cache plugin — adds object-cache.php drop-in automatically
• Add WP_REDIS_HOST and WP_REDIS_PORT to wp-config.php
• Enable cache from the plugin settings — verify hit rate in the diagnostics panel
• Monitor the hit rate — aim for 80%+ after the cache warms up on first-day traffic

Images are typically 60–80% of total page weight on WooCommerce product and category pages. WooCommerce page speed optimisation for images has three components: format conversion to WebP, responsive sizes via srcset, and lazy loading for below-fold images. WordPress 5.8+ handles WebP uploads natively, but you still need to convert your existing image library and configure Cloudflare or a plugin to serve WebP to supporting browsers.

For Largest Contentful Paint (LCP) — the Core Web Vital that matters most for WooCommerce page speed optimisation — the hero image or above-fold product image is almost always the LCP element. This image must not be lazy-loaded. Add fetchpriority="high" to the hero image tag and ensure it is preloaded in the <head> if your theme does not do this automatically.

The most overlooked area in WooCommerce page speed optimisation is the WordPress database. Two issues cause the most damage: bloated wp_options autoloaded data and missing database indexes. Both are invisible in Lighthouse scores but show up as slow TTFB on page 2+ when Redis has not yet cached those specific queries.

Autoloaded options are loaded on every page request regardless of whether they are used. Plugins frequently add rows to wp_options with autoload=yes and never clean them up. Run the following query to find the offenders and evaluate which are safe to set to autoload=no.

-- Find largest autoloaded options (run in phpMyAdmin or Adminer)
SELECT option_name, LENGTH(option_value) AS size_bytes
FROM wp_options
WHERE autoload = 'yes'
ORDER BY size_bytes DESC
LIMIT 25;

-- After identifying safe candidates, disable autoload:
UPDATE wp_options
SET autoload = 'no'
WHERE option_name = 'your_plugin_transient_name';

A CDN is the final layer in a complete WooCommerce page speed optimisation stack. Cloudflare’s free tier is sufficient for most WooCommerce stores — it caches static assets at edge nodes worldwide, adds HTTP/2 and HTTP/3 support, and can serve WebP images automatically via Polish (paid plan) or via a page rule on the free plan. TTFB improvements of 200–400ms are typical for international visitors.

Configure Cloudflare with caching rules that cache static assets (CSS, JS, images) aggressively while passing WooCommerce cart, checkout, and account pages through uncached. The Google Web.dev performance guidelines provide the authoritative reference for Core Web Vitals targets. The PageSpeed Insights tool, alongside the Chrome Lighthouse documentation, gives per-URL field data from real users — use it before and after every WooCommerce page speed optimisation change to measure real-world impact rather than lab scores.