All Posts
PerformanceMay 14, 20262 min read

WooCommerce Performance Optimisation: From 4s to 1.2s

A slow WooCommerce store is a revenue problem. Every additional second of load time costs conversions. This is the exact process I used to take a client's store from a 4-second LCP to 1.2 seconds — without a platform migration.

WooCommercePerformanceCore Web Vitals

Share this article

When this client came to me, their largest contentful paint (LCP) sat around 4 seconds on mobile — well into Google's "poor" range. Cart abandonment was high, and organic rankings had started slipping. The goal was simple: fix performance without a full platform migration.

Auditing the Bottlenecks

Before changing anything, I ran a full audit using Lighthouse, WebPageTest, and the Query Monitor plugin. The results were typical of an aging WooCommerce install: an unoptimized hero image at 2.4MB, 38 render-blocking scripts and stylesheets, and a product page that issued over 60 database queries.

Three areas accounted for almost all of the slowdown: images, plugin bloat, and database query efficiency.

Image Optimisation

Every product image was re-encoded to WebP with responsive srcsets, and the hero banner was replaced with a properly sized, lazy-loaded asset above the fold using fetchpriority="high". This single change cut LCP by nearly half.

Cutting Plugin Bloat

The store had accumulated 34 active plugins over several years — several of which duplicated functionality or loaded assets on every page regardless of need. We audited each plugin's actual usage and removed or replaced twelve of them, including three that were each loading their own copy of jQuery UI.

Plugin bloat is the silent killer of WooCommerce performance. Every plugin you add is a tax on every page load, whether that page needs it or not.

Database and Caching

We implemented object caching with Redis, added full-page caching for logged-out visitors, and cleaned up years of accumulated post revisions and transient options that had bloated the wp_options table to over 400MB.

  • Enabled Redis object cache for persistent query caching
  • Added a CDN in front of static assets
  • Reduced database table size by removing stale transients and revisions
  • Deferred non-critical JavaScript to after first paint

The Result

After two weeks of focused work, LCP dropped from 4 seconds to 1.2 seconds on mobile, and the site passed Core Web Vitals across all three metrics. Conversion rate improved by 18% in the following month — a direct result of fewer visitors abandoning before the page even rendered.

Conclusion

You don't always need a platform migration to fix WooCommerce performance. Most stores are held back by accumulated bloat rather than fundamental architecture problems — and a disciplined audit can recover most of that lost speed.

AB

Araib Butt

WordPress Developer · WooCommerce Specialist · Automation Engineer

Work Together