Find dead clicks and rage clicks: what UserProof counts and how to use it
UserProof counts four click problems from real visits: dead clicks (nothing happened within 2.5 seconds), rage clicks (3 or more fast clicks on one element), errors on click and responses slower than 2 seconds. Fixed rules count them, never an LLM. Your coding agent then gets the worst one with the file and line to change.
How common is the problem? When we scanned 493 YC startup homepages on October 28, 2026, 33 of them (6.7%) had at least one dead click, and 43 of the 49 dead clicks were on real buttons and links, not plain text. The full numbers are in our dead clicks report.
Jump to: quick picks · the four rules · how to use it · limits · price · FAQ
Quick picks: what are you doing?
| If you want | Use | Why |
|---|---|---|
| To check your own page right now, free | The dead click finder | You click through your page and each click is marked worked, slow, dead or error. Nothing is sent back. |
| To find the clicks real visitors get stuck on | UserProof on your live site | It counts the four problems below across every recorded visit and ranks them. |
| Broken buttons found before launch | The free scan in setup | It clicks what looks clickable on your live site and needs no traffic. |
| A heatmap of where people click | Microsoft Clarity or Hotjar | UserProof has no heatmaps. |
The four rules, read from the code
Each rule below is copied from the recorder at ingest.getuserproof.com/sdk.js and from the findings engine that reads its events, both read on November 7, 2026. The recorder holds every click for 5 seconds and notes the first thing that happened after it and how long that took.
| Problem | What one looks like | When it becomes a finding |
|---|---|---|
| Dead click | Nothing happened within 2.5 seconds: no change to the page, no scroll within 0.1 seconds, no focus, text selection or tab change within 1 second, and no move to another page. | 70% or more of the sessions that clicked that element got no response. |
| Rage click | 3 or more clicks on the same element, each less than 1 second apart and within 30 pixels of the first, with nothing happening within 1 second of the first click. | Enough sessions do it (the floors below). Clicks in text fields, dropdown selects and labels don't count. |
| Error click | A JavaScript error on the same page within 1 second of the click, before the next click or page load. | Half or more of the clicks on that element are followed by one. |
| Slow response | The page answered, but after more than 2 seconds (the watch stops at 5). Only clicks that ask for something count: buttons, links, checkboxes and pointer-styled elements. | The median response on that element is over 2 seconds. |
Every finding also has to clear three floors: at least 10 sessions, at least 3 different visitors, and at least 1% of the page's sessions. Clicks on links, form fields, labels, the page background and layout blocks such as a section or a footer are never counted as dead, because they focus, navigate or were never meant to do anything. Plain paragraphs and headings count only when they are styled with a pointer cursor.
Most guides define these problems without a number. LaunchDarkly's tutorial, read November 7, 2026, calls rage clicks "frantic, repeated clicks on a button or link that doesn't seem to be working" and gives no click count for the definition itself. Its alert rule uses five or more clicks in an eight-pixel area over at least two seconds. The table above is the count and the window UserProof uses.
How to use it
- Set up UserProof in your agent. Follow the Claude Code setup or the Codex and Cursor setup. Done looks like the agent reporting status
received: the script tag records. - Deploy and let visitors arrive. Nothing is counted until real visits come in, and a finding needs 10 sessions from 3 visitors. Done looks like visits showing when you ask your agent for usage.
- Ask for the top fix. Ask your agent "what should I work on?". Done looks like one problem, for example a dead click on a menu button, with the sessions that prove it and the file and line to change.
- Ship the fix and mark it. Tell the agent the fix is in. Done looks like the fix marked applied; UserProof then checks whether your goal moved.
Before you have traffic, the free scan and the dead click finder catch the same kind of broken button on day one. To keep part of a page out of recordings, see what the script tag records.
No visitors yet? The site scan tries a live site before anyone arrives.
Limits, stated plainly
- Low-traffic pages may show nothing. The floors of 10 sessions and 3 visitors keep one confused visitor from becoming a finding, so a page with a handful of visits a week won't produce one.
- A hover menu can read as a dead click. If a menu opens on hover, the click itself changes nothing. That is often a real problem on phones and keyboards, but check it before you change the menu.
- A slow request that ends in nothing counts as dead, not slow. The watch stops at 5 seconds, so a reply after that is not timed.
- It stores events, not a video. You see which element, what happened after and how long it took, not a picture of the screen.
- No heatmaps and no surveys. Use a tool from our ranking of 12 replay tools if you need those.
Price
| Plan | Price | Recorded visits a month | Sites |
|---|---|---|---|
| Free | $0 | 5,000 | 3 |
| Pro | $29 a month | 50,000 | Unlimited |
| Scale | $99 a month | 250,000 | Unlimited |
Read from our pricing page on November 7, 2026. Dead click, rage click, error and slow response counts are on every plan, and analyses are unlimited.
FAQ
How many clicks make a rage click in UserProof?
Three or more clicks on the same element, each less than 1 second after the one before and within 30 pixels of the first, with nothing happening on the page within 1 second of the first click. Repeated clicks in a text field are left out, because that is how people select text.
How long does UserProof wait before it calls a click dead?
The recorder watches each click for 5 seconds. A click counts as working if the page changes within 2.5 seconds, it scrolls within 0.1 seconds, focus, a text selection or the tab's visibility changes within 1 second, or the visitor leaves for another page. Anything else is marked dead.
How much traffic does UserProof need before it reports a dead click?
A finding needs at least 10 sessions from at least 3 different visitors, and at least 1% of that page's sessions. For a dead click, 70% or more of the sessions that clicked the element must have got no response. Below that, use the free scan or the dead click finder.
Does UserProof use AI to decide what a dead click is?
No. Dead clicks, rage clicks, errors on click and slow responses are counted from the recorded events by fixed rules. Your coding agent only writes the explanation and the fix, and the finding carries the sessions that prove it.
Sources, read November 7, 2026
- UserProof recorder: sdk.js (the 5-second click watch and its response windows), read November 7, 2026
- UserProof findings engine (the dead, rage, error and slow rules and the floors), read November 7, 2026
- Dead click counts: UserProof scan of 493 YC startup homepages, scanned October 28, 2026
- UserProof plans: pricing page, read November 7, 2026
- LaunchDarkly, What are rage clicks and how to detect them, read November 7, 2026