What rage clicks really mean.
Someone pressed the same thing over and over, fast. Usually that means they expected something to happen and saw nothing. It is one of the few signals that points at a single button.
3 sources, each one read in October 2026 and linked at the bottom.
THE SHORT ANSWER
The quick version.
A rage click is several fast clicks on one spot. It usually means a person pressed something and nothing seemed to happen: a slow button, something that looks pressable and is not, or an invisible layer in the way. Go and press the thing yourself, on a phone.
THE NUMBERS
How the tools define it.
3 clicks, 1 second
is Moxel's rule: three or more clicks on one spot inside a second. Moxel
More than 3
clicks on one element inside a one-second window is Datadog's. Tools draw the line in slightly different places, so counts from two tools will not match. Datadog
Multiple clicks
in a clustered area in rapid succession is Clarity's rule. It also flags dead clicks, a click that gets no feedback in a reasonable time, as a separate signal. Microsoft Learn
5 causes
are on Fullstory's list: not knowing whether something can be clicked, buttons that do not work, broken elements, misleading content and invisible overlays. It also describes dead time, the wait for a page or a server to answer. Fullstory
Not proof
is Fullstory's own caution. A rage click can be user error or a sign of a real problem, and it takes a closer look to tell which. Fullstory
WHAT TO CHANGE
Why it happens, and the fix for each.
01The button works, but does not show it
The press went through and the page is working on it. With nothing on screen to say so, people press again. Fullstory calls the wait dead time. Fullstory
TRY THISChange the button the moment it is pressed: a spinner, a new label, or grey it out until the answer comes back.
02It looks pressable and is not
Underlined text that is not a link, a picture that looks like it should open, a card with a shadow. People press what looks like a button. Fullstory
TRY THISEither make it do what people expect, or take away the styling that says it will.
03Something invisible is in the way
A cookie bar, a chat bubble or a sticky header can sit over a button and swallow the press, often only at phone width. Fullstory
TRY THISOpen the page on a phone and press the exact thing. If the press lands on something else, move or shrink whatever is on top.
04The target is too small for a thumb
On a phone a rage click is a rage tap: the same spot tapped again and again. Small links set close together, a tiny close button on a pop-up, or a checkbox with no tappable label all miss the first time.
TRY THISMake the thing bigger, or make its label tappable too. Then try it one-handed on your own phone.
05It is broken
Sometimes the plain answer is the right one. The button fails, or it only fails in one browser.
TRY THISPress it in the browser most of your visitors use, then in another one. If nothing happens, that is your answer, and whoever built the site can find out why.
06It was not anger
One person pressing fast is not a pattern. The count matters more than the name. Fullstory
TRY THISLeave a single rage click alone. Look when the same button collects them from several visits.
ON YOUR OWN SITE
From angry clicks to a line on a list.
Moxel waits for enough evidence, then writes the finding with the element named and the fix beside it.
Pay button, checkout
reading sessionsHero, home
reading sessionsGift cards page
reading sessionsRage clicks are recorded at Feral only. Moxel notes the label of the thing that was pressed, cut to 60 characters with emails and long numbers hidden, and the fix list names it once it has happened more than once. Moxel has no session recordings, so it cannot show you the moment. It tells you which button, and you go and press it. It also does not record dead clicks, the single press on something that does nothing.
THE LIMITS
What this cannot tell you.
The sources here are companies that sell this measurement, describing their own rules. There is no independent count of how often a rage click points at a real fault. Treat one as a reason to go and look, never as the verdict. On a small site a handful of them is a hunch.
QUESTIONS
Asked a lot.
- What is a rage click?
- Several fast clicks or taps on the same spot. Moxel counts three or more inside one second. It usually means the person expected something to happen and saw nothing.
- What is the difference between a rage click and a dead click?
- A dead click is one press that gets no response: nothing on the screen changes and the page does not move on. A rage click is many fast presses on one spot, often what follows a dead click. Clarity reports both. Moxel records rage clicks at its Feral depth and does not record dead clicks.
- What is a rage tap?
- A rage click on a phone or tablet: the same spot tapped several times fast. Most tools count it the same way as a click. Moxel does too, because a tap reaches the page as a click.
- How do I find rage clicks on my site?
- You need a tool that watches for them. Microsoft Clarity is free and shows rage clicks and dead clicks with recordings of each. Moxel counts them at its Feral depth and names the button. Without a tool, press every button on your key pages on a phone and watch for anything that does not answer straight away.
- Are rage clicks always a bug?
- No. Fullstory says a rage click can be user error or a sign of a real problem. Look for the same button collecting them across several visits before you change anything.
SOURCES
Where the numbers came from.
- Rage clicksFullstory, March 2022. Fullstory sells a tool that measures rage clicks.
- Frustration signalsDatadog. Product documentation, describing Datadog's own rule.
- Semantic metrics (Clarity)Microsoft Learn, December 2025. Product documentation, describing Clarity's own rules. Clarity is free.
Read in October 2026. Studies get updated, so follow the link for today's figures.
KEEP READING
More from the field guide.
- Why people leave in ten seconds
- Why people abandon forms
- Why people abandon checkout
- How far people really scroll
- Analytics for vibe coded apps
- Your website stats in plain English
- Analytics without a cookie banner
- How to track form abandonment
- Shopify traffic but no sales
- Where people drop off in checkout
- Should the phone field be required?
How Moxel records all of this is in the docs. What it never records is on the privacy page.