WooCommerce speed optimization: how to pass Core Web Vitals
To speed up a WooCommerce store, measure real-user Core Web Vitals first, then fix the biggest causes in order: slow hosting and missing page caching, oversized images, plugins loading scripts on every page, and heavy page builders. The targets are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, for at least 75% of visits.
- Speed affects sales before it affects rankings: small delays measurably cut conversions.
- Pass Core Web Vitals on real-user data: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 at the 75th percentile.
- Fix in order: hosting and caching, then images, then plugins and scripts, then the theme.
- Never cache cart, checkout or my-account pages. They must stay dynamic.
- Test each template (home, category, product, cart) on mobile, not just the home page.
Why does WooCommerce speed matter for SEO and sales?
Core Web Vitals are part of Google’s page experience signals, so speed can tip rankings between pages of similar quality. But the bigger effect is on sales: shoppers leave slow stores before they ever buy.
Different studies, same message: on a store, every second costs orders. And because WooCommerce runs on your own hosting with your own plugins, the speed is yours to fix.
What Core Web Vitals scores should a WooCommerce store hit?
Google measures three things on real visits, and a page passes when at least 75% of visits are in the “good” range for all three (the thresholds are Google’s):
| Metric | What it measures | Good | Usual WooCommerce cause |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | ≤ 2.5 s | Slow server, no page cache, huge hero or product images |
| INP (Interaction to Next Paint) | How fast the page reacts to taps and clicks | ≤ 200 ms | Too much JavaScript from plugins, builders and trackers |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | ≤ 0.1 | Images without dimensions, late banners, web fonts |
How do you measure WooCommerce speed properly?
Use real-user data to decide what to fix, and lab tests to check the fix worked:
- Search Console → Core Web Vitals. Real-user data grouped by similar URLs, so you can see whether product or category templates fail.
- PageSpeed Insights. Shows real-user data (when there’s enough traffic) and a lab test with specific suggestions.
- Test every template: home, a category, a product, cart and checkout. A fast home page hides slow product pages.
- Test on mobile first. That’s where most stores fail and where Google measures first.
- Re-test after each change, one change at a time, so you know what actually helped.
How do you fix a slow WooCommerce store?
In this order. The first two steps usually deliver more than everything after them combined:
- Hosting and PHP. A current PHP 8 version on a host built for WordPress. Cheap shared hosting is the most common reason WooCommerce feels slow.
- Page caching. Serve cached pages to visitors, excluding cart, checkout and my-account. On LiteSpeed servers, the LiteSpeed Cache plugin does this well.
- Object caching. Redis or Memcached cuts repeated database queries on busy catalogues.
- Images. WebP, sized to how they’re shown, with width and height set. Lazy-load below the fold, but never the main product or hero image.
- Plugin audit. Deactivate what you don’t use; for the rest, check what each loads with Query Monitor.
- Load scripts only where needed. Reviews, sliders and chat widgets don’t belong on every page. Newer WooCommerce versions load the cart fragments script only where needed, but some themes still force it everywhere.
- Fonts and CDN. Self-host fonts and preload the main one; put static files on a CDN.
Which plugins slow WooCommerce down the most?
Not every plugin is slow, but these categories are the usual suspects in our audits:
| Plugin type | Why it slows the store | What to do |
|---|---|---|
| Page builders | Heavy CSS and JavaScript on every page | Use the block editor or a lighter theme for key templates |
| Sliders and carousels | Large images and scripts above the fold | A single static hero image |
| Social feeds and chat widgets | Third-party scripts that block interaction | Load on click, or only on pages that need them |
| Several tracking and pixel plugins | Duplicate scripts on every page | One tag manager, only the tags you use |
| Related products and search plugins | Heavy database queries | Cache results or use a lighter option |
Speed is one half of WooCommerce technical health; the other is what Google indexes. Our guide to WooCommerce index bloat covers that side, and our technical SEO work fixes both.
What are the most common WooCommerce speed mistakes?
We see these in almost every WooCommerce speed audit:
- Chasing a 100 score in a lab test instead of passing real-user Core Web Vitals.
- Stacking optimisation plugins that fight each other: two caching plugins, two image optimisers.
- Lazy-loading the main image, which makes LCP worse, not better.
- Testing only the home page while product and category templates fail.
- Caching dynamic pages: cart, checkout and account pages must stay uncached.