Rage clicks: what they are and how founders who build with a coding agent fix them
A rage click is a burst of fast clicks on one spot, because nothing answered the first one. For founders who build with a coding agent, here is the exact rule UserProof counts by. It needs 3 or more clicks on one element, each under 1 second apart and within 30 pixels of the first, and no visible response in the first second. Read November 14, 2026.
Our number: a rage click needs an element that did not answer. When we scanned 493 YC startup homepages on October 28, 2026, 33 of them (6.7%) had at least one dead click. Across the 33 the scan logged 49 dead clicks in all, and 43 of those were on real buttons and links. That scan counted dead clicks, not rage clicks, so it gives no rage click rate and we do not quote one.
How do the main tools define a rage click?
Only PostHog and UserProof publish a number. The other five describe a rage click in words. We read each vendor's own page on November 14, 2026; the date in the last column is the date the page itself shows.
| Tool | How it describes and flags one | Number published | Page and its date |
|---|---|---|---|
| UserProof Ours | Counted from recorded clicks by fixed rules; becomes a finding when enough sessions do it (rule below) | 3 or more clicks, each under 1,000 ms apart, within 30 px of the first | Findings engine, read Nov 14, 2026 |
| Microsoft Clarity | "The user clicks multiple times in a clustered area in rapid succession"; each clustered click is marked and the page view or session is flagged | None | Semantic metrics docs, dated Dec 1, 2025 |
| PostHog | "A rage click is captured when a user clicks three times in rapid succession in roughly the same spot"; event $rageclick; the thresholds are configurable | 3 clicks, each within 30 pixels and 1 second of the previous one | Autocapture docs, no date shown |
| FullStory | "Rage Clicks are logged when end users click multiple times rapidly in the same area" | None | Blog post, Mar 4, 2022 |
| Hotjar (Contentsquare) | A rage click map in heatmaps, and a "click recurrence" filter in Session Replay for repeated clicking | None | Contentsquare blog, updated Nov 9, 2025 |
| LogRocket | "A burst of rapid, repeated clicks on the same element"; on mobile, repeated taps in a small area | None | Signals docs, updated Oct 6, 2026 |
| Mouseflow | Flagged automatically as part of Friction Events and the Friction Score | None | Blog post, Dec 19, 2024 |
The units differ even where numbers exist. PostHog measures each click against the one before it. UserProof measures the distance against the first click of the burst, as the horizontal gap plus the vertical gap, so the allowed area is a diamond, not a circle. Hotjar's own rage click page now redirects to the Contentsquare post cited above. Full list of tools that flag them: best rage click and dead click detection tools.
What is UserProof's exact rule for a rage click?
UserProof counts a rage click when 3 or more clicks land on the same element and each click comes less than 1,000 ms after the one before it. The rule is in our findings engine (src/lib/engine/findings.mjs), read November 14, 2026. A burst counts only if all of this holds:
- Every click in the burst hits the same element on the same page.
- Each click is less than 1,000 ms after the previous one.
- The horizontal gap plus the vertical gap from the first click of the burst stays under 30 pixels.
- The first click got no visible response within 1 second, or none at all.
- Clicks on input, textarea, select, option and label elements, because repeated clicks there select text. Clicks from older recorder versions inside native controls are skipped too, because their effect cannot be judged.
- A burst becomes a finding only when it happens in at least 10 sessions, from at least 3 different visitors, and in at least 1% of that page's sessions.
Dead clicks, errors on click and slow responses have their own rules, listed on the dead click and rage click feature page.
What causes rage clicks?
A visitor clicks again when the first click gets no answer. In the dead click scan, the elements that gave no answer were mostly real controls, which is where a second and third click would come from. We did not observe visitors rage-clicking them; the scan clicked each element once itself.
- A button or link that does nothing. Our October 28, 2026 scan logged 49 dead clicks in all: 43 were on real buttons, links or menus, and 6 were on cards, rows or icons that only looked clickable.
- A menu that opens only on hover. 17 of those dead clicks sat in the header, nav or footer, most of them dropdown buttons such as Product and Solutions. On a phone or keyboard the click opens nothing.
- A slow response. 7 of the 493 homepages had a click that answered after more than 2 seconds. With no spinner, the visitor clicks again.
- An error on click. 2 of the 493 homepages had a click that threw an error from the site's own code.
How do you fix a rage click?
- Find the element. You need the page, the element and how many sessions did it. UserProof gives all three, and the file and line, to your coding agent (Claude Code, Codex or Cursor).
- Reproduce it. Click the element three times yourself, on a phone as well as a desktop.
- Fix the cause, not the clicking. Dead element: wire up the handler or drop the pointer cursor. Hover menu: open it on click and keep hover as a shortcut. Slow response: show feedback at once and disable the button while the request runs. Error: fix the exception behind the click.
- Check it. Ship the fix and see whether the same element still collects bursts. UserProof checks whether the fix worked.
What the dead click scan found
A dead element is one place a rage click can start, and it is the part of the problem we have counted. We clicked up to 20 things that looked clickable on each page of 493 YC startup homepages (1,337 pages) on October 28, 2026, and counted a click as dead when 3 tries in a row changed nothing.
| Kind of element | Dead clicks (count, on 33 of 493 homepages) |
|---|---|
| Buttons and links in the header, nav or footer | 17 |
| Other buttons and links | 15 |
| Toggles, tabs and hover cards | 11 |
| Things that only look clickable | 6 |
| All dead clicks | 49 |
Method, limits and the CSV are on the dead clicks report, and the same scan scored per startup is the YC homepage report.
How do you find rage clicks on your own site?
Click through your page with the free dead click finder to catch dead elements before visitors do. To see what visitors actually do, UserProof records real visits with a script tag and field values are never recorded. It is free for 3 sites and 5,000 recorded visits a month; Pro is $29 a month for 50,000 visits and Scale is $99 a month for 250,000. Analyses and fix checks are unlimited on every plan. See pricing.
Sources, read November 14, 2026
- UserProof rage click rule: findings engine, src/lib/engine/findings.mjs (rage block and passesFloors), read November 14, 2026
- Dead click scan of 493 YC homepages, October 28, 2026: getuserproof.com/state-of-dead-clicks and the CSV
- Microsoft Clarity definition (page dated December 1, 2025): Semantic metrics
- PostHog thresholds: Autocapture
- FullStory definition (March 4, 2022): Rage clicks
- Hotjar and Contentsquare (updated November 9, 2025): Rage clicks
- LogRocket (updated October 6, 2026): Signals
- Mouseflow (December 19, 2024): Understanding and resolving rage clicks
- UserProof plans: getuserproof.com/pricing
FAQ
What is a rage click?
A rage click is a burst of fast, repeated clicks on one spot, usually because the first click got no visible response. Microsoft Clarity describes it as multiple clicks in a clustered area in rapid succession (docs dated December 1, 2025, read November 14, 2026).
How many clicks make a rage click?
It depends on the tool. PostHog counts three clicks, each within 30 pixels and 1 second of the previous one, and UserProof counts 3 or more clicks on one element, each under 1 second apart. Clarity, FullStory, Hotjar, LogRocket and Mouseflow publish no number on the pages we read on November 14, 2026.
What is the difference between a rage click and a dead click?
A dead click is a single click that changes nothing. A rage click is a burst of clicks on the same spot. A dead element is one common reason a visitor clicks again, but a slow response or an error on click can cause it too.
How do I stop rage clicks on my site?
Find the element and page where they happen, click it three times yourself, then fix the cause: wire up the handler, show feedback at once while a request runs, fix the error, or make a menu open on click. Then check the same element on the next visits.