INP

How It Works

INP (Interaction to Next Paint) evaluates the time from when a user initiates an interaction (for example, clicking a button) to when the browser paints the next frame that reflects the result of that interaction. Unlike older interaction metrics that focused on a single first input, INP considers many interactions throughout a page visit and summarizes them to represent the overall responsiveness users experience.

The latency captured by INP typically includes input delay (waiting for the main thread to be free), event processing time (JavaScript handlers and framework work), and rendering time (style recalculation, layout, and paint). High INP often happens when long tasks block the main thread, heavy third-party scripts run during interactions, or the page performs expensive DOM updates. Improvements usually come from breaking up long JavaScript tasks, reducing script execution, deferring non-critical work, and optimizing rendering so the UI can update quickly after an input.

Why It Matters for Web Hosting

While INP is heavily influenced by front-end code, hosting choices can still affect it by shaping how quickly interactive pages become usable and how much work the browser must do after each action. Slow back-end responses can trigger extra client-side loading states, repeated re-renders, or large payloads that increase JavaScript parse and execution time, all of which can worsen interaction responsiveness. When comparing hosting plans, look for strong CPU performance, low-latency networking, HTTP/2 or HTTP/3 support, effective caching, and the ability to serve smaller, compressed assets. For dynamic sites, ensure the plan can handle peak concurrency without timeouts or queueing that forces the UI to wait for server results after clicks or form submissions.

Common Use Cases

• Evaluating real-user responsiveness for JavaScript-heavy sites (SPAs, dashboards, web apps)
• Diagnosing sluggish clicks, taps, and form interactions caused by main-thread blocking
• Comparing performance impact of third-party scripts (analytics, chat widgets, tag managers)
• Validating improvements from code splitting, lazy loading, and reducing long tasks
• Monitoring interaction quality after hosting changes, caching adjustments, or CDN configuration

INP vs TBT (Total Blocking Time)

INP is a field-focused metric that reflects how responsive a page feels during real user interactions, summarizing interaction latency across a visit. TBT is a lab metric that estimates how much time the main thread is blocked by long tasks during page load, typically measured in synthetic tests. TBT is useful for debugging and correlates with responsiveness, but it does not directly measure interaction outcomes in real sessions the way INP does.