Core Web Vitals in Practice: A Checklist That Actually Moves Revenue

Speed isn't a vanity metric. Faster pages convert better, rank better and make every advertising dollar go further. Google's Core Web Vitals give teams a shared language for performance — here's the practical checklist we use to improve them.

The three metrics that matter

• Largest Contentful Paint (LCP) — how quickly the main content appears. Aim for 2.5 seconds or less.
• Interaction to Next Paint (INP) — how quickly the page responds to taps, clicks and typing. Aim for 200 milliseconds or less.
• Cumulative Layout Shift (CLS) — how much the layout jumps while loading. Aim for 0.1 or less.

Measure with real-user field data, not only lab tests. Search Console and analytics tools show how visitors on real devices and networks actually experience your site.

Improving LCP

• Serve images in modern formats such as AVIF and WebP, sized for each screen
• Preload the hero image and never lazy-load content above the fold
• Render pages on the server or at the edge so HTML arrives complete
• Self-host and subset fonts, and use a swap display strategy
• Put a CDN in front of static assets and cache them aggressively

Improving INP

• Ship less JavaScript: remove unused libraries and split code by route
• Keep interactive components small and defer non-critical widgets
• Break up long tasks so the main thread can respond to input
• Load third-party scripts such as chat widgets after interaction or when idle

Improving CLS

• Always set dimensions or aspect ratios on images, videos and embeds
• Reserve space for banners, consent notices and ads
• Avoid inserting content above existing content after load
• Animate with transforms rather than properties that trigger layout

Make performance a habit, not a project

Performance regresses quietly: a new tag here, a heavier image there. Teams that stay fast build guardrails into their workflow.

1. Set performance budgets for JavaScript, images and LCP
2. Run automated Lighthouse checks in continuous integration
3. Review third-party scripts quarterly and remove what isn't earning its keep
4. Monitor field data after every major release

On one retail project, cutting mobile LCP from 4.1 to 1.3 seconds coincided with a 37% lift in conversion. Speed is a revenue feature.