---
title: "What is Dead Click? Definition & Examples | Kitbase"
description: "A click on an element that produces no visible response or navigation, suggesting a UX issue."
canonical: https://kitbase.dev/glossary/dead-click
---

[Home](/) [Glossary](/glossary) Dead Click

Session Tracking

# What is Dead Click?

A click on an element that produces no visible response or navigation, suggesting a UX issue.

A dead click occurs when a user clicks on an element and nothing visible happens — no navigation, no state change, no feedback. Unlike rage clicks (repeated frustrated clicking), a dead click is a single click that goes nowhere.

Dead clicks typically indicate elements that look interactive but aren't: text styled like a link, images that appear clickable, or buttons whose event handlers are broken. They represent a gap between user expectation and interface behavior.

Tracking dead clicks at scale reveals systematic UX issues. If 500 users per day dead-click on an image in your product tour, that image probably needs to be made actually clickable or visually redesigned to look non-interactive.

## Example

Dead click tracking shows that 200 users per week click on the product screenshots on your landing page, expecting them to enlarge or link to a demo. You add a lightbox preview, reducing dead clicks by 90% and increasing demo signups by 8%.

## Related Terms

[

Rage Click

Repeated rapid clicks on the same element, indicating user frustration with an unresponsive interface.

](/glossary/rage-click)[

Frustration Score

A computed metric that quantifies user frustration based on signals like rage clicks, dead clicks, and error encounters.

](/glossary/frustration-score)[

Session Replay

A visual playback of a user's session, showing exactly what they saw and did in your application.

](/glossary/session-replay)

## Understand every user session

See how users navigate your app, detect frustration, and replay sessions to debug UX issues.

[Explore Session Tracking](/event-tracking)