Event Timing and INP
Measures how long clicks, taps and key presses take to produce the next frame.
In one line
Can time how fast the page responds to your taps, clicks and key presses
Measures how long clicks, taps and key presses take to produce the next frame.
Records each interaction's input delay, processing time and presentation delay (8 ms granularity) so sites can compute Interaction to Next Paint (INP), and also learns when and how fast people interact.
What it can and can't do
What the user does: You tap, click or press a key on the page
It can
- Measure delay from each tap or key press to the next screen update
- Report the slowest responses to the site owner
- Learn if your device is slow or busy
It cannot
- Record what you typed
- Get exact times, since they are rounded to about 8 ms
- Work in Safari, where it is limited or partial
- Ask permission first
How it differs between platforms: Chrome and Edge fully support it. Firefox and Safari have limited or no support.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 76 | 2019-07-30 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Not supported | Not available | Not listed | :Event Timing in development |
| Safari | Partial | 26.2 | 2025-12-12 | :Behind flag or in preview |
| Safari on iPhone | Partial | 26.2 | 2025-12-12 | :Behind flag or in preview |
| Chrome on Android | Supported | 76 | 2019-07-30 | None |
| Samsung Internet | Supported | 12.0 | 2020-06-19 | None |
How a site asks for it
| API | PerformanceObserver type 'event' and 'first-input'; performance.interactionCount |
| Browser compat keys | api.PerformanceEventTiming |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Observe event entries with durationThreshold
- Group by interactionId
- Compute worst or 98th percentile
Data you get
What comes back: Entries with startTime, processingStart, duration (rounded to 8 ms)
Shape: event
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
duration | integer | ms | 16 to 10000 | 8 ms rounding |
interactionId | integer | None | 0 to unbounded | exact |
Technical limits
- Doesn't expose key identity or pointer coordinates
- 8 ms rounding limits fine timing
The story
What it is
Browsers measure how long it takes between a click or key press and the next screen update.
For you
You never see the measurement. You just feel it as a page that reacts quickly or one that feels stuck. Slow pages lose visitors and rank lower in Google search.
For makers
INP is one of Google's Core Web Vitals, so it affects search ranking and ad revenue. Teams measure it from real visitors, and fix slow scripts. Real time apps use it to make sure buttons feel instant.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A retailer measures how long an Add to cart tap takes to show, and fixes scripts that slow it down. | Shopify stores |
| games | A browser game checks that button taps and key presses show on screen in time, to avoid feeling laggy. | None named |
| creative | Figma and web editors measure how fast clicks, drags and menus respond on huge files. | Figma |
| news | A news site finds that a slow cookie banner makes taps feel stuck, and fixes it. | None named |
| ads | An ad tech vendor tests that its tags do not make taps slow, since publishers punish slow scripts. | None named |
| analytics | Real user monitoring tools collect INP from visitors and show it in a dashboard. | Datadog RUM, SpeedCurve, Chrome UX Report |
| productivity | A web spreadsheet or document app measures key press delay to keep typing smooth. | Google Docs, Notion |
Risks
- Slow scores hurt ranking
- Reports go to analytics vendors
What the platform says
- web.dev: Interaction to Next Paint (INP). Google says INP measures how fast a page responds to your clicks, taps and key presses.
- MDN: Event Timing API. Describes how pages can measure how long interactions take to be handled and painted.
Good uses and abuse
Legitimate uses
- Core Web Vitals reporting
Known abuse
- Interaction timing patterns for bot detection
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2024-03, Chrome: INP replaces FID as a Core Web Vital
- 2024-09, Chrome: INP in Search ranking signals
Related capabilities
Related
- Long Animation Frames (LoAF). Can see slow page frames and which scripts caused them
- Keystroke dynamics. Can time your key presses to learn your typing rhythm
Sources
How well checked: Based on official documentation.