A slow WooCommerce store leaks revenue on every product view. The good news: the fixes are known and ordered. This is the priority list we apply on client stores — roughly in descending impact — tuned specifically for Woo (see the Core Web Vitals guide for the scoring details).
1. Get the baseline first
Run PageSpeed Insights on home, category, product and checkout. Record LCP, TTFB and total weight. Without the baseline you cannot tell which fix worked — and neither can the plugin you are about to buy.
2. Server & caching (the biggest lever)
- PHP 8.2/8.3 + OPcache — hosts on PHP 7.x are leaving performance on the table
- Full-page cache for catalog pages; cart/checkout/account excluded
- Redis or Memcached object cache — product lookups and sessions stop hammering MySQL
- TTFB over ~600ms on cached pages is a hosting problem, not a plugin problem — see migration options
3. Images (usually the #1 page-weight item)
- Bulk convert to WebP/AVIF; regenerate thumbnails to real display sizes
- First gallery image: preloaded, never lazy-loaded (it is the LCP element)
- Serve through a CDN with correct cache headers
4. The WooCommerce-specific traps
Cart fragments: WooCommerce’s default wc-cart-fragments loads the full cart via AJAX on every page for every visitor — a classic hidden killer. Replace with a lightweight AJAX count or context-aware loading. Checkout bloat: dozens of plugins enqueue their CSS/JS on checkout “just in case”. Unload everything that is not payment-critical.
5. Database hygiene
- Autoloaded options over ~1 MB total — audit and move the heavy ones to on-demand loading
- Expired transients and old action-scheduler entries on a schedule
- Post revisions and orphaned meta cleaned on large catalogs
6. Plugins: subtract before adding
Every “speed plugin” you add to fix a slow store usually adds a problem. The 12,000-product store in our speed case study got faster by removing two optimizer plugins and replacing them with a proper pipeline. Fix the causes; the plugins are symptom management.
Realistic expectations
| Fix | Typical LCP gain |
|---|---|
| Object cache + page cache tuning | 0.8 – 2.0s |
| Image pipeline overhaul | 0.5 – 1.5s |
| Asset unloading + critical CSS | 0.3 – 0.8s |
| Theme swap to lean base | 0.2 – 0.5s |
Want the results without the project management? Our speed optimization service runs this exact list with documented before/after numbers — start with the free audit.
Frequently asked
If your TTFB on cached pages is high, hosting is likely the bottleneck and an upgrade or migration is the right call. If TTFB is fine and the page itself is heavy, a new hosting plan changes nothing. Mobile LCP under 2.5s for field data, TTFB under 500ms, and checkout feeling instant. Below that, conversion data (see our case study: +18%) beats chasing single milliseconds.My host offers 'turbo' plans — should I upgrade instead?
How fast is 'fast enough' for WooCommerce?
