Rage Clicks: What They Are and Why Most Are False Alarms

A screening test catches about eight cancers in ten and wrongly flags about one healthy woman in ten, in a group where roughly one woman in a hundred has the disease. A woman tests positive. Her chance of having cancer is under one in ten. When David Eddy put this problem to physicians, in his chapter of Judgment Under Uncertainty (Cambridge University Press, 1982), most answered around three in four.

Rage clicks are rapid, repeated clicks or taps on the same spot of a page within a second or two, which replay and analytics tools such as Microsoft Clarity, Hotjar, FullStory and PostHog flag automatically as visitor frustration. The threshold differs by vendor, so two tools can report different counts for the same session.

Why Rage Clicks Matter for B2B SaaS

A rage click is a positive test result. Run Eddy's numbers on a thousand women: ten have the disease and the test catches eight, while it flags about 99 of the other 990. Eight of 107 alarms are real.

The usual reading is that a rage-click report maps your worst conversion friction: sort by count, fix from the top. Our claim, which your own data could prove wrong, is that friction bad enough to lose the visitor is rarer than the flag. We expect most flagged sessions to be somebody waiting on a slow button, double-clicking out of habit, tapping a screenshot expecting it to zoom, or selecting a line to copy, and many of them go on to sign up.

The costlier visitor produces no click at all. They reach a field asking for a phone number and close the tab. The session recordings piece argued that opposite states of mind leave near-identical traces; this visitor leaves no trace to read.

How to Measure Rage Clicks

The reported rate is sessions with at least one rage click divided by all sessions on the page, comparable only within one tool. It exists to ration viewing. A product manager wrote on r/ProductManagement in June: "The hardest bit for me is reviewing those manual recordings. With thousands of sessions each week, we barely get to look at 1-2% of them."

So measure the flag's base rate. Take twenty flagged sessions from one page and put each in a bucket:

1. Waiting on something slow.
2. Clicking something that looks clickable and is not.
3. A real block that ended the visit.

Then count how many of the twenty converted anyway. Only the third bucket is what the flag implies.

Rage Clicks vs Dead Clicks

A dead click is one click that changes nothing. A rage click is several fast clicks on the same spot. The two overlap in bucket two: a visitor clicks something that only looks clickable, nothing happens, and they try again.

What Causes Rage Clicks, and What to Fix

Fix bucket two first: a fake-looking button is cheap to change, and it is what rage clicks reliably find. Bucket one is a performance ticket. For bucket three, look at what the page asked for just before the clicking started.

Our own method has the opposite gap. A Nudgent audit reads the page and never watches a visitor (the Clarity comparison says so), so it cannot see a rage click. It can ask whether the flagged element looks clickable, or asks for something the page has not earned.

"Session recordings show what people do; they don't tell you what evidence they were still looking for," one r/GrowthHacking commenter wrote in August. Of everyone who left your signup page without clicking anything, what does your replay tool tell you about why?

Related Terms

• Conversion friction
• Audit methodology
• Form abandonment