Skip to content
Hoot Lens.Start free

How do I find rage clicks on mobile?

In Hoot Lens, rage clicks are called pile-ups: three or more clicks or taps on the same spot within a second. Filter your visits to phones and to visits with snags, open the elements with the most pile-ups in the mobile heatmap, and watch the replays, which draw taps, long presses and swipes in place of a cursor. Hoot Lens records websites in mobile browsers. It has no SDK for native iOS or Android apps.

Markdown copy

What you need

Hoot Lens installed on the site (one tag, see the install guide) and some visits from phones. Hoot Lens sorts visits into three device classes from the width of the viewport: mobile is narrower than 768 pixels, tablet is 768 to 1023 and desktop is 1024 or wider. It never buckets by exact pixel size, and heatmaps for the three classes are always kept separate.

Steps

  1. Open Recordings, choose Phones, and turn on Has snags. Each visit opens with a one-sentence summary of its device, pages, scroll and snags, and the snag badges name pile-ups, no-shows and misfires.
  2. Open Heatmaps and choose a page and the mobile device class. The elements table lists the most clicked elements, with a count of pile-ups, no-shows and misfires for each.
  3. Choose an element with pile-ups. Hoot Lens outlines it on the page snapshot, which is drawn at the phone's proportions.
  4. Open one of the example replays. From a snag example, the replay opens two seconds before the click. A tap shows as a ripple, a press held half a second or more as a dashed ring, and a swipe as a short trail.
  5. Compare with no-shows on the same element. A pile-up on an element that also has no-shows suggests the taps changed nothing visible. Check that the control gives immediate feedback, that no overlay or sticky bar covers it, and that its tap target is large enough.
  6. Fix one thing, log the change, and check the result with "Did it help?" on the mobile device class. See how to test a landing page change without an A/B tool.

Ask your coding agent to do it

With the Hoot Lens connector at https://mcp.hootlens.com/mcp (see how to give your coding agent real user behavior data), these are the exact tool calls.

list_projects {}
list_sessions { "projectId": "PROJECT_ID", "deviceClass": "mobile", "signal": "rage", "limit": 10 }
review_findings { "projectId": "PROJECT_ID" }
get_heatmap { "projectId": "PROJECT_ID", "key": "MOBILE_COHORT_KEY" }
get_session_narrative { "projectId": "PROJECT_ID", "sessionId": "SESSION_ID" }

signal takes rage for pile-ups, dead for no-shows and error for misfires. In review_findings and list_heatmaps, pick cohorts whose key ends in the mobile device class. get_session_narrative returns the visit's facts (device, browser, pages, deepest scroll, clicks, pile-ups, no-shows and misfires) and a short summary.

How much to trust it

A pile-up is a counted pattern of clicks, not a reading of emotion. Treat fewer than ten as a lead and fewer than thirty as weak, and report the count and the recording ID with each claim. Visits from automated tools are flagged and left out of counts. Your own test taps will show up too, so mark deliberate test visits with the variant controlled-validation to keep them out of heatmaps, findings and traffic.

See it on your own site

Free to start. Add one line, and your first visits show up within minutes.

Start freeSee the example workspace