INP and Core Web Vitals: How Site Speed Affects Sales
How Google's Core Web Vitals and the INP metric shape both search rankings and whether a visitor completes a purchase or booking.
rabbitclip teamPublished: 6 min read
Short answer
Core Web Vitals are three metrics Google uses to measure how a page loads, how visually stable it is, and how quickly it responds to interaction (LCP, CLS, INP); together they act as both a ranking signal and a direct indicator of whether a visitor stays on the page. INP (Interaction to Next Paint) replaced the FID metric in March 2024 and measures the time between a click or tap and the screen actually responding.
These metrics can sound like an engineering detail, but the outcome is concrete: on a page that loads slowly or responds late to a click, a visitor leaves before filling in a form or adding something to the basket.
This piece covers what the three metrics measure, why they matter for different types of business, and where to start.
What Core Web Vitals actually measure
Core Web Vitals is a set of measurements Google uses to summarise a page's user experience across three separate metrics: LCP (Largest Contentful Paint) measures how long the main content takes to appear, CLS (Cumulative Layout Shift) measures how much elements move around while the page loads, and INP (Interaction to Next Paint) measures how quickly the screen responds after a click or tap.
Together they answer a simple question: does the page feel fast? If content appears late (high LCP), a button jumps while someone is reading (high CLS), or the screen seems to freeze after a menu tap (high INP), the experience counts as poor.
Why INP replaced FID
FID (First Input Delay) only measured the delay before the very first click; it ignored every interaction that happened after the page had loaded. INP measures every click, tap and keypress for as long as the page stays open and reports the worst one, which reflects real usage far more accurately.
Take a booking page where the time slot list freezes for a moment after a visitor picks a date: FID would never have caught that, but INP shows it directly. Under web.dev's published thresholds, an INP under 200 milliseconds is considered good, and anything over 500 milliseconds is considered poor. The slower the response, the sooner a visitor gives up.
How site speed affects sales
A slow page means a visitor leaves before finishing what they came to do. Picture a spa chain's booking form: if picking a date lags by a second on every tap, the visitor may just ring up instead, or check a competitor.
The same applies to a manufacturer's quote request form. If the confirmation screen takes too long to appear after submission, the user is not sure whether it went through, taps again, and sometimes sends the same request twice, or gives up and leaves without sending it at all.
The risk here is not only search ranking; it is the number of completed transactions.
Where to start: measurement
The first step is measuring. Google's PageSpeed Insights and the Core Web Vitals report in Search Console are built on real visitor data (field data), which, unlike a lab test, shows how the site actually performs on visitors' own devices and connections.
A speed effort that skips measurement usually targets the wrong thing. Shrinking one image might do nothing if the real culprit is a third-party chat widget slowing down the whole page.
Measurement works better as a regular habit than a one-off report; if the same report is not checked again after an update or a new feature ships, a regression can go unnoticed for weeks.
- Check current LCP, CLS and INP figures in PageSpeed Insights
- Read the Core Web Vitals report in Search Console for real visitor data
- Assess mobile and desktop separately; mobile is usually the more critical one
- Test third-party scripts (adverts, chat widgets, analytics tools) on their own
Which businesses feel it most
Site speed matters everywhere, but in some sectors it hits revenue directly. On an e-commerce site, a slow-loading basket page is a lost sale; for a business built around bookings or applications, a delayed form is a lost customer.
On a brochure-style corporate site with a handful of pages, speed still matters, but its effect runs more through brand perception; a visitor may simply find a slow site less trustworthy.
Practical ways to improve INP
Improving an INP score usually comes down to breaking up long JavaScript tasks that keep the browser's main thread busy. If the code running right after a click takes too long, the browser waits for it to finish before updating the screen; the user feels that wait as a freeze.
Third-party scripts, a live chat widget, advertising tags, analytics tools, are often the real source of a poor INP, since they share the same main thread as the page's own code. Delaying a script so it only runs a few seconds after the page loads reduces freezing on those first interactions.
If a manufacturer's product filter recalculates the entire list on every option clicked, breaking that calculation into smaller chunks that leave the browser room to breathe fixes it; the technical detail sits with the developer, but what a manager needs to know is that this fix is measurable and rarely needs a full rewrite.
These fixes do not need doing all at once; starting with the three or four scripts causing the biggest impact is a more realistic path than a months-long rewrite.
Core Web Vitals can look like a technical report, but the outcome is a business one: a page that loads fast and responds instantly to a click carries more visitors through to a completed booking, purchase or form. In a discovery call with rabbitclip, the site's real visitor data gets reviewed together, and the point worth fixing first becomes clear. Tracking all three together usually makes it obvious which page deserves attention first.
FAQ
What counts as a good INP score?
Under web.dev's published thresholds, under 200 milliseconds is good and over 500 milliseconds is poor.
Do Core Web Vitals decide rankings on their own?
No, they do not override content quality, but they are one of Google's page experience signals and can be the deciding factor between two otherwise similar pages.
Does mobile or desktop matter more?
Search Console reports the two separately; since most corporate sites see a higher share of mobile traffic, mobile data usually takes priority.
How long does a speed fix take?
It depends on the cause; an image fix can take days, while third-party script issues can take longer to resolve.
Do LCP and CLS matter as much as INP?
Yes, all three are assessed together; focusing on just one risks missing problems in the others.
