Docs Find and fix real problems
Find where users get stuck or rage-click
Relia spots clicks that do nothing, repeated clicks and pages people get stuck on, and suggests what to change in your UI, with real visits as proof.
Not every problem is an error. Sometimes nothing is broken, but people click something that doesn't respond, press a button again and again, or go back and forth without getting anywhere. Relia finds these places from real visits and tells you what to change.
The example is Relia's demo shop: on the product list, people click a row and nothing opens; on search, people press Search several times because nothing shows it's working.
Before you start
Relia's browser SDK in your web app. See Watch your web app. It records clicks, pages and form submits, never the text people type.
What you'll see
- Home may still say All good: nothing is broken. Under What to change in the UI, Relia lists its top suggestions. All suggestions opens the full list.
- When the friction is strong, it also becomes an incident, for example Users rage-click 'Search' on /search or Users get stuck on /checkout. Friction alone needs at least 3 different people before it Needs you; with fewer it's Watch or less, because two people is often your own team testing.
Find the cause
Open Users, then UX issues (or click All suggestions on Home). This page shows where people struggle: clicks that do nothing, repeated clicks, pages they get stuck on.
Read What to change. Each suggestion comes from at least 3 people or at least 5 occurrences, and names the place, how many people and the change to make. The kinds are:
Suggestion What people did Rows people expect to open Clicked rows of a table or list, and nothing opened. Looks clickable, does nothing Clicked something that looks like a link or button but isn't. No feedback after pressing Pressed the same button several times quickly (rage clicks). People get stuck Repeated actions on a page without moving forward. Back and forth between pages Went between the same pages again and again. Slow page Waited on a page that loads slowly. Watch the proof. Open one of the example visits. The timeline shows exactly what happened, for example four presses on Search within one second. In a visit's timeline you can filter to Rage Clicks or Dead Clicks.
Tip: watch Visitors, sessions and Core Web Vitals explained (2 min).
Fix it
The suggestion says what to change. Typical changes:
- Rows that don't open: make the whole row open the item, or make the name a clear link, and show a pointer cursor on hover.
- Buttons pressed again and again: show a loading state as soon as the button is pressed, and disable it until the answer comes back.
- Things that look clickable: make them work, or style them so they don't look like links.
- Stuck pages: walk through the page yourself on a phone and a slow connection; look for a hidden error message or a step that isn't clear.
Check the fix worked
- Suggestions: once your change is live, click Done on the suggestion. If people still hit the same thing a day later, it comes back. Not a problem hides it for good.
- Incidents: click I fixed it on the incident. Relia watches real visits and, once the friction stays away for 30 minutes, says Fix confirmed and sends Your fix worked.
Next
Last checked against the product: 1 Nov 2026