Skip to Content
Platform.Ontology

Event Timing and INP

Measures how long clicks, taps and key presses take to produce the next frame.

Gets silentlySpeed and timingPerformance APIWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported762019-07-30None
EdgeSupported792020-01-15None
FirefoxNot supportedNot availableNot listed:Event Timing in development
SafariPartial26.22025-12-12:Behind flag or in preview
Safari on iPhonePartial26.22025-12-12:Behind flag or in preview
Chrome on AndroidSupported762019-07-30None
Samsung InternetSupported12.02020-06-19None

How a site asks for it

APIPerformanceObserver type 'event' and 'first-input'; performance.interactionCount
Browser compat keysapi.PerformanceEventTiming
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Observe event entries with durationThreshold
  2. Group by interactionId
  3. Compute worst or 98th percentile

Data you get

What comes back: Entries with startTime, processingStart, duration (rounded to 8 ms)
Shape: event

FieldTypeUnitRangePrecision
durationintegerms16 to 100008 ms rounding
interactionIdintegerNone0 to unboundedexact

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

TypeExampleApps
shoppingA retailer measures how long an Add to cart tap takes to show, and fixes scripts that slow it down.Shopify stores
gamesA browser game checks that button taps and key presses show on screen in time, to avoid feeling laggy.None named
creativeFigma and web editors measure how fast clicks, drags and menus respond on huge files.Figma
newsA news site finds that a slow cookie banner makes taps feel stuck, and fixes it.None named
adsAn ad tech vendor tests that its tags do not make taps slow, since publishers punish slow scripts.None named
analyticsReal user monitoring tools collect INP from visitors and show it in a dashboard.Datadog RUM, SpeedCurve, Chrome UX Report
productivityA 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

Good uses and abuse

Legitimate uses

  • Core Web Vitals reporting

Known abuse

  • Interaction timing patterns for bot detection

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits2Rough identifying entropy, when known

History

  • 2024-03, Chrome: INP replaces FID as a Core Web Vital
  • 2024-09, Chrome: INP in Search ranking signals

Sources

How well checked: Based on official documentation.

On this page