Skip to main content

INP by rage clicks

INP by rage clicks without noise

Vasil Dachev avatar
Written by Vasil Dachev
Updated over 2 months ago


What is INP by rage clicks

INP by rage clicks shows how Interaction to Next Paint (INP) differs for sessions where users perform rage clicks compared to those without them.

A rage click occurs when a user rapidly clicks multiple times on the same element within a short timeframe — usually out of frustration. This often means they expected the page to respond, but either nothing happened or it was too slow to react.

This breakdown helps you determine whether poor responsiveness (high INP) is a driver of rage-click behavior. If interactions take too long to trigger a visible response, users may repeatedly click, assuming the site is broken.


INP by rage clicks sample


Should you worry

In a healthy view, INP values for rage click sessions look similar to non-rage click sessions. Rage clicks may still happen, but they’re usually UX-related (like unclear feedback) rather than responsiveness problems.

A healthy setup typically shows:

  • INP consistently below 200ms in both groups.

  • Immediate visual feedback for clicks, taps, and inputs.

  • Clear affordances (buttons look clickable, disabled states are obvious).

If INP remains fast, rage clicks are more likely design-related than performance-driven.

Unhealthy INP by rage clicks

If rage click sessions consistently show higher INP values, responsiveness issues are frustrating users into clicking repeatedly.

Common causes include:

  • Slow button or link responses due to heavy JavaScript execution.

  • Input fields lagging before updating visually.

  • API calls blocking UI updates, making clicks feel ignored.

  • Main thread congestion delaying feedback.

Here, poor INP directly fuels rage clicks by making the page feel unresponsive.

Resolving unhealthy INP by rage clicks

Go-to action plan to resolve an unhealthy INP by rage clicks:

  1. Ask Uxi to analyze your INP by rage clicks values and suggest improvements.

  2. Use Filters to compare rage click sessions by device, country, or traffic source.

  3. Simulate INP of the suspected breakdown to see if fixing it will resolve the INP by rage clicks. If yes, this is where the resolution focus should be.

  4. Use an automated INP optimization tool like INProve to improve your INP by rage clicks values.

  5. 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.

Did this answer your question?