Find friction
Last updated
Friction is what gets in people’s way even when nothing errors: a button that does nothing, a form that keeps rejecting an answer, a page people leave as soon as they land on it. Each one costs conversions. The Friction screen shows how often it happens, exactly where, and who it hits hardest.
You don’t need to tag anything. The SDKs capture friction signals on their own.
Friction signals
At the top of Friction, With friction shows the share of sessions that hit at least one signal. Next to it is the share of sessions with each signal:
| Signal | What it means |
|---|---|
| Rage clicks | Three or more rapid clicks on the same spot |
| Dead clicks | Something that looks clickable did nothing within 4 seconds |
| Slow controls | A control took between 1 and 4 seconds to respond |
| Error clicks | A click was followed by a JavaScript error |
| U-turns | Someone went straight back to the previous page within seconds |
| Up-and-down scrolling | Someone scrolled up and down the page four times or more within 10 seconds, as if hunting for something |
| Form errors | A field failed validation |
| Form abandons | Someone started a form and left without submitting |
Metrickle counts sessions, not clicks. One frustrated person clicking twenty times is one session, so busy pages don’t look worse than they are.
U-turns are seen on sites where every page is a full page load too, and when the back button brings a page back from the browser’s cache. That needs the last two pages remembered in the tab’s session storage, so in cookieless mode u-turns are only seen within a single-page app.
Up-and-down scrolling and accessibility settings
Only scrolling with a mouse wheel, trackpad or touch counts, and each change of direction has to move the page by at least 30% of the window (and 150 pixels). Scrolling with the keyboard, focus moving, a screen reader reading down the page, find in page and links to a part of the page never count, because they move the page for other reasons. A page that’s pinch-zoomed is skipped, since people pan around it to read. Because the distance is a share of the window, browser zoom and large text don’t make it easier to set off. It’s recorded at most once per page view.
Which platforms report which signals
- Web (script tag or npm package): every signal above. Up-and-down scrolling and u-turns across full page loads need the npm package’s next release; the script tag has them already.
- iOS, Android and Flutter: rage taps, dead taps and slow controls (counted as dead clicks and slow controls), u-turns between screens, and form errors through the
formError()helper. In SwiftUI, only controls marked with.metrickleTag()are judged for dead taps. - React Native: u-turns, rage taps and form errors, plus dead taps and slow controls on controls wrapped with
pressable().
If the screen says No friction signals in this period, update to the latest SDK or widen the date range. See Install Metrickle.
Metrickle never reads what people type into forms. Form errors record the field and the kind of validation failure.
Hotspots
Hotspots lists the specific elements, forms and pages where people get stuck, ranked by the number of sessions affected. Each row shows:
- the Signal,
- the Page it happened on,
- the Element, form or destination: the element’s selector and visible label, the form, for a u-turn the page people went back to, or for up-and-down scrolling the whole page.
Select a page in the table to filter the whole screen, and every other screen of the app, by it. Select Who hit it to list the people behind a hotspot, each opening their journey (and replay, where there is one).
If your app has accessibility scan results, a hotspot also lists what the latest scan found on the same element, linked to how to fix it. See accessibility breakdowns.
What a hotspot means
A rage click on a button and a rage click on a paragraph are different problems. Each hotspot says, in plain words, what it most likely means for the people who hit it:
| Meaning | What people ran into |
|---|---|
| Looks clickable but isn’t | They clicked something that looks like a link or button but isn’t one. Make it one, or stop it looking clickable. |
| Doesn’t respond | A real control did nothing visible, or not fast enough to tell. |
| Doesn’t work with a keyboard | People pressed Enter or Space on it and nothing happened. That likely fails WCAG 2.1.1 Keyboard, so it’s marked as an accessibility failure. |
| Too slow to respond | It took over a second to react, so people clicked again or gave up. |
| Breaks when clicked | Clicking it set off a script error. |
| Wrong page | Most people left within 2 seconds and went back. The link that brought them promised something else. |
| Not what they hoped | Most people looked for 2 to 7 seconds, then went back. The page answered the wrong question. |
| Hunting for something | People scrolled up and down the page again and again. Put what most people come for near the top, with a clear heading or a link to it. |
| Gave up at the start | Most people left the form after the first field. Ask for less up front, or say why you need it. |
| Gave up part-way | People filled in some fields, then left. Something later in the form stopped them. |
| Rejected their input | A field kept failing validation. Say what’s expected before they type, and keep what they entered. |
| Trying to select text | Three quick clicks on text is how people select a line. They likely wanted to copy it: add a copy button. |
The web SDK from version 0.3 records whether the clicked thing was a real control, only styled to look clickable, or plain text. Older SDKs and mobile apps leave Metrickle to judge from the element’s name, which is less certain. Update the SDK for the most accurate meanings. See Install Metrickle.
Pages and screens
Pages and screens shows, for each page, how many sessions it had and the share of them that hit any friction signal there. Use it to find the page with the most friction, then look at its hotspots.
Who friction hits
The Accessibility card compares friction and conversion for people using each accessibility setting, such as keyboard navigation, a screen reader, zoom or large text, against sessions with no accessibility settings. The difference is shown in percentage points. A session can have several settings.
A dead click that a mouse user shrugs off can stop someone on a keyboard. Select a segment to filter the whole screen to those sessions.
You can filter friction in other ways too: by device, campaign, country or any other breakdown. See the dashboard tour.
Ask them why
The numbers say what people did. Only people can say why. Each hotspot has two links:
- Survey them opens a new survey draft, shown right after the same moment to the same people. For a dead click on a button, that’s a short question on that page, straight after someone clicks that button. You can change anything before you save it.
- Plan a study opens a new study draft with the hypothesis written down, such as “People expect this button to do something, and give up when it doesn’t.”
Nothing goes live until someone with permission puts it live. See surveys, feedback and studies.
Surveys need to remember who has already answered, so they never reach visitors in cookieless mode. If most of your visitors are cookieless, Metrickle offers a study instead.
The same links appear on Converters and next to doubt before deciding.
Create an issue from a hotspot
When you’ve found a problem worth fixing, send it to your issue tracker without leaving Metrickle.
- In Hotspots, select Create issue on the row.
- Metrickle drafts a Title and Description from the hotspot. Edit anything before it is sent.
- Select Create issue.
The issue goes to the tracker connected for this app, such as Linear, GitHub, Jira or GitLab. If none is connected, the dialog tells you, and someone with permission can connect one under Integrations. See integrations. Filing issues needs the permission to file issues in a connected tracker.
Check whether the fix worked
Select Fixes in your app to see every issue created from Metrickle: from friction hotspots, feedback, tasks and cases.
Metrickle records the issue’s metric over the 7 days before it was opened. Seven days after the issue is closed, it measures the same metric again and shows before and after. Each issue has a status:
| Status | Meaning |
|---|---|
| Open | The issue isn’t closed yet |
| Measuring | Closed, with the result due 7 days after closing |
| Fix worked | The metric improved |
| No improvement | The metric didn’t improve |
| Cancelled | The issue was cancelled in the tracker |
The top of the list says how many measured fixes improved their metric. You can also be notified of fix results: see notifications.
Next steps
- See it happen in heatmaps and replays
- Ask people what went wrong with surveys and feedback
- What slowness costs
- Protect a task so the next release that adds friction opens a case