A rage click occurs when a user clicks (or taps) the same spot multiple times in quick succession — a behavioral signal of frustration. The name comes from the interpretation that users who do this are "raging" at an unresponsive or confusing interface.
Session replay and analytics tools like Hotjar, FullStory, and Microsoft Clarity automatically detect and flag rage clicks, making them one of the most actionable signals in behavioral analytics.
What Rage Clicks Indicate
Rage clicks almost always signal one of these problems:
| Cause | Description |
|---|---|
| Broken element | A button or link that looks clickable but doesn't function |
| Slow response | A click triggers an action but takes too long to respond, prompting re-clicks |
| Visual bug | An element appears interactive (underlined text, button-like styling) but isn't |
| Unexpected behavior | A click does something other than what the user expected |
| Unmet CTA expectation | A button promises something the resulting page doesn't deliver |
How to Investigate Rage Clicks
- Identify the location — Use a rage click heatmap overlay to find where on the page they're concentrated
- Watch session recordings — Filter for sessions with rage clicks to observe actual behavior in context
- Check for technical errors — Use browser console logs and error tracking to identify JavaScript errors near the affected element
- Verify cross-device behavior — Rage clicks are especially common on mobile where tap targets are small or overlapping
Rage Clicks as a CRO Signal
High rage click rates on a page often predict high bounce rates and low conversion rates. Pages with concentrated rage click activity are strong candidates for CRO investigation.
Before running an A/B test on a page with rage clicks, fix the underlying UX issue first — you'll get cleaner test results and a baseline improvement without any experiment.