What is a dead click?

How is a dead click detected?

Detection is inference, not observation. The tool cannot know what a click was supposed to do, so it watches for what did not happen.

After a click, the script waits a short window, typically somewhere between 500 milliseconds and a few seconds depending on vendor, and checks whether any of the following occurred:

• A DOM mutation anywhere in the document
• A navigation or URL change
• A network request initiated by the click
• A scroll position change

If none occurred, the click is recorded as dead. Because the window is a fixed guess, a genuinely slow response gets misclassified as dead, and so does a click that triggers an animation the tool does not watch for. Dead click counts therefore carry more false positives than rage click counts, so confirm one against a recording before treating it as a defect.

How is a dead click different from a rage click?

They count different events, and only one of them says anything about how the visitor felt.

The relationship is causal and sequential. A dead click is often the first event, and the rage click is what happens when the visitor tries again. An element with high dead clicks and low rage clicks means people accept the non-response and move on. High on both means they care enough to fight it, which usually indicates the element was on the path to something they wanted.

What causes dead clicks?

Five causes, roughly in order of frequency.

Non-interactive elements that look interactive. Styled cards, bordered boxes, icons, headings in a heavier weight, images inside content. The dominant cause, and the one carrying the most product insight, because it is visitors telling you what they expected to work.

Broken or missing event handlers. A JavaScript error killed the listener, a third party script failed, or a handler was attached to an element that gets re-rendered. Real defects.

Clicks before scripts finish loading. Fast visitors clicking during page load, before the handler attaches. Concentrated on slow connections and above-the-fold elements.

Disabled controls with no disabled styling. A submit button that is inert until validation passes, styled identically to its active state.

Overlays intercepting clicks. An invisible element with a higher z-index sitting over the target. The visitor clicks the button, the overlay receives it, nothing happens. Common with cookie banners, modals that did not fully close, and full-width containers with unintended padding.

Are dead clicks always bad?

No, and treating every dead click as a bug wastes effort.

Legitimate dead clicks:

• Clicking on whitespace to dismiss focus, close a dropdown, or deselect
• Clicking text to position a cursor or begin a selection
• Double clicks on already-completed actions
• Clicking a static element deliberately, such as tapping an image to check whether it enlarges, and accepting the answer

The distinguishing question is whether the click was exploratory or expectant. Exploratory dead clicks are noise. Expectant dead clicks, especially clustered on one element, are a defect or an unmet expectation.

Volume is the practical filter. A handful spread across a page is normal behavior. Dozens concentrated on a single element is a signal.

Where do Webflow sites generate dead clicks?

Images inside CMS rich text. They look like every other image on the site, and images placed in a rich text field are not lightbox enabled by default. Visitors tap expecting a zoom.

Cards and collection items where only part of the card links. The link block wraps the title, and the visitor clicks the image, the description, or the padding around them. The most common Webflow dead click and the easiest to fix, since a link block can wrap the entire card or collection item.

Divs styled as buttons. Full button styling, no link block or click interaction. The missing pointer cursor is the tell.

Interactions triggered on hover rather than click. Works on desktop, produces dead clicks on touch devices where hover does not exist. A frequent source of mobile-only dead clicks.

Tabs where the click target is the text label. Padding around the label sits outside the tab link, so clicks near the edge land on nothing.

Custom code components that fail silently. Embedded widgets that error out render their container but no functionality, so the element looks present and does nothing.

Key takeaway: most Webflow dead clicks come from the gap between what is styled as interactive and what is wrapped in a link block.

Related terms

Rage click · Click map · Session recording · Website heatmap · User behavior analytics

Service: Conversion Rate Optimization.

FAQ

What is a normal dead click rate?

Lower confidence than the equivalent rage click number, because the detection window is a fixed guess and a slow response gets counted as a dead click. Read the count as a shortlist of elements to inspect rather than as a rate to track, and confirm each one in a recording before treating it as a defect.

Do dead clicks affect conversion rate?

Indirectly, and sometimes substantially. A dead click on a decorative element costs nothing. A dead click on the element a visitor believed was the path to pricing costs that visitor. Impact depends entirely on where the click landed, which is why ranking by element rather than by page is the right first step.

Can Google Analytics detect dead clicks?

No. GA4 records events that fired, and a dead click is defined by the absence of one, so there is nothing for it to log. Detection requires a behavioral tool watching for what did not happen after a click, which is why the definition and the counts vary between vendors.

How do you fix a dead click on a non-clickable element?

Two options, and the right one depends on intent. Make it work, by wrapping it in a link block or adding the interaction visitors expected. Or make it stop looking clickable, by removing the border, shadow, hover state, or weight that implied interactivity. Doing neither leaves the promise in place.