Skip to content
Open fromusers

Usability metrics

Usability tests

Usability metrics turn interactive tasks into evidence: whether people succeeded, how long they took, where they clicked, and which paths they followed.

MetricMeaning
Task successParticipant met success criteria (URL, destination, or configured rule)
Time on taskDuration spent before success, fail, or abandon
Path analysisSequences of screens or clicks across the prototype
Click heatmapWhere clicks clustered on a screen
First clickInitial click distribution for first-click tests
Scroll mapScroll depth for free exploration when available

Details by question type: Charts by question type.

  1. Open the usability test Results.
  2. Use Dashboards for per-task charts.
  3. Open Responses → View session (and View recording on Pro when enabled).
  4. Filter to completed sessions before you trust rates.
  • High success + high time → usable but costly.
  • Low success + heatmaps on the wrong control → discoverability issue.
  • Divergent paths with eventual success → unclear information architecture.
  • Always sample recordings; metrics alone miss hesitation and mutterings (with participant recording).

Metrics only reflect the success criteria you configured. If criteria are wrong, numbers mislead. Preview detection before Live.

  1. Sort tasks by lowest success rate.
  2. Open path analysis for that task.
  3. Inspect the heatmap on the step with most misclicks.
  4. Watch three failing recordings.
  5. File design issues with screenshots from the heatmap export.
  • Prototype permission failures look like participant struggle.
  • Extension-based website success depends on install (browser extension).
  • Coffee studies without recording still show interaction charts when clicks were captured, but lack video evidence.

Common questions

Which metrics appear for goal-based tasks?

Expect task summary (success vs fail), path analysis, click heatmaps, and timing signals when interaction data was collected.

Do heatmaps require Pro?

Interaction charts appear when tasks collect click data. Screen recordings and transcription are Pro capabilities.

Why is success low but recordings look fine?

Recheck success URL or destination rules. Strict criteria can mark successful behavior as failed.