Performance

INP Checker

Interaction to Next Paint measures how quickly your page responds to user input. It replaced First Input Delay (FID) as a Core Web Vital in March 2024. Google's target is under 200ms. We'll also show Total Blocking Time, the lab-data proxy for INP.

Uses Google PageSpeed Insights — typically 10–30 seconds. Results are lab data; real-user numbers may differ.

What is an INP checker?

An INP checker measures Interaction to Next Paint — how fast your page responds to clicks, taps and key presses. This free INP test runs Google PageSpeed Insights so you can check INP on any URL.

Diagnose & fix poor responsiveness

A high interaction to next paint usually means the main thread is busy. Break up long JavaScript tasks, defer or drop heavy third-party scripts, and debounce expensive handlers. We surface Total Blocking Time so you can track the lab proxy as you optimize, then re-test.

What's a good INP?

Aim for 200ms or less. 200–500ms needs improvement; above 500ms is poor. INP is a Core Web Vital that replaced FID, so improving it helps users and rankings.

More Core Web Vitals tools

Check the rest: LCP Checker, CLS Checker, TTFB Checker, and the full Page Speed Test.

Frequently asked questions

An INP checker measures Interaction to Next Paint — how quickly a page responds to user input (clicks, taps, key presses). This free INP test runs Google PageSpeed Insights on any URL and also shows Total Blocking Time, the lab proxy for INP.
Google considers INP good at 200ms or less, needs-improvement up to 500ms, and poor above 500ms. INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.
Break up long JavaScript tasks, defer or remove unused third-party scripts, debounce expensive event handlers, and avoid heavy work on the main thread during interactions. Lowering Total Blocking Time usually improves INP.
Completely free and online, with no account required. It's part of WebsiteAuditTools' free suite of Core Web Vitals tools.