Define scope
Select templates, URLs, devices, regions and important interactions. Record dates, sample volume and intervening changes.
GUIDE / PROTOCOL
A lab score describes one test; experienced performance depends on users, devices and journeys.
Direct answer
Separate field from lab data, mobile from desktop, and pages from journeys. Track LCP, INP and CLS distributions, then find the responsible resource or interaction before changing the site.
01 / Review method
Select templates, URLs, devices, regions and important interactions. Record dates, sample volume and intervening changes.
Review field Core Web Vitals at the 75th percentile; use lab traces for reproduction and diagnosis, not as a substitute for users.
Identify the LCP element, critical resources, blocking scripts, long tasks, layout shifts and third parties. Support each hypothesis with a trace.
Prioritize by reach and cost, compare before and after under similar conditions, and watch for regressions.
02 / Evidence to keep
Source, dates, device, region, URL or page group and sample size.
LCP, INP and CLS with percentile, range and field/lab distinction.
Network timeline, affected element, task or resource and tested hypothesis.
Change, owner, observed effect and monitoring threshold.
AFTER THE REVIEW
Do not claim user improvement yet. Check collection delay, population, cache, device mix and URLs before attributing the gap.
Inspect the interactions affecting INP, JavaScript tasks and third parties; retest the same journey after a fix.
03 / FAQ
Field data spans real devices and networks; a lab uses a controlled scenario. Compare populations and dates.
A value that 75% of measured visits meet or improve on for a given metric and population.
No. Test multiple interactions and use field data; a lab trace explains a particular case.
Start with images that actually affect perceived loading, including dimensions and priority.
04 / Official references