Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

Core Web Vitals on WooCommerce: LCP, INP and CLS by Template

Three templates cause most failures: the product gallery, the variation script and the header banner. Field data versus lab data, and the fixes that move real numbers.

Core Web Vitals are three numbers, and on WooCommerce stores each one fails for a small set of predictable reasons. Fixing them is less about optimisation plugins and more about knowing which template is responsible.

LCP: what loads last when it should load first

Largest Contentful Paint measures when the biggest element in the viewport finishes rendering. On a product page that element is almost always the main product image. On a category page it is the first product image or the first row.

Four causes, in order of frequency:

1. The image is lazy-loaded. WordPress applies native lazy loading broadly, including to the element that should load immediately. The result: the browser waits, then fetches the largest image last. This is the single most common LCP failure on WooCommerce, and the fix is to mark the first image eager and give it a high fetch priority.

2. The image is too large. A 2400px original in a 600px slot delays the render regardless of connection speed. Serve the right size, in a modern format.

3. Render-blocking CSS and fonts. If the browser must download three stylesheets and two font files before painting, the image may be downloaded and still not displayed. Fonts loaded with @import inside CSS are especially costly.

4. Server response time on uncached pages. LCP cannot be faster than the time to first byte. A store with 900ms TTFB has an LCP floor of 900ms before any image loads — which is why the diagnosis sequence starts with server time.

What to fix first: the eager/high-priority attribute on the main image. It is a template change, not a plugin, and it usually moves LCP by several hundred milliseconds.

INP: the interaction that takes too long

Interaction to Next Paint replaced FID and measures responsiveness across interactions, not just the first one. On shops, the interactions that matter are add-to-cart, variation selection, quantity change, and filter clicks.

Common causes on WooCommerce:

  • AJAX add-to-cart that waits on a full WordPress bootstrap — 200–500ms of server work for a button press
  • Variation selection that recalculates prices and stock in JavaScript across hundreds of variations — the page freezes while it searches
  • Filter plugins that re-render the product grid entirely on each click
  • Third-party scripts blocking the main thread — chat widgets, review widgets, tracking pixels

The variation case deserves attention: a product with 500 variations, each with attributes, images and stock, produces a large JavaScript payload. Stores that generate every combination whether or not it is purchasable pay for combinations nobody can buy.

Third-party scripts are the other big one. A reviews widget and a chat widget can each add 300ms of main-thread work on mobile. Test with them disabled to see whether they are worth their cost.

CLS: the layout that moves while it loads

Cumulative Layout Shift measures unexpected movement. On product pages the causes are almost always structural:

Images without dimensions. No width and height means the browser does not know how much space to reserve, so content jumps when the image arrives. Every image needs explicit dimensions — a template-level fix.

Banners injected above content. Cookie notices, promo bars and announcement strips that render after first paint push everything down. Reserving space, or rendering them server-side, removes the shift.

Fonts that swap late. A script font loading after the system font renders produces a visible reflow. Preloading the font, or matching metrics, helps.

Ads or recommendation blocks that size themselves after load. If a block has no reserved height, everything below it moves.

CLS is the cheapest of the three to fix and the one most likely to be entirely caused by two or three templates.

Measurement: lab versus field

Lab tools test one page under one condition. Field data — from real users — is what search engines use. They often disagree, and when they do, field data is the truth.

Practical approach:

  1. Use field data to identify which page types fail
  2. Use lab testing to reproduce on that page type
  3. Fix the cause, not the score
  4. Verify with field data after two to four weeks — it lags by design

A common mistake is optimising until a lab score turns green on a desktop connection while field data on mobile is unchanged. Mobile is where most traffic is and where the failures concentrate: slower CPU, slower network, same payload.

The template map

Metric Where to look first
LCP Product image template: eager loading, size, format, priority
INP Add-to-cart handler, variation script, filter plugin, third-party widgets
CLS Image dimensions, injected banners, font loading

Three templates account for most WooCommerce Core Web Vitals problems: the product gallery, the variation script, and the site header with its cookie banner. If you only have time for three fixes, start there.

What does not help

Installing a “Core Web Vitals plugin”. These usually add more JavaScript, which is the problem.

Removing features to raise scores. A faster page that sells less is not an improvement.

Chasing 100. The difference between 90 and 100 rarely changes anything commercially; the difference between 45 and 80 usually does.

Core Web Vitals work overlaps almost entirely with technical SEO and hosting, which is why we usually assess them together with technical SEO rather than as a separate project — the fixes are in templates, not in policy.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote