Free, and the single most effective change available to a WooCommerce store, provided your host offers Redis. It stores the results of database queries in memory so that repeated lookups do not hit the database again.

The reason it matters so much here is that it works on exactly the pages page caching cannot touch. A cart page runs dozens of queries to assemble products, prices, tax rules and shipping options; with an object cache most of those are answered from memory. WordPress has a built-in object cache that lasts only for the duration of a single request, so without a persistent backend the same query is repeated on every page load forever. Ask your host whether Redis or Memcached is available; on many managed plans it already is and is simply not switched on.

• Price: Free plugin; needs Redis on your host
• Helps: Cart, checkout and account pages directly
• Best for: Every store whose host supports it
• Watch out for: Without a Redis backend it does nothing

Free, and the strongest all-round option if your host runs LiteSpeed or OpenLiteSpeed. It provides server-level page caching for the pages that can be cached and an object cache for the pages that cannot, from one plugin at no cost.

That combination is unusually well suited to stores, because a shop needs both halves and buying them separately is the normal arrangement. Its WooCommerce handling includes appropriate exclusions and cache purging when stock or prices change, which is the fiddly part of caching a store correctly. Check your server software before comparing anything else: if it says LiteSpeed, the decision is made and the cost is zero. On Apache or Nginx it remains a capable optimisation plugin without its defining advantage.

• Price: Free
• Helps: Page and object caching, with WooCommerce-aware purging
• Best for: Stores on LiteSpeed hosting
• Watch out for: Needs a LiteSpeed server for the main benefit

$59 a year for one site, $119 for three, $299 for fifty, and the safest paid choice for a store because its WooCommerce handling is correct by default rather than by configuration.

Cart, checkout and account pages are excluded automatically, which sounds trivial until you consider what happens when they are not. That default is worth the licence on its own for a store owner who is not going to audit cache rules. Beyond that it handles file optimisation, lazy loading and JavaScript delay, and its database tools cover the revision accumulation a busy store generates through product edits. What it does not do is object caching, so on a store it is half the answer and should be paired with Redis.

• Price: $59/yr for 1 site, $119 for 3, $299 for 50
• Helps: Cacheable pages, with correct store exclusions by default
• Best for: Stores wanting safe defaults with no tuning
• Watch out for: No object caching; pair it with Redis

Free, and disproportionately effective on stores with large catalogues. It adds indexes to WordPress’s core tables so that the queries a shop runs constantly become faster without anything being deleted.

WooCommerce is demanding on postmeta in particular, because product attributes, prices, stock levels and variations all live there. On a catalogue of several thousand products with variations, that table reaches millions of rows, and WordPress’s default indexes were not designed for it. The symptom is a slow admin, slow product filtering, and slow order screens, all of which are query problems rather than caching problems. Because it adds indexes rather than removing data, it is among the safest interventions available. Enable WooCommerce’s High-Performance Order Storage alongside it if you have not, since that moves orders out of the posts table entirely.

• Price: Free
• Helps: Product queries, filtering, and admin order screens
• Best for: Catalogues above a few thousand products
• Watch out for: Index building takes time on very large tables

$29.95 a year for one site, $59.95 for three, $124.95 for unlimited sites, and the tool that addresses the most WooCommerce-specific performance problem there is: cart fragments.

WooCommerce uses an AJAX request to keep the cart total current in the header. That request is uncacheable by design and it fires on every page load, including on blog posts and the homepage where no cart is involved. On a slow server it adds noticeable delay to every page on the site. Perfmatters lets you disable cart fragments on pages that do not need them, and disable WooCommerce’s scripts and styles entirely outside the shop, which on a content-heavy site with a small store is a substantial saving. The caution is to test the header cart updates correctly after any change, since that is what fragments exist to do.

• Price: $29.95/yr for 1 site; $124.95 for unlimited
• Helps: Cart fragments and WooCommerce assets outside the shop
• Best for: Content sites with a small store attached
• Watch out for: Test that the header cart still updates

Not a plugin, and frequently the honest answer. If your cart and checkout run live on every request, the speed of those pages is a direct function of your server, and no plugin changes that arithmetic.

Three things to look for specifically, none of which appear in the marketing. Redis or Memcached availability, since object caching is your main lever and some cheap plans do not offer it at all. A current PHP version, because each recent release has been meaningfully faster than the last and hosts do not always upgrade you. And database resources rather than only disk and bandwidth, since a store is database-bound and shared plans frequently throttle exactly that. Moving from a crowded shared plan to something with dedicated resources routinely does more for checkout speed than every plugin in this article combined, and it costs less than a lost weekend of debugging.

• Price: Whatever the upgrade costs
• Helps: Every uncacheable page, which is the ones that matter
• Best for: Stores on crowded shared hosting
• Watch out for: Confirm Redis, PHP version and database resources