This WooCommerce performanjce optimisation project was about solving an LCP problem without creating a UX problem somewhere else. The client had seen a serious drop in rankings and poor Core Web Vitals scores across product pages, with visibly slow image loading on mobile making the issue obvious to users as well as search engines.
What They Needed
They needed the slowest parts of the product-page experience diagnosed and improved without destabilising the rest of the site.
- Better LCP performance on product pages.
- Faster, clearer image loading on mobile.
- Changes that could be tested and rolled back safely.
- A sensible balance between Google’s metrics and real user experience.
The key challenge was that performance issues were coming from several places at once rather than one single broken setting.
How I Helped
WooCommerce Performance Optimisation Without Guesswork
I handled it as a WooCommerce Services and performance-focused troubleshooting job rather than chasing speed scores blindly.
- I audited both live and staging environments to isolate the real causes of the slow product-page experience.
- I identified several issues working together, including render-blocking CSS, theme logic that disabled lazy loading, JavaScript delays, and Cloudflare Rocket Loader interference.
- I replaced WP Meteor with Perfmatters for more control over script and asset handling.
- I removed unused CSS, inlined critical CSS, and adjusted image and iframe lazy loading so the right elements loaded at the right time.
- I overrode theme behaviour where it was actively hurting image loading.
- I improved parts of the product-page experience around media and buy-button handling so the frontend felt better as well as benchmarking better.
The important part was that each change was tested in a controlled way instead of being piled on all at once.
Results
The site’s product pages became faster and more usable.
- Product-page LCP performance moved back into the green.
- PageSpeed Insights scores reached the high 90s on mobile for key pages.
- Key images loaded more predictably and visibly.
- The frontend felt cleaner without sacrificing important site behaviour.
- The changes were modular and easier to reason about later.
This was not just about getting a nicer score. It was about restoring confidence in how the product pages actually behaved.
“Ray took the time to really understand what we needed — not just technically, but in terms of how the site feels to customers. He explained every step clearly, avoided risky changes, and worked with us to strike the right balance between Google’s metrics and real user experience. We’re now seeing much faster load times and better engagement. Hugely appreciated!“
— Andrew B.
Why It Worked
This worked because the project treated performance as a technical systems problem with UX consequences, not as a checklist of plugin toggles.
The main decisions that mattered were:
- diagnosing the different causes instead of assuming one plugin could solve everything
- making staged, testable changes rather than broad risky ones
- balancing lab metrics with the actual feel of the product page
- keeping the final implementation modular and reversible
That is what made the gains more trustworthy than a quick optimisation pass.
Related Work
If you want to see more project work, my Portfolio is the best place to continue.
For slow or awkward WooCommerce stores that need technical cleanup rather than generic speed tips, WooCommerce Services is a good place to start.
For more general site performance and technical improvement work, Performance Optimisation is also worth a look.