Understand LCP, INP and CLS, compare lab and field data, and prioritize practical mobile fixes for your most important business pages.
Core Web Vitals measure how quickly the main content appears, how responsive the page feels and how much its layout shifts. Start with your homepage, a service page and the page where customers enquire or pay. Test on mobile and prioritize issues that interrupt those journeys.
What are the three Core Web Vitals?
| Metric | What it measures | Good threshold |
|---|---|---|
| LCP | When the largest visible image or block of text is rendered. | 2.5 seconds or less |
| INP | How quickly the page updates visually after a typical click, tap or key interaction. | 200 milliseconds or less |
| CLS | How much visible content unexpectedly shifts during use. | 0.1 or less |
Google evaluates these thresholds at the 75th percentile of visits, with mobile and desktop assessed separately. See Google’s Web Vitals documentation for how each metric is calculated.
Why do PageSpeed Insights and a crawler show different numbers?
Field data comes from eligible real visits over time. A lab test runs a simulated visit with set device and network conditions and helps you reproduce an issue. A small site may have too little field data for an individual URL. Use lab results to guide testing and check the experience yourself on a phone. Google Search Console groups similar URLs in its Core Web Vitals report when it has enough field data. Google Search Central’s Core Web Vitals guide explains the distinction.
How do you fix a slow or unstable business page?
When LCP is slow, identify the actual LCP element in Lighthouse. If it is the hero image, resize it for the screen, compress it and make it available early. Keep lazy loading for images farther down the page. When the main element is text, check server response time, style sheets and how fonts load before changing images.
When INP is slow, reproduce the interaction customers use, such as opening the mobile menu or submitting a form. A heavy script can keep the browser busy and delay a response. Move unnecessary work out of the interaction and test any analytics, chat or other third-party script you add.
When CLS is high, reserve room for images, videos and embeds. Check whether a banner or widget pushes buttons down after load. If a lead form shows a message or error, reserve enough space for the feedback so the next control stays where the visitor expects it.
Test the customer action after every change
Suppose a clinic’s mobile page shows its service copy quickly but the appointment button jumps while a widget loads. Record the problem on a real phone, reserve space for the widget and retest the same page. Then follow the booking path through confirmation. Keep a short record of the page, change, lab result and whether the appointment worked.
Aim for a usable page before chasing a perfect tool score. Check your page with PageSpeed Insights, then use our SEO priority guide and website development services across India if you are planning a rebuild.