A slow store costs you twice: shoppers leave before they buy, and your team wastes time waiting on a sluggish admin. The good news is that most WooCommerce performance problems come from a short list of causes. Here is the order in which I work through them.
1. Measure before changing anything
Run your home page, a category page and a product page through Google PageSpeed Insights, and check the Core Web Vitals report in Search Console if you have one. Focus on the three metrics Google uses: Largest Contentful Paint (how quickly the main content appears), Interaction to Next Paint (how quickly the page responds to taps and clicks) and Cumulative Layout Shift (how much the layout jumps around). Note the numbers, so you can prove each change helped.
2. Fix the foundation: hosting, PHP and caching
- Use hosting sized for WooCommerce, not the cheapest shared plan. Dynamic pages such as cart, checkout and account cannot be fully cached, so server speed matters.
- Run a current, supported PHP version. Upgrades are often one of the cheapest speed improvements available.
- Add page caching for public pages, and make sure cart, checkout and my-account pages are excluded from it.
- Where the host supports it, add a persistent object cache such as Redis to reduce repeated database queries.
3. Make images earn their place
Product photos are usually the heaviest part of a store. Serve modern formats such as WebP or AVIF, make sure WordPress generates and uses the right image sizes, and lazy-load images further down the page. Do not lazy-load the main hero or product image, because that delays the Largest Contentful Paint.
4. Audit plugins and scripts
Every plugin can add database queries, scripts and styles to every page. List what is installed, remove what you no longer use, and replace heavy plugins that duplicate features you already have. Then look at third-party scripts such as chat widgets, review badges, heatmaps and multiple tracking tags. Load only the ones you actively use, and delay non-essential ones until after the page is interactive.
5. Watch WooCommerce-specific overheads
- Cart fragments: check whether the AJAX request that refreshes the mini-cart runs on pages that don't need it.
- Order storage: newer WooCommerce versions support High-Performance Order Storage, which keeps orders in dedicated tables. It is worth planning a careful migration for stores with many orders.
- Search and filters: large catalogs often need an indexed search or filtering solution instead of default queries.
- Database housekeeping: clear expired transients, old revisions and leftover tables from removed plugins.
6. Keep it fast
Performance is not a one-off task. New products, plugins and marketing scripts slowly add weight. Re-test key pages after major changes, keep WordPress, WooCommerce and plugins updated on a staging copy first, and review your Core Web Vitals every month or two. A short, regular check is far cheaper than a rescue project once the store has become slow.