Fixing Core Web Vitals on WooCommerce

If you're on Avada, Divi, Bridge, BeTheme or one of the other older multi-purpose themes, that alone can be the bottleneck. These themes are built for design flexibility and feature parity, not for performance, and they ship megabytes of CSS and JavaScript that load on every page whether you use it or not.

Themes built specifically for performance, Blocksy, Kadence, GeneratePress, Astra (configured properly), regularly score 90+ on mobile out of the box on a fresh install.

A theme migration is the highest-impact CWV change you can make. It's also the most disruptive, so plan it properly. Budget 4 to 8 weeks for a serious WooCommerce store with custom templates and a non-trivial plugin stack.

Most slow WooCommerce stores have 30+ active plugins. Each one adds CSS, JavaScript and database queries. Use Query Monitor (free plugin, install on staging) to identify the worst offenders by time spent in PHP and number of database queries per request.

Replace heavy plugins (especially page builders, sliders, popup plugins, social sharing plugins) with lighter alternatives or native theme features. Elementor and WPBakery in particular are common culprits, both can be replaced by native Gutenberg blocks on a well-built theme.

Anything you can't justify by traffic, revenue or operational necessity should be removed. The 'we might need it one day' plugin is a Core Web Vitals tax you pay daily.

Use a serious caching layer. WP Rocket, FlyingPress or LiteSpeed Cache (if you're on LiteSpeed hosting) all work. Pair with Cloudflare or BunnyCDN for asset delivery. This alone can shave 1 to 2 seconds off LCP on a poorly cached store.

Configure object caching too, not just page caching. Redis or Memcached at the server level dramatically reduces database load, particularly on WooCommerce admin and cart operations.

Test cache invalidation properly after setup. A misconfigured cache can serve stale stock counts and prices, a real revenue and trust risk.

Convert all product imagery to WebP. Use ShortPixel, Imagify or Smush to bulk convert. Original 4MB JPGs from your photographer are not acceptable in 2026.

Lazy load below-fold images. Preload the LCP image (usually the hero on home, the first product gallery image on product pages, or the featured collection banner on category pages). Most performance plugins handle preload automatically once you tell them which selector wins LCP.

Serve responsive image sizes via srcset. WordPress handles this natively if your theme is built properly. Check on mobile, many themes ship desktop-sized images to mobile devices, which alone can tank LCP.

Defer or async every script that isn't critical for first paint. Move Google Tag Manager, analytics, chat widgets and review plugins to load after the LCP. WP Rocket and Perfmatters both make this manageable without code.

Audit third-party scripts ruthlessly. Each one is a request to an external server you don't control and a potential blocker. We've seen single chat widgets add 800ms to LCP on otherwise healthy stores.

Inline critical CSS where your theme doesn't already. This eliminates the render-blocking external stylesheet for the above-the-fold content.

Cheap shared hosting (Bluehost, GoDaddy, HostGator) caps your CWV scores no matter what you do at the application level. The server is slow, the database is contended, the TTFB is high before WordPress even starts running.

Move to managed WooCommerce hosting (Kinsta, WP Engine, Cloudways with a decent server, Rocket.net) and you'll see immediate TTFB improvements often in the 300 to 700ms range.

For stores over £1m in revenue, the difference between £30/month shared hosting and £150 to £400/month managed hosting is trivial against the revenue at stake. Stop saving £100 a month at the cost of organic rankings.

WooCommerce databases bloat fast. Old order metadata, expired transients, stale session data, leftover data from uninstalled plugins. Run WP-Optimise or similar quarterly to clean it up.

Old action scheduler tables in particular get huge on busy stores and slow down admin and cart operations. Truncate scheduled actions older than 30 days unless you specifically need them.

If your wp_options table is over 5MB, you have autoloaded options bloat. Audit and clean using a tool like Advanced Database Cleaner. This single fix has shaved 1+ second off TTFB on multiple stores we've worked with.

Cart and checkout are the highest-revenue pages on the site and often the worst performing because they bypass page caching by design. Optimise the application layer instead: minimal plugins active, database queries reviewed, third-party scripts loaded after submit rather than on page load.

If you're on WooCommerce Blocks (the new checkout), performance is generally better than the classic checkout but still benefits from the same discipline.