Skip to main content
Core Web Vitals

Core Web Vitals in 2026: INP, LCP and What Actually Moves

The Core Web Vitals interventions that produce measurable p75 improvements on real user data — and the ones that don't.

Core Web Vitals in 2026: INP, LCP and What Actually Moves — article hero

Most Core Web Vitals audits produce a lab-data PDF that never ships. This post focuses on the field-data interventions that move p75 numbers within a single release cycle.

Fix LCP with the image

On mobile, the LCP element is almost always the hero image. Serve AVIF, preload it with fetchpriority=high, and stop lazy-loading it. That single change fixes LCP for most templates.

Fix INP with the main thread

INP is a main-thread problem. Break long tasks, defer non-critical scripts, and audit third-party tags — analytics, chat, and consent scripts are the usual culprits.

CLS is a discipline problem

Reserve width and height on every image, iframe, and ad slot. Avoid injecting content above the fold after load. That's it.

Frequently asked questions

Does CrUX data always match my analytics?

No. CrUX is p75 across Chrome users with Chrome UX Report participation. Your analytics is a different sample. Reconcile them before making decisions.

Are Core Web Vitals still a ranking factor?

Yes, as part of Page Experience — but they are a tie-breaker, not a lever that ranks weak content.

Tags

Work with our team on this

Explore the services we use to ship the playbook above.

Related articles

Free strategy session

Want this playbook implemented on your site?

Book a free 30-minute audit with a senior strategist. We'll turn this article into a prioritized roadmap for your brand.