Question 1

What is a good INP score?

Accepted Answer

200 milliseconds or less at the 75th percentile of real users is good; 200–500ms needs improvement; over 500ms is poor.

Question 2

What's the difference between INP and FID?

Accepted Answer

FID measured only the input delay of the very first interaction. INP measures responsiveness across all interactions and includes processing and repaint time too, so it's a fuller—and harder—measure of how the page feels. INP replaced FID as a Core Web Vital in March 2024.

Question 3

Why is my INP fine in Lighthouse but failing in Search Console?

Accepted Answer

Lighthouse doesn't interact with the page, so it can't truly measure INP. Search Console uses real-user field data where people actually click and type. Diagnose INP with field data or by interacting with the page yourself in DevTools, not with a standard Lighthouse score.

Question 4

Does INP affect SEO rankings?

Accepted Answer

INP is part of Core Web Vitals, which act as a ranking tiebreaker between pages of similar relevance and authority—especially on mobile. Just as importantly, a responsive page feels better to use and converts better, so the work pays off beyond rankings.

Question 5

What usually causes high INP?

Accepted Answer

Too much JavaScript on the main thread: long tasks during load, heavy event handlers, and third-party scripts like chat widgets, tag managers, and A/B testing tools. Caching and CDNs won't help—the fixes are code-level.