What is INP by browser
INP by browser shows the Interaction to Next Paint (INP) metric across different browsers (e.g. Chrome, Safari, Firefox). This lens helps you uncover which browsers cause your users to experience more input delay — the kind that makes a site feel slow, even if it technically isn’t.
The list includes only browsers that generated traffic to your website during the selected period.
INP measures the latency of user interactions like clicks, taps, and key presses — it reflects how fast the interface responds to users. When INP is high, your site feels laggy.
Healthy INP by browser sample
Should you worry
A healthy INP by browser lens is all green. It means your site responds to user input promptly across browsers. You might see small differences, but as long as none hit the yellow or red zone, you’re in good shape.
Unhealthy INP by browser sample
In the example below, Safari users experience a high INP — even though the rest of the experience is smooth. That’s a red flag. Sluggish interactions frustrate users and increase the likelihood of abandonment.
This can happen if:
Event listeners are delayed or too heavy on certain browsers.
Browser engines handle animations and DOM updates differently.
There are compatibility issues with third-party tools or UI libraries.
Resolving unhealthy INP by browser
Go-to action plan to resolve an unhealthy INP by browser:
Ask Uxi to analyze your INP by browser values and suggest improvements.
Use Filters to isolate the slow browser, then dig deeper using INP by page and INP by element to find the source of lag.
Simulate INP of the suspected lens to see if fixing it will resolve the INP by browser. If yes, this is where the resolution focus should be.
Use an automated INP optimization tool like INProve to improve your INP by browser values.
Once you’ve improved INP, set an alert to be the first to know if it starts worsening again.
Try it yourself
Discover how your website performs with real user data.