What Are Core Web Vitals and How Should a Business Use Them?
A business-focused guide to LCP, INP and CLS, including field versus lab data and how to prioritise website performance work.
Core Web Vitals are experience signals that help answer how quickly primary content appears, how promptly a page responds and whether the layout moves in disruptive ways. They are useful when connected to business goals, not treated as a replacement for content quality or conversion measurement.
What the three main metrics describe
- LCP (Largest Contentful Paint) measures when the largest visible content element is rendered
- INP (Interaction to Next Paint) reflects responsiveness to clicks, taps and keyboard input across the visit
- CLS (Cumulative Layout Shift) measures unexpected layout movement that was not caused by the user
Field data and lab tests answer different questions
Field data reflects real devices, networks and behaviour over time. Lab tools use a controlled simulation that makes causes easier to diagnose. A site can score well in Lighthouse while real users still encounter slow pages in a particular template, market or lower-powered device, so both views matter.
Start with templates and journeys that matter to the business
Do not review only the homepage. Group results by template—services, articles, case studies and forms—and prioritise pages that contribute meaningful organic traffic, enquiries or revenue. Fixing a shared component often creates more value than tuning URLs one by one.
Common causes worth investigating
- LCP: an oversized hero image, slow server response, or blocking CSS and fonts
- INP: long-running JavaScript, expensive event handlers or unnecessary third-party widgets
- CLS: images without dimensions, font swaps that change layout or banners inserted above content
Measure the result without chasing a single score
Record the baseline, deployment date, affected templates and any change in conversion or usability. Then allow field data to accumulate over its reporting window. A perfect score in one test matters less than a stable experience across the devices and journeys customers actually use.
Use Core Web Vitals to find and prioritise experience problems—not as a goal detached from users and business outcomes.
Separate lab diagnosis from field experience
| Metric | Meaning | Diagnostic use |
|---|---|---|
| LCP | Main content display time | Inspect server time, images and fonts |
| CLS | Unexpected layout movement | Reserve media/font/widget space |
| INP | Interaction responsiveness | Review handlers and long tasks in real journeys |
| Lighthouse TBT | Lab main-thread blocking during load | Use diagnostically; do not label it field INP |
Good Core Web Vitals targets are LCP at most 2.5 seconds, INP at most 200ms and CLS at most 0.1 at the 75th percentile, segmented by device. A local page without CDN scripts differs from production. Use the distinction to isolate causes rather than presenting local results as every visitor’s experience.
Preserve media and motion by reducing unnecessary work
Deliver images appropriate to display size and pixel density, reserve dimensions and prioritise only genuinely visible media. Pause offscreen animation. Preloading a required heading font can help, while preloading every weight competes for bandwidth. Keep static content out of unnecessary hydration and verify actual interactions afterwards.
Test the pages that support enquiries
| Page | What to check |
|---|---|
| Service | Read the offer, review proof and open LINE on mobile |
| Case study | Load initial imagery and open detailed screenshots |
| Guide | Read the article and follow relevant service links |
| Contact | Choose a channel and see the actual form state |
Compare before and after under the same device and test conditions, then review field data when sufficient real-user data exists. Lighthouse and TBT are diagnostic lab evidence; INP measures real interactions.
Measure SEO through actual LINE enquiries →

