Poor Interaction to Next Paint (INP)

What This Means

The page's Interaction to Next Paint — measuring the time from any user interaction (click, tap, key press) to the next visual update — is in the "Poor" range (above 500ms). Google considers INP below 200ms "Good" and above 500ms "Poor". INP replaced FID as a Core Web Vital in 2024.

Why It Matters for SEO

INP measures responsiveness — when a user clicks a button, how quickly does the page visually respond? A high INP makes pages feel laggy and unresponsive. For interactive pages (those with forms, filters, accordions, or any JavaScript-driven interactions), poor INP directly damages the user experience.

Poor INP is almost always caused by JavaScript that runs too long on the main thread, blocking the browser from painting the response to the user's interaction. This is common on pages with heavy JavaScript frameworks, unoptimized event handlers, or excessive JavaScript execution on every user input.

What the Platform Checks

Measures INP score via performance data (field data from CrUX or lab measurements). Fires when INP is in the "Poor" band (>500ms).

How to Fix It

• Identify long tasks: Use browser DevTools Performance panel to find JavaScript tasks exceeding 50ms during interactions.
• Defer non-critical JavaScript: Code that doesn't need to run at interaction time should be moved to run after.
• Break up long tasks: Use scheduler.yield() or setTimeout to yield to the browser between heavy computation steps.
• Optimize event handlers: Review event listener code for expensive DOM operations, complex layout triggers, or synchronous data processing.
• Reduce JavaScript bundle size: Smaller bundles mean less JavaScript to parse and execute on interaction.