LCP
Measures when the main visible element appears. Images, fonts, CSS and server response are common factors.
Before changing components or installing another plugin, it helps to identify which element produces the metric and on which pages. LCP, INP and CLS describe different problems and need different fixes.
Treating them as one score often leads to work that misses the real cause.
Measures when the main visible element appears. Images, fonts, CSS and server response are common factors.
Measures interaction latency. JavaScript, rendering and long tasks are often central.
Measures unexpected layout shifts. Missing dimensions, fonts and late content are common causes.
CrUX and Search Console describe aggregated real experiences, not one Lighthouse run.
A metric can be good on the homepage and poor on product or article pages.
Behavior can differ significantly between desktop and mobile and across network conditions.
We start from the failing metric and trace it back to the element or work that produces it.
Identify which templates or groups of URLs share the issue.
Use lab tests to reproduce the issue and field data to understand how often it happens.
LCP element, long task, font, banner, image or component shifting the layout.
Change the code or configuration causing the issue instead of applying a generic optimization.
Verify the result in the lab and allow field data enough time to reflect the change.
The checklist depends on the metric that is failing.
Core Web Vitals are useful because they point to degraded real experiences. The work is done when the cause is controlled, not when one test turns green.
Send the affected URLs and the data you are looking at. We can start from there.