Interaction to Next Paint: Crawl Audit check 73

Short answer: Interaction to Next Paint (INP) measures how long your page takes to react when someone taps, clicks or types. It's a Core Web Vital, and it replaced First Input Delay (FID) on 12 March 2024. Check 73 passes at 200ms or less, warns up to 500ms and fails above that.

What Crawl Audit checks

• Full report: real-user INP from the Chrome UX Report when your site has enough visitors. INP needs real people interacting, so without that data Crawl Audit falls back to a Lighthouse lab figure when one is available.
• Free check: an estimate based on how many external scripts the page loads (120ms plus 25ms per script). It's a rough signal, not a measurement.
• Pass: 200ms or less. Warning: up to 500ms. Fail: over 500ms.

What Google says

• web.dev: "INP observes the latency of all interactions a user has made with the page, and reports a single value which all (or nearly all) interactions were beneath."
• "Good INP values are 200 milliseconds or less. Poor values are greater than 500 milliseconds."
• "INP is the successor metric to First Input Delay (FID)." From 12 March 2024, "Interaction to Next Paint is now a stable Core Web Vital metric, replacing First Input Delay."

What slows it

• Long JavaScript tasks that keep the browser busy when someone taps. Total Blocking Time (check 76) is the lab measure that tends to move with INP.
• Heavy third-party scripts: chat widgets, trackers, ad tags (check 99).
• A very large page that's slow to redraw after each change (check 78).

Common fixes

• Remove scripts you don't need, and load the rest with defer or later.
• Break long tasks into smaller pieces, so the browser can respond in between.
• Show something straight away after a tap (a pressed state, a spinner), then do the slow work.

Sources

• web.dev, Interaction to Next Paint (INP) (updated 2 September 2025) and INP is officially a Core Web Vital (12 March 2024), checked 3 October 2026.