The Best Caching Plugins For WooCommerce

Caching is the single biggest lever for WooCommerce speed, but the plugin you pick and how you set it up matter a lot. Two stores running the same theme can feel completely different because of a few caching settings.

Our rule is simple: reliability comes before speed. A store that’s fast but shows the wrong stock level or breaks at checkout is costing you money. The tools below are the ones we’ve found predictable, stable and well supported across a very large number of WordPress sites.

Page Caching

A page cache builds each page ahead of time and stores the finished result. The database lookups, PHP work and HTML generation all happen once, so when a visitor asks for the page the server just hands over the saved copy.

WP Alpha hosting includes server level caching, and a caching plugin still earns its place on top of server caching because it manages the cache for you. It can build the cache before visitors arrive and clear the right pages when something changes. That matters on WooCommerce, where products move in and out of stock. A stale cached page that shows the wrong stock status frustrates shoppers and loses sales.

WP Rocket: best for the DIYer

WP Rocket is our pick for store owners who aren’t especially technical and are doing the work themselves. It’s easy to use and its settings are hard to get badly wrong.

FlyingPress: best for performance and technical users

FlyingPress suits developers and anyone chasing extra performance. It has more technical settings to work through, which also means more ways to break something, so change one thing at a time and test as you go.

Caching Plugin Mistakes to Avoid on WooCommerce

Whichever plugin you choose, these are the mistakes we see most often. Each one can hurt speed, SEO or both.

1. Never run two caching plugins at once

Two page caching plugins fighting over the same pages makes the site slower, not faster. Pick one and remove the other.

2. Leave CSS and JS minification off

Both plugins still offer to minify CSS and JavaScript. Don’t use it. It does nothing meaningful for speed and it damages caching. A minified file is saved under a temporary filename that changes every time the page cache is cleared. The copy in your visitor’s browser stops being used, so their next visit is slower, and search crawlers like Google come back looking for the old file and hit a 404, which is bad for SEO.

Modern servers compress files with Gzip and Brotli, which does a far better job than minification. Cloudflare removed its own minify feature in 2024.

3. Don’t combine CSS and JS files

With HTTP/3 on the modern web, combining files generally makes them slower to load. Combined files also get a temporary filename that changes on every cache clear, which brings the same problems as minification: slower repeat visits and more 404s for search crawlers.

4. Be very careful with delay JS

Both plugins can hold back JavaScript until the visitor interacts with the page. That makes a speed test score look better, but WooCommerce leans heavily on JavaScript, so in the real world it can make the store slower and break features.

5. Turn on caching for logged-in users

This setting is usually off by default and it’s one of the most important for WooCommerce. Lots of shoppers log in before they buy, and without it every page they view is built from scratch. The risk of enabling it is close to zero. We cover the rest of the logged-in picture in how to speed up WooCommerce for logged-in users.

Object Caching

Object caching is a type of database caching. It stores the results of repeated database queries in memory, which speeds up the parts of a store that can’t be page cached: the admin area, My Account, the cart and checkout.

Many hosts provide it without needing a separate plugin. WP Alpha includes Redis, and you can set up Redis object caching here. If you ever need a standalone plugin, the one to use is Redis Object Cache.

Use Cloudflare as Your CDN

Cloudflare is the only CDN we recommend for WooCommerce. At a minimum, add their APO service for $5 a month, which caches pages on Cloudflare’s own servers. It takes a large amount of load off your hosting and makes the store noticeably quicker for shoppers. For bigger stores, the $25 a month plan is worth it for its extra speed features and a proper firewall. If the budget is tight, start with the free plan.

Never run two CDNs together. Stacking them makes the site much slower. Cloudflare rules are also a good way to cut load and block brute force attacks on WooCommerce.

Other Tools Worth Adding

Many optimisation plugins overlap. Only switch each feature on in one place. For example, several plugins can lazy load images, but you want exactly one of them doing it.

• Perfmatters: a great general purpose optimisation plugin. We rely heavily on its lazy load and image preload features to speed up what shoppers see first.
• A WooCommerce robots.txt file: the right rules reduce server load and improve security and SEO. See our WooCommerce robots.txt guide.
• Database optimisation: a tidy database helps every uncached request. Start with speeding up a slow WooCommerce backend and optimising your WooCommerce database.

For the parts of a store that caching can’t help, see our guides to a slow WooCommerce checkout and a slow add to cart.