Google quietly changed how it grades site speed in 2024, and most small business sites still haven't caught up. INP (Interaction to Next Paint) is now a full Core Web Vital, and unlike the metric it replaced, it doesn't forgive a sluggish click three scrolls into the page. Here's what changed, why it's tripping up sites that "passed" the old test, and what actually fixes it.
What INP Actually Measures
INP measures how long your page takes to visually respond to every interaction a visitor makes — every click, tap, and keypress, for the entire time they're on the page. It replaced FID (First Input Delay) as an official Core Web Vital in March 2024. FID only scored the very first interaction, which meant a site could load fast, respond instantly to that first click, and still feel broken on the fourth or fifth one. INP closes that loophole.
Why So Many Sites Are Failing It Without Knowing
Most site owners last checked their Core Web Vitals when FID was the standard, saw a green score, and never looked again. INP scores the whole session, so a mega menu that freezes for half a second, a mobile filter panel that lags on tap, or a chat widget that hijacks the main thread when it loads — all invisible to FID — now drag the score down. A site can look fast on a cold load and still fail INP the moment a real visitor starts clicking around.
What counts as good: under 200ms is good, 200-500ms needs improvement, and anything over 500ms is poor — measured at the 75th percentile of real visitor interactions, not a single lab test.
How to Check Your Score
PageSpeed Insights and Google Search Console's Core Web Vitals report both now surface INP using real-world Chrome UX Report data, not just a lab simulation. Search Console is the more useful of the two — it groups your actual URLs into Good, Needs Improvement, and Poor, so you can see which templates (product pages, blog posts, the homepage) are dragging the score down instead of guessing from one test run.
The Usual Culprits
Third-party scripts are the single biggest offender — chat widgets, ad tags, review-platform embeds, and tracking pixels that each grab the main thread the moment they load. Long JavaScript tasks are the second: any script that runs for more than 50ms without yielding blocks the browser from responding to a click that happens mid-task. Heavy work stuffed inside click or input handlers — re-rendering a whole component tree for a single toggle — is the third.
Fixes That Actually Move the Needle
Lazy-load or defer third-party scripts so they load after the page is interactive, not before. Break long JavaScript tasks into smaller chunks so the browser gets a chance to breathe between them. Debounce expensive handlers (search-as-you-type, live filtering) instead of running them on every keystroke. Audit which third-party embeds you actually need — a lot of sites are running two analytics tools and three marketing pixels nobody's looked at in a year.
Does INP Actually Affect Rankings?
Core Web Vitals are a confirmed ranking signal, and INP is now one of the three that make up that signal alongside LCP and CLS. It's a smaller factor than content relevance, but on competitive local-service and e-commerce keywords, where several sites are otherwise similarly optimized, a Poor INP score is a real, avoidable disadvantage — and a slow, laggy site loses visitors and sales regardless of what it does to your ranking.
The Bottom Line
A green Core Web Vitals score from a year ago doesn't mean anything today if it was measured before INP became a Vital. Pull your current Search Console report, find which page templates are Poor or Needs Improvement, and start with the third-party scripts — that's where most sites recover the most ground the fastest.
Not sure what's slowing your site down?
We'll run a free Core Web Vitals audit, show you exactly which scripts are hurting your INP score, and quote the fix.