WooCommerce Core Web Vitals Checklist
Audit your store against Google's official LCP, INP, and CLS performance benchmarks to ensure mobile search ranking success.
Preload Main Product Gallery Image
Add rel="preload" as="image" for single product featured image to ensure LCP under 2.5s.
Convert Images to WebP or AVIF Format
Serve next-gen image formats to reduce hero image payload weight by 60%+.
Disable Cart Fragments on Catalog Pages
Remove wc-ajax=get_refreshed_fragments execution to eliminate main thread blocking on click.
Defer Non-Essential Payment Gateway Scripts
Load Stripe and PayPal SDKs asynchronously to reduce Interaction to Next Paint latency.
Set Explicit Width & Height on Product Images
Prevent Layout Shift by reserving image container aspect ratios before images load.
Reserve Notice & Coupon Banner Containers
Avoid shifting page content dynamically when WooCommerce notice alerts pop up.
Serve Catalog Pages from Static Edge CDN
Deliver pre-built HTML from edge nodes to guarantee TTFB under 100ms globally.
Using This Checklist to Systematically Pass WooCommerce Core Web Vitals
1. What This Checklist Actually Covers
This is an interactive self-audit built around the seven most common WooCommerce-specific causes of failed Core Web Vitals, grouped by which metric they affect: two items target LCP (image preloading and next-gen formats), two target INP (cart fragments and gateway script deferral), two target CLS (image dimensions and notice/banner containers), and one targets TTFB (static edge delivery). Clicking a card marks it complete and updates the progress bar at the top — the checklist state is stored only in your browser session, not saved to an account.
2. How to Use the Checklist Effectively
Work through the items in order of metric severity: check your current LCP, INP, and CLS scores first (using PageSpeed Insights or the Nimbica Core Web Vitals Checker), then focus on the checklist section matching your worst-performing metric. For example, if CLS is failing, prioritize "Set Explicit Width & Height on Product Images" and "Reserve Notice & Coupon Banner Containers" before spending time on LCP-only items. Re-test after each change since WooCommerce metrics can interact — disabling cart fragments, for instance, can also incidentally reduce main-thread work that was contributing to layout shift.
3. Why WooCommerce Needs a Specialized Checklist
Generic WordPress speed checklists miss WooCommerce-specific failure modes. Cart fragments, payment gateway SDKs, coupon notice banners, and product variation JSON are all sources of Core Web Vitals regressions that don't exist on a typical blog or brochure site. A store can follow every generic "optimize images and minify CSS" tip and still fail INP because of an unthrottled AJAX call firing on every page, or fail CLS because a "free shipping over $50" notice banner injects itself above the fold after initial render.
4. Worked Example
A store fails CLS at 0.31 (poor) on its product pages. Working through the checklist: item "cls-1" (explicit image dimensions) reveals the theme's gallery template omits width/height attributes, causing the browser to reflow content once each image's true dimensions load. Fixing this alone typically drops measured CLS into the 0.05-0.15 range. Item "cls-2" (reserving notice containers) then addresses a secondary shift caused by a coupon banner plugin that injects its markup after page load — reserving a fixed-height container for it before the plugin renders removes the remaining shift.
5. Practical Use Cases
- Pre-launch QA: Run through the full checklist before launching a new WooCommerce theme or major redesign.
- Client handoff documentation: Agencies can use the checklist as a shared reference when explaining to a client which specific fixes were applied and why.
- Post-regression triage: When a Search Console Core Web Vitals report shows a sudden drop, work through the checklist to identify which recent change likely caused it.
6. Common Mistakes & Limitations
Checking a box here does not verify the fix was implemented correctly — it's a planning and tracking aid, not an automated scanner. A common mistake is marking "Preload Main Product Gallery Image" complete after adding a preload tag but pointing it at the wrong image variant (e.g. a thumbnail instead of the actual LCP element), which provides no benefit. Always confirm each item with a real Lighthouse or field-data test rather than relying on the checklist alone as proof of compliance.
Frequently Asked Questions
What are the target Core Web Vitals metrics for WooCommerce?
Google recommends: LCP (Largest Contentful Paint) under 2.5s, INP (Interaction to Next Paint) under 200ms, and CLS (Cumulative Layout Shift) under 0.1 on mobile devices.
How is this checklist different from a Lighthouse or PageSpeed Insights scan?
This checklist is a manual, self-audit reference tied specifically to WooCommerce architecture (cart fragments, product galleries, checkout notices) rather than a live scan. For an automated live measurement of your actual store, pair this checklist with the Nimbica Core Web Vitals Checker or Google PageSpeed Insights.
Which WooCommerce page type is hardest to pass Core Web Vitals on?
Checkout and cart pages are typically the hardest, since they load payment gateway scripts, coupon/notice logic, and dynamic totals that cannot be cached or pre-rendered. Product and category pages are usually easier to fix because their content is largely static per visitor.
Do I need to complete every item on this checklist to pass Core Web Vitals?
Not necessarily — Core Web Vitals are evaluated per metric (LCP, INP, CLS) at the 75th percentile of real visits, so a store can pass all three without completing every checklist item if the underlying causes don't apply to their theme or plugin stack. Use the checklist to prioritize the items most relevant to issues you've already observed.
Why does disabling cart fragments on catalog pages help INP?
WooCommerce's cart fragments AJAX call (wc-ajax=get_refreshed_fragments) refreshes the mini-cart on every page load by default, including category and product pages where the cart widget may not even be visible. This background request competes for main-thread time and can delay how quickly the page responds to a shopper's first click or tap.
How often should I re-run this checklist?
Re-check after any theme update, new plugin installation, or checkout/gateway change, since these are the most common sources of Core Web Vitals regressions on WooCommerce. A quarterly review is a reasonable baseline even without changes, since third-party scripts (ad pixels, chat widgets) tend to accumulate over time.
What is the difference between LCP, INP, and CLS in plain terms?
LCP measures how long the largest visible element (usually a hero image or product photo) takes to render. INP measures how responsive the page feels when a visitor clicks, taps, or types. CLS measures how much visible content unexpectedly jumps around while the page is loading.
Pass 100/100 Core Web Vitals on WooCommerce automatically
Nimbica handles static compilation, image WebP conversion, and edge CDN deployment out of the box.
