Core Web Vitals and INP explained

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content loads (LCP), how quickly the page responds to a tap or click (INP) and how much the layout jumps around (CLS). A page passes when at least 75% of visits meet the "good" threshold for all three.
Interaction to Next Paint (INP) replaced First Input Delay (FID) as the responsiveness metric on 12 March 2024. Any guide or audit still reporting FID is out of date.
The three Core Web Vitals and their thresholds
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | Time until the largest image or text block is visible | 2.5 seconds or less | 2.5 to 4 seconds | Over 4 seconds |
| Interaction to Next Paint (INP) | Time from a click, tap or key press to the next visual update | 200 milliseconds or less | 200 to 500 milliseconds | Over 500 milliseconds |
| Cumulative Layout Shift (CLS) | How much visible content moves unexpectedly | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
Google assesses each metric at the 75th percentile of page loads, separately for mobile and desktop (web.dev). The 75th percentile means your slower visitors count: a page that loads in 1.5 seconds on office broadband but 5 seconds on a mid-range phone on 4G fails.
Do Core Web Vitals affect rankings?
Yes, but as one signal among many. Google's ranking systems use Core Web Vitals as part of page experience, and relevance still outweighs speed. A fast page that does not answer the search will not outrank a slower page that does.
The larger effect is on the people who arrive. Slow, jumpy pages lose visitors before they read anything, and that shows up in enquiries and sales long before it shows up in rankings. The cost of a slow website is usually felt in conversion rate first.
How to test your Core Web Vitals
There are two kinds of data, and they answer different questions.
| Data type | Where to find it | What it tells you |
|---|---|---|
| Field data (real users) | Search Console Core Web Vitals report, PageSpeed Insights "Discover what your real users are experiencing", Chrome UX Report | Whether real visitors pass, over the last 28 days |
| Lab data (simulated) | PageSpeed Insights diagnostics, Lighthouse, Chrome DevTools Performance panel | Why a page is slow, under fixed test conditions |
Google ranks on field data. Use the lab tools to find causes, then wait for the 28 day field data to confirm a fix worked. Smaller sites without enough traffic for field data only get lab results, so test on a throttled mobile profile, not your desktop.
INP is hard to reproduce in a lab test because it depends on what people actually click. The Chrome DevTools Performance panel shows live INP as you use the page, and the free web-vitals JavaScript library can send real INP values from your visitors into GA4.
How to improve LCP
LCP is usually an image: the hero photo, a banner or a product shot. Fix that element first.
- Load the LCP image early. Do not lazy load it. Add
fetchpriority="high"so the browser fetches it before anything else. - Serve the right size. A 2,400 pixel hero image on a 390 pixel phone screen wastes most of the download. Use responsive
srcsetsizes. - Use modern formats. WebP and AVIF files are typically much smaller than JPEG at the same visual quality.
- Cut server response time. Slow hosting, no page caching or a heavy database query delays everything after it. A CDN such as Cloudflare serves cached pages from a location near the visitor.
- Remove render blocking files. Large CSS files and scripts in the page head hold back the first paint. Web fonts loaded without
font-display: swapcan hide text until they arrive. - Do not hide the hero. Fade-in animations that start the main heading or image at zero opacity delay LCP until the animation runs.
How to improve INP
Every interaction has three parts: the delay before the browser starts handling it, the time your code takes to run and the time to paint the result. Google's INP guidance covers each.
- Reduce JavaScript on load. Long tasks while the page is loading delay the first interactions. Remove unused scripts and defer what is not needed immediately.
- Break up long tasks. Code that runs for hundreds of milliseconds blocks the main thread. Split it into smaller tasks and yield between them so the browser can paint.
- Update the screen first. In a click handler, run only what is needed for the visible change. Saving, logging and analytics calls can wait until after the paint.
- Audit third party scripts. Chat widgets, tag managers loading many tags, heatmaps and ad pixels often cause the worst INP. Each one should earn its place. Load non-essential ones after interaction or consent.
- Keep the DOM small. Pages with thousands of elements take longer to re-render. Page builders and mega menus are common causes.
- Avoid layout thrashing. Reading an element's size straight after changing its style forces the browser to recalculate layout mid-task.
On WordPress, INP problems usually trace back to a heavy page builder, several plugins each loading their own scripts on every page and a stack of marketing tags. WordPress speed optimisation starts with removing what the site does not need before tuning what it does.
How to improve CLS
Layout shift happens when something appears and pushes content down after the visitor has started reading.
- Set width and height on images and video so the browser reserves the space before they load.
- Reserve space for embeds, ads and banners. Cookie banners, promo bars and embedded reviews that insert themselves above content are frequent causes.
- Load fonts carefully. A fallback font with very different sizing causes text to reflow when the web font arrives. Preload key fonts and use size-adjusted fallbacks.
- Animate with transform. Animations that change
top,heightormarginshift layout. CSStransformdoes not.
A practical order of work
- Open the Search Console Core Web Vitals report and note which page groups fail, and on which metric.
- Fix shared templates first. One fix to the product template improves every product page.
- Start with LCP on mobile, as it fails most often, then CLS, then INP.
- Test each change in PageSpeed Insights, then let 28 days of field data confirm it.
- Check again after any new plugin, tag or design change. Most regressions come from additions, not code changes.
Core Web Vitals are not a one-off project. A site that passes today can fail next month after a new chat widget or tracking tag goes in, so build a check into your release process.
If your pages are failing and you cannot see why, Google PageSpeed optimisation covers the diagnosis and the fixes.
Further Reading
View All PostsView All PostsStatistics that Define Atomic
Impressions for our Clients
Conversions across SEO, PPC & Social for our Clients
Average ROAS across our 100+ Global Clients on SEO, PPC & Social









