Rage Clicks & Error Clicks – Say Goodbye to Frustration

Rage Clicks & Error Clicks – Say Goodbye to Frustration

Frustrating user experience can be improved faster than you think.

If you’re familiar with our guide to understanding user frustration, you’ve already read a thing or two about rage clicks and error clicks. In this blog post, we’re going to cover this topic in more detail. You’ll learn:

  • what are rage clicks and error clicks
  • how you can filter them with session tracking tools like LiveSession
  • how detecting error and rage clicks can help you spot some of the most important issues on your website

Ready to say goodbye to frustration? Let’s dive in!

What are rage clicks

A situation like this one probably sounds familiar to you:

You’re on a website, trying to complete a goal. You finally found the button you’re looking for: Proceed, Buy now, Read more – you name it.

Then, you try to click on it.

Nothing happens.

You click again. Still, nothing happens.

Click, click. Click, click, click, click.

A disaster you’d rather avoid, right?

You get angry and keep clicking even more, even faster.

This is what we call a rage click. It happens when a user clicks (or taps) on a specific section of a website repeatedly, very fast, in frustration. You could also say that it’s a digital parallel of pressing the elevator button a couple of times in a row when it’s not responding. Overall, a rage click is a very clear signal that your visitor wasn’t able to achieve their goal.

What are error clicks

Rather than being related to an emotional reaction, error clicks are based on technical issues. In LiveSession, we’re talking about an error click when a JavaScript error occurs.

If you’re not particularly tech-savvy and this term doesn’t sound clear to you, here’s a quick explanation:

JavaScript (often abbreviated as JS) is one of the most popular programming languages used to build web pages. A popular metaphor claims that this language was made to “make pages alive”. When a particular JS element is not working, it means you’re dealing with a JavaScript error.

In this case, the user doesn’t have to click on something many times in a row. Just one click is enough for the tracking tool to detect an error. What’s more, sometimes the users don’t even notice that something is broken within the app. Most of the time, however, error clicks indicate that you need to prioritize the issue.

How to filter rage clicks and error clicks with LiveSession

LiveSession detects error clicks and rage clicks automatically. You can find all the sessions with these types of clicks very easily – all you need to do is select a filter from the drop-down menu


If needed, you can use more advanced filters, too. Rage clicks can be filtered based on the CSS selector or text, while error clicks can also be sorted according to a specific type of error:


If you would like to read more about using filters in LiveSession, ourguide to user segmentation is sure to come in handy.

How rage clicks and error clicks can help you spot important issues

In this part of the article:

  • we’ll cover some of the most common appearances of rage and error clicks
  • you’ll learn how to draw conclusions from the events recorded with a session tracking software

Let’s dive deeper to find out how to leverage rage click and error clicks in your user research strategy!

When rage clicks occur

Some of the most common occurrences for rage clicks include:

Dead links

Rage clicks happen when a text looks like a hyperlink (e.g. it’s in a different color, in bold or underlined) but it’s not really clickable. Oftentimes, the user is certain that they’re dealing with a link and keep clicking on it, expecting to be redirected to a different page.

Unclear error messages

When a user is filling a form and they got the postcode format or their credit card number wrong, they might not be able to proceed. If the error message is not clear, they will keep clicking on the Proceedor Send button repeatedly, until they realize that something is wrong, or worse, leave the page.

Desire paths

Sometimes users are expecting certain elements to act in a certain way (in this case, to be clickable), yet the website behaves differently. Still, the user is trying to follow the expected path – a desire path, also known as goat track or bootleg trail. This term is best explained with one of the most popular examples in the history of UX:


In this case, the user doesn’t want to take the established road and chooses the shortcut instead, just because it’s faster and more natural.

Desire paths can be based on the expectations, too. For instance, if the user goes on your company blog and clicks on the logo of your product in the top left corner, they probably expect to be taken back to the main page. If the logo is not clickable, they might try to click on it again, and again – and here goes our rage click.

An example from our blog – the users are likely to click on the LiveSession logo, expecting to be redirected to the home page. If the logo is not linked, they may click on it a couple of times, until they realize the pattern is not working.

Speed issues

A rage click may also indicate that a particular element of your page takes too long to load. What’s more, this phenomenon may occur when the entire page is loading and the user keeps clicking on the loading screen to see if something will happen. Keep in mind that this is more likely to happen if a slow response comes with an unclear message – the user gets lost and keeps clicking to get any kind of feedback.

Most of the time you can take action to improve the page speed, yet sometimes the fault lies somewhere else. In that case, we’re talking about false rage clicks.

False positive rage clicks

It might happen that a rage click is detected when it’s not related to the interface design. We call it a false positive rage click, which might be due to a poor internet connection or a lagging device. It always pays off to double-check a recording to see if a rage click is caused by an external reason or maybe there is something that can be improved on your website.

When error clicks occur

As mentioned above, error clicks are logged based on JavaScript errors. When the user notices that a particular element is broken, they might start clicking on it repeatedly. This is why error clicks are often registered together with rage clicks, like in the example below:


In such cases, you can see that the visitor was frustrated and you can also see what kind of error caused the frustration. When you have complete information handy, it’s much easier to start working on the bug.

Key takeaways

Rage clicks and error clicks detection is a handy feature designed to help you spot the most urgent issues as soon as possible. You don’t have to search manually to find the main points of frustration. Instead, your session recording app will keep track of them automatically. This makes work much smoother for everyone involved, including developers, UX designers and customer service agents.

If you’re not monitoring the frustration of your users yet, it’s high time you started paying more attention. It’s a simple and efficient way to learn more about your visitors and improve their experience – and in the end, this is how you make your customers happy and loyal.

Want more knowledge?

Get more tips and insights on UX, research and CRO. Zero spam. Straight to your inbox.