A fashion retailer lifts mobile PageSpeed from 23 to 81.

The challenge

A Pune online fashion retailer had a mobile PageSpeed score of 23 after 3 years of stacking features onto a WooCommerce store. Each addition was reasonable on its own. Together they made the storefront crawl.

The store carried 4,200 product images, almost all unoptimised, and a long list of plugins fighting for the main thread. On a mid-range Android in Pune the LCP sat at 7.1s, which is well past the point most shoppers wait.

The approach

Webzenia treated the speed problem as the whole brief. The store stayed on WooCommerce, so the work was making the existing platform fast rather than replacing it.

All 4,200 product images were converted to WebP and compressed, the single biggest weight on the page. Lazy-loading was added so the browser fetched only what a shopper actually scrolled to.

Core Web Vitals were addressed directly. Render-blocking scripts were deferred, the plugin load was trimmed, and Cloudflare caching was tuned so repeat visits served fast from the edge.

Google Search Console and GA4 tracked the Core Web Vitals report and organic sessions, while Hotjar confirmed that faster pages held attention rather than just scoring better in a lab.

The results

Mobile PageSpeed climbed from 23 to 81, and LCP dropped from 7.1s to 2.2s. The store moved from failing Core Web Vitals to passing on the devices most of its Pune customers use.

Organic sessions rose 34%. Faster pages earned back the search visibility the slow ones had lost.

The gains stayed because the page weight stayed down. Speed work compounds in commerce, where every second of load is a checkout abandoned.

The stack behind it

• WoWooCommerceCommerce
• WoWordPressCMS
• GAGA4Analytics
• GSGoogle Search ConsoleSearch
• ClCloudflareSearch
• HoHotjarAnalytics