Core Web Vitals: Diagnose LCP, INP and CLS

Core Web Vitals describe loading, interaction responsiveness and visual stability. Diagnose the metric that is failing for the relevant users before changing assets or chasing a higher Lighthouse score.

Separate field measurements from a lab run

Field data reflects visits by actual users over a reporting window. A lab test is a controlled diagnostic run. Device, network, caching and interactions can make their results differ. A page with no field data has insufficient measurements; it has not automatically passed or failed. Total Blocking Time is a lab diagnostic and must not be relabeled as INP.

Choose a repair from the evidence

Avoid applying every recommendation at once. An image compression change cannot explain a slow event handler, and a fast initial load cannot establish responsive checkout interactions.

Worked example: a product image arrives late

Suppose a product page has a late hero image while other resources finish early. Confirm that the image is the LCP element. Check whether it is discovered only after JavaScript runs or is incorrectly lazy loaded. Change discovery or loading priority, retain suitable image dimensions, then repeat the same lab setup. Finally, watch the relevant field trend when enough new visits have been collected. This is a diagnostic example, not a measured SearchBastion result.

Record the test conditions

Save URL, device profile, test time, release identifier and the observed bottleneck. Run comparable tests after the change and also exercise navigation, menus and purchase controls. Performance work should improve the experience users encounter; a score increase alone does not establish a ranking increase.

Use Speed Checker for an initial investigation and consult Web Vitals for the metric definitions.