TL;DR: Rage clicks, dead clicks, quick backs, excessive scrolling and click errors are the five frustration signals worth checking on a lead-generation site. Each points at a different kind of fix. On our own quote page, the most common dead click was a "Get Started" button that links to the page the visitor is already on.
The one-sentence answer: A rage click is rapid repeated clicking in one spot, a dead click is a click that gets no response, and a quick back is a visitor leaving a page and returning within a short time threshold; each one points to a specific spot where your site may have failed someone, and each has a few likely causes you can check.
We pulled our own Microsoft Clarity dashboard for the 30 days to October 3, 2026. After Clarity excluded 91 bot sessions, 127 sessions were left. Dead clicks showed up in 14 of them, 11.02%. Rage clicks showed up in one.
Then we opened the dead-click map for our quote page. The element at the top of the list, with two of the five dead clicks on desktop, was the white "Get Started" button in our own navigation bar. It links to /payments/get-a-quote. On the quote page, that's the page you're already on, and Clarity saw no response: it counted both clicks as dead.
One caveat up front: we didn't filter this map. It includes every visitor ID, including the four repeat visitors we flagged in our session recordings guide, so some of these clicks may be our own. The button still points at the page it sits on.
That's the whole value of these signals in one example. Nobody reported it. Nobody would. We found it by looking.
What are frustration signals?
Frustration signals are behaviours that analytics tools flag automatically when a visitor's interaction with a page goes wrong: clicking repeatedly, clicking something that doesn't respond, scrolling far more than normal, or leaving and immediately coming back. Clarity's Insights panel flags four of them, tags a fifth (click errors) separately, and lets you filter recordings and heatmaps by each.
The numbers below are Clarity's, because it's free and we run it, but the signals aren't Clarity-specific. Other session-recording tools have their own versions. What matters is the reading, not the brand.

Our Clarity Insights panel for the 30 days to October 3, 2026. At 127 sessions, one session is 0.79 percentage points, so read the session counts, not the percentages.
What is a dead click, and what usually causes it?
A dead click is a click on an element that gives no feedback in a reasonable amount of time: nothing visually changes and the page doesn't navigate. Microsoft says a dead click "can signify broken elements, high latency requests, or misleading UX." These are the four causes we check, in order, and three of them have nothing to do with broken code.
1. Text or images that look clickable. Bold headings, underlined phrases, product photos and icons. On our quote page, two of the five dead clicks landed on the panels around our quote form: one whose text starts with our "Save" percentage on processing fees, the other headed "Get a free rate analysis." Without watching those recordings, we can't say what the visitor expected.
2. Links to the page you're already on. Our "Get Started" button. Shared navigation makes this easy to do by accident, because the same header renders on every page, including the one each button points to.
3. Slow responses. A button that works, but takes long enough that the visitor decides it didn't. The page eventually responds, but by then the click may already count as dead.
4. Genuinely broken elements. A script error, a missing link, a form button wired to nothing. The most urgent of the four.
The fix, by cause: make the clickable-looking thing actually clickable (link the claim to the detail), make self-links do something useful (on the quote page, scroll to the form), speed up or add a loading state to slow controls, and fix broken ones first. As of October 3, our "Get Started" button, in both the desktop header and the mobile menu, still links to itself on the quote page. Now we know.

Dead clicks on our quote page, desktop only, 30 days to October 3, 2026. Five clicks is a small sample. One of them pointed at something we can fix in two places in our code.
What is a rage click?
A rage click is several clicks in quick succession on the same small area. Microsoft describes it as a visitor who "clicks multiple times in a clustered area in rapid succession," and says rage clicks can be strong indicators of user frustration. It usually means the visitor expected something to happen, it didn't, and they tried again harder.
Rage clicks and dead clicks can overlap. A dead click is one click that did nothing. A rage click is what happens next if the visitor really wants it to work.
Causes we'd check first:
- A button that's working but slow, especially on mobile connections. The visitor taps three times while the form submits, and sometimes submits it three times.
- Small or crowded tap targets on phones, where the visitor keeps missing.
- Carousels, accordions and tabs that respond to a click with an animation the visitor doesn't notice.
- Disabled buttons that don't look disabled. A submit button that stays grey until a required field is filled, with no message saying which field.
The fix: watch the recording first, because the cause is rarely obvious from the heatmap. Then add visible feedback within a fraction of a second of a click (a spinner, a colour change, a disabled state with a reason).
Our one rage-click session in 30 days isn't a pattern. On a site with ten times the traffic, a cluster of rage clicks on one element is worth an afternoon.
What is a quick back?
A quick back is a visitor clicking through to a page, then returning to where they came from within a short time. Microsoft says the user "doesn't find the navigation useful" and returns "under a certain threshold of time," which it ties to the dwell time for that page. Microsoft says the quick-back filter helps you find confusing navigation or content; often, a link promised something the destination didn't deliver.
Quick backs showed up in 5 of our 127 sessions, 3.94%. That's the second most common of Clarity's four Insights signals on our site, after dead clicks.
Causes we'd check first:
- Menu labels that don't match the page. A visitor clicks "Pricing" and lands on a page that says "contact us for a quote."
- Calls to action that oversell. "See how it works" leading to a sales form.
- Accidental clicks on mobile, especially on navigation close to the thumb.
- Wrong-audience pages. A visitor looking for one service landing on a page written for another.
The fix: filter recordings to quick backs and note which page people bounced from and which link they used. If the same link keeps producing quick backs, rewrite either the link or the destination until they agree.
What does excessive scrolling tell you?
Excessive scrolling is a session with more vertical scrolling than the expected average. Microsoft says it "could indicate inaccessible or frustrating UX, poor content relevance, discovery, or nonstandard site interactions." Microsoft's filter docs say it helps identify users who are lost on your page: often a visitor hunting for something they can't find, like a phone number, a price or a specific service.
We had zero sessions flagged in 30 days. That isn't proof our pages are easy to navigate. Excessive scrolling is relative to an expected average, and on a small site with short sessions, the bar may simply not be crossed.
The fix: if a page shows it, look at what visitors scroll past and what they stop on. If they scroll the full page twice and leave, the thing they wanted either isn't there or isn't labelled the way they'd search for it. Pair it with a scroll map, covered in our guide to Clarity heatmaps.
What about JavaScript errors and click errors?
JavaScript errors are script failures in the visitor's browser, and click errors are the subset that happen right after a click. Clarity tags every session where a click triggers a JavaScript error, so you can filter to them. These are the signals most likely to mean something is actually broken rather than confusing.
Visitors rarely see the error itself. They see a button that does nothing, which is why click errors can show up as dead clicks too. If a dead click repeats on the same element, check for a click error on it before redesigning anything.
The fix: sort errors by frequency, watch two recordings of the most common one, and send the error message and the recording link to whoever maintains your site. A recording is worth ten bug reports, because it shows the exact browser, device and steps.
How should you prioritize which signal to fix first?
Fix in this order: click errors first, then dead clicks on calls to action, then rage clicks, then quick backs, then everything else. Broken things lose leads silently. Confusing things lose them more slowly. And a signal on a page that matters, like your quote form, outranks the same signal on a blog post.
Two rules keep the list honest:
- Count sessions, not percentages. On a small site, one session moves the rate by nearly a point. Our 0.79% rage-click rate is a single session.
- Exclude your own team before you count. Repeat visits from people who already know the site distort every signal. We cover the filters in our guide to Clarity session recordings.
If you want the broader context, our list of signs your website is costing you customers covers the problems these signals tend to reveal, and website conversion rate optimization covers what to change once you've found them.
Frequently Asked Questions
Does a dead click always mean something is broken?
No. Dead clicks measure the gap between what visitors expect to respond and what does: a working link can produce them, and so can plain text that looks interactive. Sometimes that gap is a bug. More often it's a design decision worth revisiting.
Can rage clicks happen on purpose?
Yes. Some visitors click repeatedly out of habit, and games, galleries and drag-and-drop tools generate rapid clicks by design. Before acting on a rage-click cluster, watch two recordings. If the visitors look calm and finish what they came to do, it isn't frustration.
How much traffic do I need before these signals mean anything?
There's no fixed number, but count sessions per page and per device, not per site. A handful of page views is enough to find a specific element worth fixing, as we did, but not enough to say how common a behaviour is.
Do frustration signals hurt my search rankings?
Not directly, as far as either company has said: neither Google nor Microsoft's Clarity documentation says Clarity data feeds rankings. Indirectly, slow responses also show up in Core Web Vitals, which Google does use.
We read these signals on our own site before we read them on anyone else's. If you'd like us to look at yours, see how we approach web design, or get in touch.
Sources
- Microsoft Learn, "Semantic metrics": definitions of rage clicks ("clicks multiple times in a clustered area in rapid succession"), dead clicks ("can signify broken elements, high latency requests, or misleading UX"), excessive scrolling, quick backs and click dwell time, and click errors. learn.microsoft.com (page dated 2025-12-01, retrieved 2026-10-03)
- Microsoft Learn, "Click maps": dead-click, rage-click and error-click map types. learn.microsoft.com (page dated 2025-09-15, retrieved 2026-10-03)
- Microsoft Learn, "Filters overview": Insights filters for rage clicks, dead clicks, excessive scrolling and quick backs; JavaScript error and click error filters. learn.microsoft.com (page dated 2026-05-21, retrieved 2026-10-03)
- ClickWerxs, Microsoft Clarity project for clickwerxs.com, last 30 days to October 3, 2026: 127 sessions after 91 bot sessions excluded; rage clicks 0.79% (1 session); dead clicks 11.02% (14 sessions); excessive scrolling 0%; quick backs 3.94% (5 sessions). Quote page dead-click map, desktop: 8 page views, 5 dead clicks across 4 elements, top element the navigation "Get Started" link (2 clicks). Operator data.
- ClickWerxs site code,
components/shared/Navbar.tsx: the desktop "Get Started" button and the mobile menu's "Get Started" both link to/payments/get-a-quote. Operator data.
Kaleb Dickhaut — Founder, ClickWerxs. Kaleb built ClickWerxs from the ground up, from payment processing ISO to the Command Center platform to the AI SEO methodology the blog runs on. He has onboarded hundreds of small businesses onto payment and CRM systems. linkedin.com/in/kaleb-dickhaut
