What is a rage click?

A rage click is a rapid, repeated click or tap on the same element, usually within a second or two, made by a user who expected a response and didn't get one. It is one of the clearest behavioral signals of frustration available in product data, because it captures the exact moment a user's expectation and the product's response diverge.

What causes a rage click

Rage clicks typically point to one of three problems:

1. A broken or unresponsive element: a button that doesn't fire, a link that 404s, a form that silently fails to submit.

2. An element that looks clickable but isn't: styled text or an icon a user assumes is interactive.

3. A slow-loading action with no feedback state: the click registered, but nothing on screen told the user that, so they clicked again.

Distinguishing between these three matters, because the fix is different in each case: the first is an engineering bug, the second is a UI clarity problem, and the third is often solved with a loading state or a piece of microcopy confirming the action was received.

How rage clicks are detected

Session recording tools detect rage clicks automatically by flagging click clusters: multiple clicks on the same coordinates within a short time window. That turns a vague "users seem frustrated somewhere in the app" concern, usually inferred indirectly from drop-off in a funnel analysis, into a specific screen, element, and moment worth watching a recording of.

Why rage clicks matter more in onboarding

A rage click during onboarding carries more weight than one deep in a feature a user has already adopted, because new users have the least patience and the least context for working around a broken flow. Teams that monitor rage clicks specifically within onboarding flows tend to catch user friction that would otherwise only show up later as a drop in activation rate.