Harvv Research

What is a rage click?

Several fast taps on one spot. Every analytics vendor defines it. None of them says how often it happens, or where. We measured it on a sample of 2,534,020 real sessions.

0.94%
of sessions on the median site contain a rage click
38%
of rage bursts land on a button element
5.3×
higher conversion in sessions with a rage click (they are longer sessions)

0.94%. 38%. 5.3 times. Those are the three numbers in this post. Here is the twist in the second one: people rage on real buttons, not on dead decoration.

Picture the add-to-cart button on a product page. It is a real button, wired to a real handler, and it adds the item every time. Someone taps it. The page says nothing for half a second. They tap again, and again, and the cart now holds three. Who tests the half second after the tap? Nobody. It is not a bug. It is a silence.

Harvv is a pixel that measures that silence. Clarity and Fullstory record people so you can watch them. Harvv turns behaviour into data an AI can read: you ask why conversion dropped on Tuesday and it answers with the element, the page and the fix. The rage click is one of the signals it reads, and this post is what that signal says across the sample.

How often, measured

The median site in the sample has a rage click in 0.94% of sessions. The middle half of sites sit between 0.72% and 1.79%. The quietest is at 0.04%, the loudest at 4.7%. Desktop rages more than mobile, with more rage clicks per rage session: a mouse makes three clicks in under a second easy, a thumb does not. Tablets read highest, on about 4% of sessions, so read that row as a rough guide.

DeviceSessions with a rage clickSessionsRateRage clicks per rage session
Mobile13,9782,047,2580.68%2.5
Desktop5,751380,1321.51%3.3
Tablet3,276101,7203.22%3.1

The surprise

Sessions with a rage click converted at 2.2% (500 of 22,861). Sessions without one converted at 0.4% (10,310 of 2,511,159). Rage sessions ran a median of 207 seconds against 22. Longer sessions do more of everything, including buying, so this is not a cause. What it says is that the visitors who stay long and get close to buying are the ones most likely to hit a slow control. 97.8% of rage sessions still did not convert.

Where it lands

We looked under every rage burst in the sample for 14 days to 6 October 2026: 9,998 bursts. The story is that rage clicks land on dead elements. Mostly they do not.

Element under the burstBurstsShare
A real control (button, link, linked image)4,04840%
Plain containers and text (div, span, li)2,27423%
Icon glyphs (svg, path, i)2,08721%
Images3063%

Four in ten rage clicks are on a real control, not on something that cannot be clicked. Whether each one worked was not checked; the likely problem is the half second after the tap. Three causes are common.

A real button that answers too slowly

38% of rage bursts land on a button element. Even a working button gets tapped again when its answer shows after the second tap.

Fix: Show a pressed state or a spinner inside 100 milliseconds, then fix the long task behind the delay.

An icon that swallows the click

21% land on an svg, path or i element: the glyph inside the button took the tap and the button never heard it.

Fix: Set pointer-events: none on the icon. The button is the target, not the drawing on it.

A card that looks tappable and is not

23% land on a div, span or list item: the padding around a control, or a product card where only the title is the link.

Fix: Make the whole card the link. A real <a href> or <button> also gives you keyboard and screen-reader access for free.

What the tools call it

Four vendors publish a definition. They agree on the shape, and most do not publish the numbers that make it a rule. Sentry does: 3 or more clicks within 7 seconds. Two tools on one site count different rage clicks.

ToolTheir words
Microsoft Clarity"Rage clicks occur when a user repeatedly clicks in a clustered area within a short period."source
FullstoryRage Clicks "are logged when end users click multiple times rapidly in the same area."source
Pendo"Rage clicks are repetitive clicks on a specific element in a software application, often caused by user frustration."source
Sentry"Rage clicks are a series of consecutive clicks on the same unresponsive page element."source
Harvv3 clicks within 800 milliseconds, all inside a 50 pixel radius. A burst on a text field, a number field's arrows, a slider or a select is someone editing a value, and a burst that selects text is a triple-click; neither counts. The rule is read from the pixel's source each time this page is built.

The pattern

Every site in the sample has a button like this. Not a broken one. A quiet one. And it is nobody's job to find it: the developer sees the handler fire, the designer sees the mock, the analytics dashboard sees a click. Only the visitor sees the silence, and they do not file a ticket. They tap three times, and either buy anyway or leave.

Which button on your site is the quiet one?

Questions people search

What is a rage click?

Several fast clicks or taps on one spot, the way a person presses a button again when nothing seems to happen. Harvv counts 3 clicks within 800 milliseconds inside a 50 pixel radius. In a sample of 2,534,020 real sessions, the median site saw one in 0.94% of sessions.

What are rage clicks in Clarity?

Microsoft Clarity’s FAQ: "Rage clicks occur when a user repeatedly clicks in a clustered area within a short period." Clarity shows them as a recording filter and a heatmap. It does not publish the click count, window or radius it uses, so two tools on one site count different rage clicks.

In Pendo, what is a rage click?

Pendo’s glossary: "Rage clicks are repetitive clicks on a specific element in a software application, often caused by user frustration." Pendo measures inside web apps, not public sites.

What does "dead clicks" mean?

A dead click is one click that gets no response at all. A rage click is several in a row. They rarely travel together: 6.7% of sessions with a rage click also had a dead click. Most rage clicks land on real controls (buttons and links), not on elements that cannot be clicked.

What is a good rage click rate?

Under 1%. In our sample the median site had a rage click in 0.94% of sessions, the middle half of sites sat between 0.72% and 1.79%, and the worst was at 4.7%. Above 2% may mean one control is misbehaving. Find the element, not the average.

Are rage clicks bad for conversion?

Sessions with a rage click converted at 2.2% (500 of 22,861). Sessions without one converted at 0.4%. Longer sessions do more of everything, so this is not a cause: visitors who stay long and get close to buying are the ones most likely to hit a slow control. 97.8% of rage sessions still did not convert.

Method: sessions table, 90 days to 7 October 2026, a sample of sites with at least 1,000 sessions each after excluding sessions classified as bots or internal; per-site rates, then the median and quartiles across sites. Element shares from rage events in the 14 days to 6 October 2026. Vendor definitions quoted from each vendor's own page on 8 October 2026. The detection rule is read from the pixel source at build. Related: what is a dead click, why people add to cart and do not buy, how far people scroll on each kind of page.

How this was written. The numbers come from Harvv's own data. I drafted this post with an AI assistant, checked every number against the query that produced it, and edited the final text.

Install it. Give it a week. Ask it which button.

One script, 72 event types across 10 categories, no recordings or form values. Free for 3 sites, no card.