Product tour · Epsilon Delta Gemini · Website monitoring
INP monitoring: find the script behind a slow click
Interaction splits Interaction to Next Paint into input delay, processing and presentation time, and names the scripts and elements responsible, so you know which click feels slow and why.
Interaction INP and what caused it
“Which script or element made that click slow?”
- Sample data
- Last 24 hrs
- All platforms
- m.example.com
- INP · P75
- 270 ms
- 66% good · 14% poor
- Input delay · P75
- 23 ms
- Processing · P75
- 71 ms
- Presentation · P75
- 67 ms
- Page views
- 45,347
- Interactions
- 373,467
- 3% poor
00:0004:0008:0012:0016:0020:00
Top culprit scripts
ranked by presence in poor interactionsSlowest target elements
p75 duration · click to filterSample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.
What you can see on Interaction
- INP p75 with its three phases
- Culprit scripts, ranked
- Target elements for each interaction
- Your field INP compared with CrUX
Questions about Interaction
What is a good INP?
200 milliseconds or less is good. Over 500 ms is poor.
What did INP replace?
INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.
Last updated 6 Nov 2026 · Reviewed by [Name], [Role]