Rage clicks and dead clicks are friction signals — strong behavioural evidence that something on a page isn't working the way visitors expect. Unlike an error, nothing is technically broken: the page just fails the person using it.

Rage clicks

A rage click is a rapid burst of repeated clicks on the same element — the classic sign of frustration with a button that seems unresponsive, a slow action, or a control that looks interactive but isn't. Enable detection under Settings → Features, then open Rage clicks.

Rage clicks overview with KPIs and the element table

Grouped by element, not by click

Spectry identifies each element by its position in the page structure (its XPath), so every visitor who rage-clicks the same button lands on the same row — rather than producing hundreds of unrelated events. A single burst of angry clicking counts as one occurrence with a click count attached, so one very frustrated visitor can't distort your totals.

The overview

Open elements — distinct elements still awaiting attention.
Pages affected — how widely the problem is spread.
Sessions affected — how many visits hit friction.
Rage session rate — the share of all sessions containing a rage click. This is the number to watch over time; the raw count rises with traffic on its own.

The element table

Each row is one element: its label, CSS selector, page, occurrences, clicks, device, browser, any visitor feedback collected at that moment, status and when it was last seen. Sort by occurrences to find the worst offenders, or by last seen to check whether a fix has taken effect. Filter by device (Desktop, Mobile, Tablet) and by status.

Working through them

Every element carries a status, so a team can triage rage clicks the same way it triages bugs:

Open — needs investigation. The default.
Resolved — you've shipped a fix. Keep it in this state and watch whether the element reappears; if Last seen stops advancing, the fix worked.
Ignored — expected behaviour, or not worth fixing. Removed from the open count so the list stays meaningful.

Change status from the detail panel with Mark as.

The detail panel

Open a row to see everything captured about that element:

A screenshot of the element itself, cropped from the page capture, so you can see what visitors were clicking without leaving the dashboard.
The selector, XPath, position and the captured markup.
Bursts and clicks in burst — how often it happens, and how hard people click each time.
First seen, last seen, device, browser, page URL and session ID.
Any visitor feedback left in response to the frustration prompt.
A replay link that jumps straight to the moment of the rage click — usually the fastest route to understanding it.

Dead clicks

Dead clicks are clicks on elements that don't respond at all: non-interactive text and images visitors mistake for links, or handlers that silently fail. They show up as the Dead Click Hotspots overlay on click heatmaps, positioned exactly where they happened.

How to use them

Rage clicks on a CTA → check whether it's slow, broken, or visually misleading. Watch a replay before assuming which.
Dead clicks on text or images → visitors think they're links. Make them clickable, or restyle them so they stop looking like links.
Rage clicks that only appear on one device → almost always a layout or hit-area bug. Use the device filter to confirm.
A rage-clicked element with visitor feedback attached → read the feedback first. Someone has told you exactly what went wrong.

Rage clicks need the friction-signal features enabled and the relevant consent granted. If the list is empty on a busy site, check both before concluding your site is frictionless.

Error & Friction Monitoring

In this section.

Error logs

Rage clicks & dead clicks

Can't find what you're looking for?