Core Web Vitals describe three parts of the visitor experience: when the main content appears, how quickly an interaction responds, and whether the layout shifts. They are useful for a business owner because each connects a technical measurement to something a visitor can feel.
Know the three current metrics
Google's Web Vitals reference defines these good thresholds at the 75th percentile, with mobile and desktop considered separately:
- Largest Contentful Paint (LCP): 2.5 seconds or less. This measures loading performance for the largest visible content element.
- Interaction to Next Paint (INP): 200 milliseconds or less. This measures responsiveness to interactions.
- Cumulative Layout Shift (CLS): 0.1 or less. This measures unexpected visual movement.
First Contentful Paint and Total Blocking Time are useful diagnostic metrics, but they are not members of that three-metric set. First Input Delay was replaced by INP in 2024.
Read field and lab data separately
Field data describes observed visits. A lab test runs under controlled conditions and helps investigate a problem. An ordinary Lighthouse page-load test does not interact like a real visitor, so its Total Blocking Time should not be reported as a measured INP result.
For a business review, ask your developer to label each number with its source and scope. Is the result for this URL or the whole origin? Is it mobile or desktop? Is it one run or a period of visits? If the report lacks sufficient field data, retain that limitation.
Give the developer a focused brief
Use a brief tied to one visitor task:
Page: the service booking page. Visitor task: read eligibility information and open the booking options. Observed problem: the main content is slow to appear on mobile. Evidence: attach the report with its date and conditions. Request: identify the delayed content and propose one measurable change. Acceptance: comparable post-change evidence plus a manual check that the booking controls still work.
The brief avoids telling the developer to “make the score 100.” It asks for an explanation, a correction, and evidence that the important interaction still works.
Match the investigation to the symptom
For slow main content, investigate when the browser discovers that content and what delays its delivery or rendering. For sluggish interactions, examine the actual action that feels slow rather than only the opening page load. For layout shifts, reproduce when content moves and identify the element that changed size or arrived late.
Do not assume the cause from the metric name. A visible delay may involve application behavior, an asset, or a third-party dependency. Preserve a baseline so the next measurement can evaluate the proposed correction.
Keep search expectations realistic
Google says Core Web Vitals are used by its ranking systems, but good scores do not guarantee top placement. They sit alongside other considerations, including useful content. See Google's Core Web Vitals and Search guidance.
Measure the visitor experience as its own outcome. If you also want to evaluate enquiries or sales, use your business analytics and a defined observation period rather than inferring a revenue change from a speed score.
For the hands-on test routine, follow how to run a website speed test. A free PageVital snapshot can provide a starting point for investigation.