Analytics

U-Turns, Error Clicks, and Thrashed Cursors — A Glossary of Frustration Signals

A plain-English glossary of the behavior patterns that reveal a struggling user, including rage clicks, dead clicks, error clicks, u-turns, thrashed cursors, and form re-entry, with what each one usually means.

Purushottam Kumar Suman
Purushottam Kumar SumanSeptember 14, 20268 min read
Founder & CEO, DeepSync
Interface showing user frustration signals

Short answer: frustration signals are patterns of behavior that suggest a visitor is struggling: clicking repeatedly, clicking things that do nothing, going back immediately, shaking the cursor, or retyping the same field. No single signal is proof. Several together, on the same element, almost always mark a real problem.

Table of Contents

  1. The Signals
  2. Quick Reference
  3. False Positives
  4. How to Use Signals Well
  5. Frustration Signals in DeepSync
  6. Key Takeaways

The Signals

Rage click

Several rapid clicks on the same spot. The visitor expects a response and is not getting one. Usual causes are a slow response, a broken button, or an element that looks interactive and is not. More in what are rage clicks.

Dead click

A click that produces no response at all: no navigation, no change on the page. Common on images people expect to enlarge, headings that look like links, and disabled buttons with no explanation. See dead clicks explained.

Error click

A click followed immediately by a JavaScript error. This is the clearest signal of the lot, because the page has confirmed that something broke.

U-turn

Navigating to a page and returning almost immediately. Also called a quick back. The destination was not what the link suggested. Common causes are a misleading label, a slow page, or content hidden behind a login.

Thrashed cursor

Rapid, erratic mouse movement, often side to side. It tends to appear while someone waits for a slow page or cannot find what they are looking for. It is desktop only and the least reliable signal on its own.

Form re-entry

Clearing and retyping the same field several times. Usually caused by a strict format, an unclear error message, or validation that rejects something reasonable.

Repeated submit

Pressing the submit button multiple times. Either nothing visible happened after the first press, or an error was shown somewhere the visitor could not see.

Excessive scrolling

Scrolling up and down a page repeatedly. The visitor is searching for something the page should have made easy to find.

Dead end

Reaching a page with no obvious next step and leaving. Common on empty search results, error pages, and confirmation pages with no onward link.

Pinch and zoom

On mobile, zooming in to read or to tap. Text is too small or targets are too close together.

Quick Reference

SignalWhat you seeMost likely cause
Rage clickFast repeated clicksNo response, slow response
Dead clickClick, nothing happensLooks clickable, is not
Error clickClick, then an errorBroken code
U-turnBack within secondsMisleading link, slow page
Thrashed cursorErratic movementWaiting or lost
Form re-entryRetyping a fieldStrict validation
Repeated submitMany submit pressesNo feedback, hidden error
Excessive scrollingUp and down repeatedlyCannot find information
Dead endArrive, then leaveNo next step
Pinch and zoomZooming on mobileSmall text or targets

False Positives

  • Rage clicks on a carousel arrow, a quantity stepper, or a game are normal use.
  • Dead clicks include people highlighting text to read or copy it.
  • U-turns are routine when comparing products from a listing page.
  • Thrashed cursors include people who simply move the mouse while reading.
  • Repeated submit can be a double-click habit.

This is why a count alone is not a finding. Open a few sessions before raising a ticket.

How to Use Signals Well

  1. Rank by sessions affected, not by total events.
  2. Look for clusters. The same element appearing across many visitors.
  3. Prioritise by page. A rage click on checkout matters more than one on a blog post.
  4. Combine signals. A rage click with an error is nearly certain to be a real fault.
  5. Watch the session to confirm.
  6. Track the rate after a fix. It should fall.

Start with error clicks on money pages

Sessions that reached checkout and hit a JavaScript error are the shortest route to a fix that pays for itself.

Frustration Signals in DeepSync

  • The session list shows quick signals on every row, including rage-click and dead-click counts and a frustration score, so you can choose what to watch (session filters).
  • Highlights in the player surface the moments most likely to matter, such as rage clicks, errors, and dead ends (session replay).
  • Friction and rage-click detection is available on Pro and above, with errors and friction insights bringing the two together.
  • JavaScript errors link straight to a session where each occurred.

Key Takeaways

  • Frustration signals are patterns, not proof.
  • Clusters on the same element across sessions are what matter.
  • Error clicks are the strongest single signal.
  • Confirm in recordings and track the rate after fixing.

Conclusion

Visitors rarely tell you they are frustrated. They show you, in small repeated gestures. Learning to read them is the fastest way to find what to fix.

Explore rage click detection.

Frequently Asked Questions

Was this article helpful?

Ready to understand
users like never before?

Join thousands of teams who use DeepSync to uncover insights,improve experiences, and build better products—faster.

Quick & easy onboarding
See results in real time
Enterprise-grade security