Dead clicks and rage clicks: what they tell you about lost enquiries

The short answer

Frustration on forms is common. Zuko's form analytics benchmark found that 34% of people who start a form do not complete it, and that contact forms convert worse than any other form type (a vendor study; sample size not disclosed). Dead and rage clicks are two of the clearest clues to why, because they show the exact moment a visitor tried and the page failed them.

What is a dead click?

A dead click is a click on part of a web page that produces no response in a reasonable time. The screen does not change, nothing opens and the visitor stays where they were. Dead clicks usually point to something that looks interactive but is not, an element that is broken, or a response that is too slow to notice.

Common examples on service business websites:

• Underlined or coloured text that is not a link.
• A team member's photo that visitors expect to open a bio.
• A logo in a "clients" strip that visitors expect to open a case study.
• A heading on a pricing card that looks like a button.
• A "Submit" button that is waiting on a slow request and shows nothing while it waits.

What is a rage click?

A rage click is a rapid burst of clicks in the same small area of a page. It happens when a visitor expects a response, does not get one quickly, and clicks again, and again. Rage clicks are a strong sign of frustration, and they cluster around slow buttons, broken controls and elements that look clickable but are not.

Microsoft's definition of a rage click is loose: multiple clicks in a clustered area in rapid succession. It does not publish a fixed number of clicks or a time window, and other tools use their own rules. So compare rage click counts within one tool over time, not between tools.

What is the difference between a dead click and a rage click?

A dead click is one click that got no response. A rage click is several clicks in quick succession on the same spot. They often happen together: a visitor makes a dead click, waits, then rage clicks. Dead clicks tell you what looks interactive and is not. Rage clicks tell you where a visitor's patience ran out.

Two related signals are worth knowing. A quick back is when a visitor leaves a page and returns almost straight away, because the page they reached was not what they expected. Excessive scrolling is more vertical scrolling than usual, often a sign someone cannot find what they came for. Clarity flags both.

What do dead clicks and rage clicks tell you about lost enquiries?

Dead and rage clicks show where visitors tried to act and your site did not respond. On pages that carry enquiries, that is the moment closest to a lead. Frequent dead clicks usually mean confusing design. Rage clicks on a form or button usually mean something is slow or broken. Both are fixable, and both are measurable after the fix.

The commercial logic is simple. A visitor who clicks is a visitor who wants something. A visitor who clicks five times wants it badly. If the page does not respond, you lose the most motivated person on it.

Each of those numbers maps to a click signal. WebAIM's 2026 scan found missing form labels on 51% of home pages, and unlabelled form fields are a common cause of dead clicks: in many layouts, clicking a label that is properly connected to its field puts the cursor in the field, and clicking an unconnected one does nothing. Slow pages and slow form submissions are a classic cause of rage clicks. WebAIM's figure is automated detection on home pages only, so the real rate on form pages is unknown, and Portent's speed study covers only 20 websites. They are directional, not precise.

A worked example, with the arithmetic

The figures are illustrative. Put your own in.

A quote form page gets 2,000 sessions a month and converts at 4%: 80 enquiries. Clarity shows 6% of sessions (120) include a rage click on the "Get a quote" button. Five recordings show a two to three second pause with no loading indicator after the click, and some visitors leave during it.

Suppose a third of those 120 visitors were ready to submit (40 people) and the pause lost half of them (20). Adding a loading state and a clear success message would recover up to 20 enquiries a month: 100 instead of 80, or a move from 4% to 5%. If the same site wins one in five enquiries, that is up to four extra clients a month from a change a developer can make in an afternoon. It is a scenario, not a forecast, and the only way to know is to fix it and watch the rage click count and the enquiry count the following month.

How do you find dead clicks and rage clicks in Microsoft Clarity?

In Microsoft Clarity, open the Dashboard to see the share of sessions with dead clicks and rage clicks, and the pages where they happen most. Then open Heatmaps for a key page, choose the dead clicks or rage clicks click map to see exactly where they cluster, and filter Recordings to watch the sessions behind them.

Step by step:

1. Start on the Dashboard. The insights panel shows dead clicks, rage clicks, quick backs and excessive scrolling, with the pages most affected. Note the pages that carry enquiries.
2. Filter to your enquiry pages. Use the visited URL filter for your contact page, quote form and main landing pages. Split by device, because mobile and desktop layouts fail differently.
3. Open the click map. In Heatmaps, pick the page and switch the click map from all clicks to dead clicks, then to rage clicks. Clarity also offers error clicks, first clicks and last clicks.
4. Watch five recordings. Filter Recordings to sessions on that page with rage clicks. If the same moment repeats in three of five, you have a finding. If it happens once, you have a person.
5. Check JavaScript errors. Clarity tags sessions where a click caused a JavaScript error. A click error on a Submit button is the most urgent signal of all.
6. Star the evidence. Clarity keeps recordings for 30 days. Favourites are kept for up to nine months (Clarity FAQ).

Clarity is free and already detected on 4.1% of all websites, according to W3Techs. If you have not installed it, the Microsoft Clarity guide for marketers covers setup and privacy. Other tools detect the same signals under similar names; see Hotjar alternatives and Microsoft Clarity vs Hotjar.

What causes dead clicks and rage clicks, and how do you fix them?

Most dead clicks come from design that promises interaction it does not deliver: text styled like links, images people expect to open, cards that look like buttons. Most rage clicks come from slowness or breakage: buttons with no loading state, controls that fail on mobile, scripts that error. The fix is either to make the element work or to make it stop looking clickable.

When are dead clicks and rage clicks not a problem?

Dead and rage clicks are not always a problem. Some people click text as they read, double-click out of habit, or tap quickly through an image gallery. A handful of dead clicks on body copy is normal. The signal matters when it clusters on one element, repeats across sessions, and sits on a page that carries enquiries.

Three tests before you act:

• Is it concentrated? Twenty dead clicks spread across a long article are noise. Twenty on one logo are a pattern.
• Is it on a money page? Prioritise the contact page, forms and paid landing pages over the blog.
• Does it repeat in recordings? Three of five sessions showing the same moment is a finding. One is an anecdote.

How does PostCliq use dead clicks and rage clicks?

PostCliq is a free website audit from WP Creative, an Australian website growth agency. It reads up to 50 public pages the way a careful visitor would and finds what stops visitors becoming enquiries. With Microsoft Clarity connected, it sets Clarity's dead clicks, rage clicks, quick backs and excessive scrolling beside its own findings for the same page.

The value is in the pairing. Clarity can tell you a quote form has a high rage click rate. PostCliq's own checks can tell you, from the page itself, that the same form has no visible error message or that the page is slow on mobile. Put together, that is one finding with evidence and a fix, not two dashboards. PostCliq keeps behaviour signals separate from issues it observed directly, because a rage click is a hypothesis until someone confirms it. The Clarity connection is read-only; details on the Microsoft Clarity integration page. PostCliq never submits forms, so it will not tell you whether an enquiry arrived: test that yourself with the enquiry form review kit.

What to do next

1. Install Microsoft Clarity if you have not already. It is free, and it starts flagging dead and rage clicks as soon as it records.
2. List your enquiry pages: contact, quote or booking forms, and the landing pages your ads send people to.
3. Open the dead click and rage click maps for each page, on mobile first, and write down the element with the most clicks.
4. Watch five recordings per page and keep only the findings that repeat.
5. Fix one element per page, date it, and compare the counts two weeks later.
6. Check what the recordings cannot show. Run a free PostCliq audit for speed, forms, clarity and trust on the same pages, and make sure your forms fire a GA4 key event with GA4 key events for lead generation.

Frequently asked questions

What is a dead click?

A dead click is a click on a web page that produces no visible response in a reasonable time. Nothing changes on screen and the visitor is not taken anywhere. Dead clicks usually happen on elements that look interactive but are not, such as underlined text, logos or photos, or on buttons that are waiting on a slow response and show nothing while they wait.

What is a rage click?

A rage click is a rapid burst of clicks in the same small area of a page. It usually means the visitor expected a response and did not get one quickly, so they clicked again. Rage clicks cluster on slow Submit buttons, controls that do not work on mobile, and elements that look clickable but are not. Tools define the exact threshold differently.

What is the difference between a dead click and a rage click?

A dead click is a single click that gets no response. A rage click is several quick clicks on the same spot. They often appear in sequence: a visitor makes a dead click, waits, then rage clicks. Dead clicks point to misleading design or broken elements. Rage clicks point to where the visitor's patience ran out, often on something slow.

How do I find rage clicks in Microsoft Clarity?

Open your Clarity Dashboard to see the share of sessions with rage clicks and the pages most affected. Then go to Heatmaps, choose the page, and switch the click map to rage clicks to see where they cluster. Finally, filter Recordings to sessions with rage clicks on that page and watch five. Split everything by device, because mobile often fails differently.

Are dead clicks bad for SEO?

Not directly. Dead clicks are a user experience signal inside your analytics tool, not something search engines measure. The causes can overlap with things that affect search, such as slow pages, broken scripts and poor mobile usability. Fixing dead and rage clicks is worth doing for enquiries first. Any search benefit comes from the underlying fix, not the click count.

What is a good dead click rate?

There is no published benchmark we would trust. Microsoft does not publish one, and every tool defines the signals slightly differently. Track your own rate per page over time instead. Compare the fortnight before and after a fix on the same page and device. A falling count on an enquiry page, alongside a steady or rising enquiry rate, is the result you want.