Skip to content
Open fromusers

First click test

Usability tests

A First click test shows a prototype screen and asks where participants would click first to achieve a goal. The first click is the signal; you are not scoring a full multi-step completion path.

Use first click tests to evaluate navigation entry points, homepage modules, or key CTAs before investing in longer tasks. Use a Goal-based task when you need end-to-end success. Use a Five-second test when the question is about memory and impression after a brief exposure, not a click target.

  1. Open a usability test → Build → Form.
  2. Add a page or use the First Click Task template.
  3. Choose First click test from interactive tasks.
  4. Enter the First click question (task prompt) and bind the prototype screen.

Not available in surveys or in-product surveys.

SettingOptionsNotes
First click questionTask promptGoal-oriented instruction
PrototypeBound screen/assetThe stimulus for the first click

“Where would you click to change your notification preferences?” Prototype screen: Account overview. Do not mention the gear icon in the prompt.

First click results typically include:

  • Click heatmap
  • Click areas
  • Time analysis

High agreement on the intended control is a strong early signal. Scattered first clicks suggest label or hierarchy issues.

  • Test one goal per screen for cleaner interpretation.
  • Avoid leading language that points to the correct region.
  • Follow contested first clicks with a goal-based task on the revised design.

Common questions

What does a first click test measure?

It captures the first click for a stated goal on a prototype screen, then summarizes locations with heatmaps and timing.

Is first click available outside usability tests?

No. It is an interactive task for usability tests only. Surveys and in-product surveys cannot include it.

How should I write the question?

State the goal clearly and avoid naming the correct control. Participants should decide where to click from the screen alone.