Rage and dead clicks: finding broken click targets in a shop

What rage and dead clicks reveal

A rage click is a rapid series of clicks on the same spot. Usually there is an expectation behind it that something should happen, and impatience when it does not. A dead click is a single click to which the page shows no visible response: nothing opens, nothing loads, nothing changes. Both signals are symptoms. They tell you where visitors get stuck, not why. That is what makes them useful: they direct attention to the few elements where expectation and behaviour diverge.

It is well documented that weak clickability cues cost time. In an eyetracking experiment, the Nielsen Norman Group compared pages with strong and with weak signifiers of clickability, for example underlined blue links versus links styled like body text, or raised buttons versus flat ghost buttons. On the versions with weak signifiers, participants needed on average 22 percent more time to find the target they were looking for (Nielsen Norman Group 2017), and they had on average 25 percent more fixations (Nielsen Norman Group 2017). The study involved 71 web users on a desktop computer (Nielsen Norman Group 2017) working on 9 pages; each page existed in two nearly identical versions that differed only in their signifiers (Nielsen Norman Group 2017).

One detail from the same study describes the dead click before it happens. On a jewellery retailer’s page, participants were asked to find pearl jewellery. In the version where the link looked like normal text, 9 of 24 participants stopped at the subheading because they believed it was clickable, and overlooked the actual link below it (Nielsen Norman Group 2017). In a shop, that would be a dead click on a heading without a function.

Typical click traps in online shops

Most broken click targets stem not from a spectacular bug but from a gap between design and function. Something looks like a button but is not one. Or it is meant to be one, but the code behind it was disconnected during the last theme update. Six patterns come up particularly often in shops:

An older benchmark from the Baymard Institute shows how common unclear click areas are: on 76 percent of 50 major US e-commerce sites, it was unclear to users in the product lists exactly what could be clicked and where a click would lead (Baymard Institute 2016). In their usability tests, the researchers also repeatedly observed wasted clicks on product descriptions and attributes that turned out to be static text (Baymard Institute 2016). That is the dead click in its purest form.

With inspirational images the situation has improved, but the issue has not gone away. In the Baymard Institute benchmark, 91 percent of the sites examined already consistently linked the depicted products in 2019 (Baymard Institute 2020), while 9 percent offered no easy way to the items shown (Baymard Institute 2020). During testing, some users assumed that clicking directly on a depicted product would take them to exactly that item (Baymard Institute 2020). Sites that do not offer this produce clicks that lead nowhere. How to analyse gallery and image interactions as a whole is covered in the article analysing product images and videos.

How XICTRAQ® detects both signals

XICTRAQ® captures rage and dead clicks in two places that work differently and therefore use different thresholds. The first is the click heatmap of the cookieless analytics. For every click, the tracker reports the page, the position relative to page width and height, the element type and the element’s visible label, and it flags every click with two attributes: rage click yes or no, dead click yes or no. Three clicks close together within one second count as a rage click. A click that is followed neither by a change to the page structure (DOM) nor by a navigation counts as a dead click.

The heatmap does not count links with a target or form submit buttons as dead, because they change the page or submit a form. A link with an empty jump target whose script no longer runs is therefore more likely to show up in the recording. And the tracker only counts clicks made with a mouse pointer or a finger as rage clicks: pressing Enter three times in the search field does not produce a rage click.

The heatmap itself shows the click cloud over a real screenshot for each page and device class, meaning desktop, tablet and mobile, and lists the 20 most-clicked elements with their labels. The AI assistant summarises the flags: ask it about rage and dead clicks, and for the ten most-clicked pages in the selected period it returns the totals of both signals per page alongside the number of all clicks. The heatmap view itself does not display the flags. How both signals are defined is described in the manual under form and media analytics.

The second place is session recordings. A regular job analyses every completed recording and assigns auto-tags: rage_click for three or more clicks within two seconds in a 30-pixel radius around the first click, dead_click for a click without a DOM change and without a page change within 1.5 seconds, plus error if a script error was recorded during the session. The recordings list can be filtered by these tags, and they appear as badges on each recording. The details are described in the manual for session recording.

Privacy: heatmap without cookies, recording with consent

Click capture for the heatmap sets no cookies and stores nothing in browser storage. It transmits, among other things, the page, position, device class, element type and a label shortened to 100 characters. Areas marked with the data-xictraq-block attribute deliver no text at all, areas marked with data-xictraq-mask are masked, and the tracker also obscures patterns such as email addresses, account numbers or card numbers in click texts. As a rule, this measurement does not require a consent banner; the legal assessment in an individual case remains with the operator. Background: GDPR-compliant heatmaps.

Session recording is different. It stores an identifier in browser storage for the duration of the session, and under German law storing information on the user’s device is only permitted with consent unless it is strictly necessary (Section 25 TDDDG). XICTRAQ® therefore starts recording only once it is enabled in the settings and your consent solution reports consent; recording stops if consent is withdrawn. Recordings are kept for a maximum of 90 days. How recording runs technically from your own domain and which fields are masked is explained in the article on session recording with first-party infrastructure.

<!-- Tracker: heatmap and click signals run without cookies -->
<script defer src="https://api.xictraq.com/t.js" data-site="YOUR-SITE-ID"></script>

<!-- Calls from your consent solution: record only after consent -->
<script>
  function onRecordingConsent() { xictraq.consent('granted'); }
  function onRecordingRevoked() { xictraq.consent('denied'); }
</script>

<!-- Area without text in clicks and recordings -->
<section data-xictraq-block>Customer account and addresses</section>

<!-- Text is transmitted masked -->
<span data-xictraq-mask>Customer number of the logged-in customer</span>

From signal to cause in five steps

A frustration signal is the start of an investigation, not its result. A fixed sequence has proven useful, leading from the broad overview to the individual session and only at the end to the change:

1. Narrow down the pages. Ask the AI assistant for the rage and dead click totals of the most-clicked pages and relate them to all clicks on the page. Busy pages naturally collect more signals.
2. Identify the element. Open the page’s heatmap in the right device class. If a badge, an image or a heading ranks high in the list of most-clicked elements, it is a candidate.
3. Watch sessions. Filter the recordings list under “Signal” by “Rage click” (rage_click) or “Dead click” (dead_click) and play back two or three recordings of the page. Was something still loading before the click, did the layout shift, did an error message appear?
4. Assign the cause. Distinguish three cases: the element looks clickable but is not meant to be (expectation). It should be clickable but does not respond (defect). It responds, but too late (speed).
5. Fix and measure again. After the correction, compare periods of equal length before and after. If the signals on the element drop significantly, you found the right cause.

The assignment determines the measure: with a false expectation, looking at the code does not help; with a defect, no design change helps; and with a speed problem, the cause often lies in scripts that are blocking the browser at that moment. In the graphic above, the discount label is a case of expectation, because visitors are looking for the promotion terms behind it. The size guide, by contrast, is a defect: underlined, but without a function. The following overview maps the most common combinations:

When the page responds too late

Not every rage click is caused by a dead element. Often the page responds, just not fast enough. The classic response time limits come from usability research: up to about 0.1 seconds, users perceive a response as instantaneous; up to about 1 second, their flow of thought stays uninterrupted; from about 10 seconds, their attention to the task fades (Nielsen Norman Group 1993). At one second, the heatmap threshold for rage clicks sits exactly at the second limit: anyone who clicks three times within that time is clearly signalling that they do not want to wait any longer.

There is a dedicated metric for measuring this in the browser. Interaction to Next Paint (INP) captures the delay of clicks, taps and keyboard input until the next visible response. A value of up to 200 milliseconds is considered good (Google, web.dev), a value above 500 milliseconds poor (Google, web.dev). The metric matters because most interaction happens after loading: according to Chrome usage data, users spend 90 percent of their time on a page after it has loaded (Google, web.dev). The documentation illustrates the link to rage clicks with an example: if long tasks block an accordion from opening, the user clicks several times, thinking the page is broken (Google, web.dev).

Across the web, responsiveness has improved, but secondary pages are lagging behind. In July 2025, 77 percent of websites achieved a good INP score on mobile devices (HTTP Archive Web Almanac 2025). At the level of individual pages, mobile home pages reached 80 percent (HTTP Archive Web Almanac 2025), secondary pages only 69 percent (HTTP Archive Web Almanac 2025). Secondary pages such as category and product pages are exactly where filters, galleries and form validation sit, the very elements on which rage clicks cluster. How to reduce INP in a targeted way is described in the article on optimizing INP; the free Core Web Vitals check provides a first reading.

A third cause is layout shifts. If an element slides down at the very moment the customer clicks, the click hits the wrong target. Unexpected shifts can cause users to click the wrong link or button (Google, web.dev). A Cumulative Layout Shift (CLS) of at most 0.1 is considered good (Google, web.dev). In the heatmap, this shows up as a click cloud in a spot where nothing clickable appears in the screenshot, often just below a banner or a shipping notice that loads late.

Tap targets and accessibility

On mobile devices there is another cause: the target is simply too small. Gallery dots, arrows, close buttons and quantity buttons shrink to areas of a few millimetres on a phone. The Web Content Accessibility Guidelines set a lower limit for this: under WCAG 2.2, a target for pointer input must be at least 24 × 24 CSS pixels at level AA, with exceptions such as sufficient spacing from other targets (W3C WCAG 2.2). The stricter level AAA requires 44 × 44 CSS pixels (W3C WCAG 2.2). Review rage clicks separately by device class.

Broken click targets do not only affect mouse users. A link or button without an accessible name is just as dead a target for screen reader users, except that no heatmap shows it. In the annual review of the home pages of the one million most visited websites, empty links were found on 46.3 percent of pages (WebAIM Million 2026) and empty buttons on 30.6 percent (WebAIM Million 2026). Then there are elements that only respond to the mouse, such as a div with a click function that cannot be reached by keyboard. Because the heatmap only counts pointer clicks as rage clicks, such barriers remain invisible there.

You can find them with an accessibility scan according to WCAG 2.2 and a test without a mouse, as described in the article on keyboard navigation testing. Heatmap and scan complement each other: one shows where mouse users get stuck, the other where other users never reach the target in the first place.

Checklist before Black Week

In year-end trading, every lost click weighs more heavily. For Black Friday and Cyber Monday, the German Retail Federation expected sales of 5.8 billion euros in 2025 (HDE). In 2026, Black Friday falls on 27 November. Starting to collect data now gives you a good five weeks of baseline and time to fix click traps and measure the effect. These points belong on the list:

• Check promotional areas: every banner, tile and discount label of the promotion leads to a suitable target.
• Defuse badges: labels on product images are either linked or clearly do not look like buttons.
• Clean up fake links: underlined text without a function becomes a link or loses its underline.
• Explain disabled buttons: wherever “Add to cart” requires a selection, the reason is shown right at the button.
• Feedback on click: cart, filters and quantity changes show a loading state immediately.
• Measure tap targets on mobile: arrows, dots and close buttons reach at least the level AA size.
• Click through the critical path automatically: a browser monitor checks the route from product page to checkout at fixed intervals.
• Compare signals before and after: after each correction, compare periods of equal length.

Frustration signals only reveal problems once customers experience them. For the most important paths, it is also worth having a check that does not wait for visitors: browser monitoring clicks through defined steps with a real browser and reports when a step does not deliver the expected result. What that looks like for redeeming a discount code is shown in the article on checking discount code redemption with a browser check.

Keeping click targets in view for good

Broken click targets arise continuously: with every new banner, every campaign, every plugin update. If you treat rage and dead clicks as a fixed part of your analysis, you will usually spot such breaks within a few days rather than at the end of the month in the conversion rate. A sensible rhythm for shops: review the pages with the most signals every week, check the most important product and category pages after every deploy, and work through the checklist before sale days. That way, a frustration signal becomes a task, and the task becomes a click target that works again.