Learn

The UX friction glossary

Users report broken interfaces through behavior, not tickets. These are the signals, what each one means, what causes it, and what to do about it.

Behavioral analyticsBehavioral analytics is the measurement of how users interact with an interface, their clicks, hesitations, retries, scrolling, and struggles, rather than just which pages they visited. It answers quality questions that pageview analytics cannot: not where users went, but how it went.
Bounce rateBounce rate is the percentage of sessions that end after a single page with no further interaction. It is easy to measure and hard to interpret, because a visitor who found their answer instantly and a visitor who left confused produce the same bounce.
Confusion scoreA confusion score is a per-page metric that rolls the frustration signals on that page, weighted by severity and reach, into one number tracked against the page's own baseline. It exists so friction can be ranked, alerted on, and compared before and after deploys.
Cursor thrashingCursor thrashing is rapid, erratic mouse movement without productive clicks: the cursor sweeping back and forth across a page as a user searches for something to act on. It signals a user who is lost on the page rather than blocked by any single element.
Dead clickA dead click is a click on a page element that produces no response: no navigation, no state change, no feedback of any kind. Dead clicks reveal elements that look interactive to users but are not, or interactive elements that have silently stopped working.
Form abandonmentForm abandonment is when a user begins filling out a form and leaves before submitting it. Abandonment is almost never spread evenly across a form; it concentrates at one field, and finding that field is the entire diagnostic problem.
Frustration signalsFrustration signals are measurable behavioral patterns, like rage clicks, dead clicks, cursor thrashing, and navigation loops, that indicate a user is struggling with an interface. They surface broken and confusing experiences without recording screens or capturing personal data.
HeatmapA heatmap is an aggregate visualization of user activity on a page, most commonly clicks, cursor movement, or scroll depth, rendered as color intensity over a screenshot. Heatmaps show where attention goes; they need behavioral context to explain why.
Interaction to Next PaintInteraction to Next Paint (INP) is a Core Web Vital that measures how long a page takes to visibly respond after a user clicks, taps, or presses a key. It replaced First Input Delay in 2024. Slow INP is a leading cause of rage clicks and double submissions.
Layout shiftLayout shift is when visible page content moves after it has already rendered, usually because something else loaded late and pushed it. Shifts cause misclicks, and misclicks on moved buttons are a reliable source of rage clicks and accidental actions.
Navigation loopA navigation loop is a user moving back and forth between the same small set of pages without progressing toward a goal. Loops mean the user is searching for something your navigation promises but does not deliver where they expect it.
Rage clickA rage click is three or more rapid clicks on the same spot or element, made by a user who expected something to happen and got nothing. It is one of the clearest behavioral signals that part of an interface is broken or unresponsive.
Session replaySession replay is a technique that records a user's interactions and DOM state so their session can be replayed as video. It is useful for debugging specific reported issues, and it carries trade-offs in scale, analysis cost, and privacy.
UX frictionUX friction is any point in an interface where a user has to work harder than necessary to reach their goal: an unclear control, a slow response, a confusing flow, a form that fights back. Friction compounds quietly and exits users before they convert.
UX regressionA UX regression is new friction introduced by a code release: an interaction that worked before the deploy and confuses, blocks, or slows users after it. Most UX regressions pass every test and throw no errors, so they surface only in user behavior.