Merchants often chase page-speed plugins first. On WooCommerce stores I reverse that: measure, then images and scripts, then cache, then hosting.
1. Capture the LCP element
On most product pages the LCP element is the hero or first gallery image — sometimes a webfont block. Identify it in PageSpeed Insights or Chrome Performance before changing anything. If you lazy-load that first image, you are making LCP worse on purpose.
2. Split TTFB from frontend weight
A 2.5s LCP with 1.2s TTFB is a hosting / cache problem. The same LCP with 200ms TTFB and a 3MB product gallery is an asset problem. Fixing the wrong layer wastes a week.
3. Inventory third-party scripts on product templates
Reviews widgets, chat, heatmaps, and “optimize everything” plugins often enqueue on every PDP. Unload what checkout and PDP do not need. Cart fragments (wc-cart-fragments) are a classic hidden cost on non-cart pages.
4. Only then tune cache / CDN
Page cache for catalog; exclude cart/checkout/account. Object cache (Redis/Memcached) for product lookups. CDN for images with correct cache headers. This step is powerful after you know what the page is actually waiting on.
Public checklists
- Speed checklist: https://shopaiwp.com/guides/performance/wordpress-speed-optimization-checklist-2026/
- Merchant walkthrough: https://shopaiwp.com/guides/performance/how-to-speed-up-a-slow-woocommerce-store/
- Free human-verified audit (optional): https://shopaiwp.com/services/audits/free-wp-audit/
If you have fought a stubborn LCP on variable products, what was the real culprit — hero image, review widget, or TTFB?
Top comments (0)