All articles Fundamentals

Dead Clicks: What They Reveal About Your UI

Designer at a dark studio desk reviewing an interface in blue monitor light

A user taps a card that looks exactly like a button. Nothing happens: no navigation, no spinner, no error, no request that changes the page. That is a dead click, and it is one of the clearest signals a session replay can hand you, because it marks the exact place where your interface invited an action and then ignored it.

Dead clicks are cheap to detect and expensive to ignore. They never reach your error tracker and they do not look like a bounce until the user has already given up. What they show is the gap between what your UI promises and what it does.

This guide covers what counts as a dead click, how it differs from a rage click, the usual causes, and how to fix them from the replay instead of guessing from a dashboard.

What a dead click actually is

A dead click is a click or tap on an element that produces no visible response: no route change, no modal, no expanded state, no meaningful DOM change, and no network activity that alters what the user sees. Replay tools flag it by watching the DOM and the network for a short window after the click. It is a heuristic, so read the pattern: one dead click is noise, the same element across many sessions is a design decision that failed.

Dead clicks, rage clicks, and error clicks are three different signals

A dead click is usually a single click. A rage click is the same person hitting the same area several times in quick succession — frustration, often starting as a dead click the user thought they had missed. An error click fires a JavaScript exception. They lead to different fixes: dead clicks are mostly an affordance problem, rage clicks mean something looked broken or felt slow, error clicks mean the code threw.

What dead clicks reveal about your interface

Most dead clicks come from one of three places.

Hand touching one glowing translucent panel among dark inactive panels

Non-clickable look-alikes

The most common cause, and the cheapest to fix. A card with a hover shadow and no click handler. A heading styled like a link — blue, underlined — that is a span. The user is not confused; your CSS told them it was interactive. Fix it one of two ways: make the element do the thing, or remove the affordance — the pointer cursor, the hover state, the link color. Leaving the promise in place is the mistake.

Slow handlers and missing feedback

The handler runs, the request goes out, and nothing changes on screen until the response lands. So the user clicks again — now you have a duplicate request, a rage click and a support ticket. When an action takes longer than a frame, show it: a pending state on the button, a disabled attribute, a skeleton. Then hunt the silent failure, the catch block that writes to the console and returns, leaving the user in front of a button that did nothing.

Inert layers and overlays

A dismissed cookie banner that leaves a transparent full-screen layer in the DOM, an iframe swallowing events, a misplaced z-index, a mobile drawer that closed visually but still covers the viewport. Everything under it becomes a dead click, including your primary call to action, and the user cannot see why. On mobile, a tap target that is slightly too small or sits under the thumb produces the same signal.

How to read dead clicks in a session replay

Filter sessions that contain dead clicks and sort by count per session, not recency. Watch the few seconds before the click, not only the click: what the user tried first, what they expected, whether they hesitated. Then group by element. The same selector across many sessions is a fix; a single session is probably a stray tap. The heatmap shows whether an element collects clicks out of proportion to its importance, and Web Vitals shows whether slow interaction is part of the story. When you have hundreds of sessions and no time to watch them, Py reads one and explains what the user was trying to do when it stalled. Every form field is masked in the browser and again on the server, so you can watch real sessions without reading what anyone typed.

How to fix dead clicks, in order of payoff

  1. Affordance mismatches first. The cheapest fix and the biggest drop: make it clickable or make it stop looking clickable.
  2. Feedback on the first click. Move the pending state to the moment of the click, not the response.
  3. Visible failure states. If the request fails, say so and keep the action available.
  4. Kill inert layers. Audit overlays after dismissal, then fix z-index and pointer-events.
  5. Close the loop. Re-record, filter the same segment, and compare the dead-click count on that page.

Two people reviewing a dark display of glowing session cards in a meeting room

If you want other teams to see the evidence, Replay can render sessions inside your own admin per company or user: call identify(userId, { accountId }) and open them in the embedded player. The setup is in the docs.

FAQ

Developer at a standing desk annotating a floating diagram of glowing nodes

Are dead clicks always a bug?

No. Some are stray taps on decorative elements, and a few are users trying an interaction you chose not to build. The signal matters when it clusters on the same element, page and device class.

Why do dead clicks not show up in product analytics?

Analytics tools record the events you instrumented, and a click that produces no event is invisible to them by definition. Dead clicks are found in the DOM and the network, which is why they surface in session replay.

Can I watch replays without capturing what users type?

With Prynt Replay, yes. Every form field is masked in the browser and again on the server, with no unmask option, and bot sessions do not count against your session quota.

Dead clicks are the cheapest interface bug you will find this week. Prynt Replay records dead, rage and error clicks alongside heatmaps, JavaScript errors and Web Vitals, with Py to explain the sessions you have no time to watch. The free plan includes 1,000 sessions a month with 14-day retention. Start at https://pryntid.com — Replay runs on the same platform, one account and one bill, as the rest of the suite (platform).

Try it free

Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.

Keep reading