Quick answer
A dead click is a click or tap on a web page that produces no visible response, such as no navigation, content change or triggered request, usually because an element looks clickable but is not, or because its code fails or responds too slowly.
What is a dead click?
A dead click is a click (or tap) that produces no visible response: the page does not navigate, nothing opens, nothing changes on screen. The visitor expected something to happen, and nothing did.
Dead clicks usually mean one of two things: an element looks clickable but is not, or an element should do something but its code is broken or too slow. Either way it is a small moment of friction, and many of them add up to lost conversions.
Dead clicks vs rage clicks vs error clicks
| Signal | What happens | Usually means |
|---|---|---|
| Dead click | One click, no response | Misleading design or broken element |
| Rage click | Several rapid clicks on the same spot | Frustration: something is not working or is slow |
| Error click | A click followed by a JavaScript error | A bug in the click handler |
They often appear together: a visitor dead-clicks a non-working button, then rage-clicks it.
How tools detect dead clicks
Session-recording and heatmap tools typically flag a click as dead when, within a short window after it (often around a second), there is no navigation, no change to the page's content and no network request triggered by it. Exact rules vary by tool, so dead-click counts are not comparable across products.
Common causes
| Cause | Example |
|---|---|
| Visual cues of clickability | Underlined or blue text that is not a link; product images that cannot be enlarged |
| Icons and cards without actions | A card with a hover effect where only the small "More" link works |
| Broken JavaScript | A button whose handler failed to load or threw an error |
| Slow responses | A button that works after 3 seconds with no loading state |
| Overlapping elements | An invisible layer covering the real button |
| Disabled controls that do not look disabled | A "Next" button that silently does nothing until a field is filled |
Worked example
A product page's click map over two weeks (sample data):
| Element | Clicks | Share of clicks | Clickable? |
|---|---|---|---|
| Add to cart | 4,120 | 38% | Yes |
| Main product image | 1,950 | 18% | No |
| Size chart text ("Check sizes") | 870 | 8% | No |
| Reviews star rating | 640 | 6% | No |
| Other | 3,240 | 30% | Mixed |
Nearly a third of clicks (32%) land on elements that do nothing. The fixes are cheap: let the image open a zoom gallery, turn the size text into a link to the size chart, and make the star rating jump to reviews. After shipping them, the team should see those clicks become interactions and fewer exits from the page.
How to fix dead clicks
- Make it work or make it look inert. If people expect an action, add it; if not, remove the visual cues (underlines, pointer cursors, hover effects).
- Add loading and disabled states so slow or unavailable buttons explain themselves.
- Enlarge tap targets and check for overlapping layers, especially on mobile.
- Fix JavaScript errors on click handlers; see find JavaScript errors.
- Recheck after each release: layout changes often create new dead zones.
Finding them in TapCub
TapCub does not label "dead clicks" as a separate metric. It records clicks with coordinates for heatmaps, an element table of the most clicked controls, rage clicks (three clicks within 300 ms and 50 px, decided in the collector) and JavaScript errors. To find dead-click candidates, open the page's heatmap and look for click clusters on elements that are not links or buttons, check the element table for non-interactive elements with a high share of clicks, and watch session replays filtered to sessions with rage clicks or errors. See how to read a heatmap, session replay and user friction.
Sources
- Microsoft Clarity. Semantic metrics: dead clicks, rage clicks, excessive scrolling.
- FullStory. What are dead clicks?
- Nielsen Norman Group. Beyond blue links: making clickable elements recognizable.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.
Product Adoption Consultant
Explores customer onboarding, live conversations, and self-service, turning common usage questions into practical guidance and improvements.