Category

Core Web Vitals

Making the metrics Google measures move: INP, LCP, CLS, and the performance budget that keeps them green.

Website design work
Practical guide

Core Web Vitals: what to settle before implementation.

Core Web Vitals work fails when teams optimise the audit tool instead of the page people use. Start with field data by template, device, and traffic source. Then trace LCP, INP, and CLS to the server, browser task, asset, or component causing the delay.

One fast test run is not a control system. Set budgets for server response, JavaScript, images, fonts, and third-party scripts. Check them in delivery and watch field data after release so performance drift becomes visible before rankings or conversion fall.

Before you start

Three decisions that prevent avoidable rework.

Separate field data from laboratory tests and segment it by page type.
Fix the largest root cause before polishing low-impact assets.
Set release budgets and assign an owner for every third-party script.
Common questions

Direct answers about Core Web Vitals.

Which Core Web Vital should you fix first?

Fix the metric failing for the most important page type and the largest share of real users. The answer may differ between landing pages, article pages, and checkout.

Why do Lighthouse and Search Console disagree?

Lighthouse is one controlled test. Search Console aggregates real Chrome visits over time. Device mix, geography, cache state, and user behaviour make the field result different.

Articles

Read more about Core Web Vitals.

INP incident record connecting a URL group to a slow user interaction

Search Console INP problem: find the slow interaction

Map a mobile INP URL group to the user action, latency phase, responsible script, fix, and field-data validation.

Read guide ↗

Related categories

Related categories

Start here

Ready to talk.Book a short diagnostic.

Tell us what needs fixing

A process, a tool, a decision that's stuck. One sentence is fine.

By submitting you agree to our privacy policy.

We read every brief and reply within one business day.

Prefer to talk first?or request a tech stack audit or email us directly

Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.