---
title: "Reduce INP to under 200 milliseconds"
description: "Interaction to Next Paint measures how quickly the page responds to input, reported at p75. A good value is under 200 ms. Find the slowest interactions in the Performance panel, then split long tasks, defer third-party scripts, reduce hydration cost and trim DOM size."
url: "https://seo-mcp.io/t/reduce-inp-to-under-200-milliseconds"
---

# Reduce INP to under 200 milliseconds

Interaction to Next Paint measures how quickly the page responds to input, reported at p75. A good value is under 200 ms. Find the slowest interactions in the Performance panel, then split long tasks, defer third-party scripts, reduce hydration cost and trim DOM size.

## Prerequisites

- Field data access
- Access to JavaScript bundles and third-party tags

## Steps

1. **Find the worst interactions** — In the Performance panel, record a session with clicks and typing, then open the Interactions track. Sort by duration and note input, processing and presentation delay.
   Check: The three slowest interactions are listed with their phase breakdown.
2. **Break up long tasks and defer scripts** — Move non-urgent work out of event handlers, yield to the main thread between chunks, and load analytics and chat widgets only after interaction or idle time.
   Check: The trace shows no task over 50 ms during the previously slow interaction.
3. **Confirm in the field** — Deploy and compare the p75 INP for the template over four-week windows in the Core Web Vitals report.
   Check: Field p75 INP is 200 milliseconds or less.

## Source

@seo-mcp on 2026-10-19: https://web.dev/articles/inp

Canonical: https://seo-mcp.io/t/reduce-inp-to-under-200-milliseconds