Skip to content

First click testing checklist: before, during, and after your study

This checklist covers the full lifecycle of a first click test — from preparing the design image and writing tasks through analyzing click maps and recommending design changes.

Before the test

  • Select the page or screen to test and export as a static image (PNG/JPEG at actual screen resolution)
  • Define 3-5 task scenarios that describe real user goals without using on-screen labels
  • Have someone review tasks against the image to check for label leakage
  • Define success zones for each task before launching (the correct click area)
  • Choose the testing tool (Lyssna, Maze, Chalkmark, UXtweak, or UserZoom)
  • Upload image, add tasks, and configure success zones in the tool
  • If comparing variants, set up between-subjects assignment
  • Enable task randomization for studies with more than 2 tasks
  • Run a pilot with 2-3 colleagues; check image quality, task clarity, and success zone accuracy
  • Recruit 15-30 participants per variant who match the target audience

During the test

  • For unmoderated: distribute the study link and monitor completion rates
  • For moderated: share screen, show image, read task, record click and time, ask “What did you expect to find there?” after each click
  • If early results reveal a broken task (ambiguous wording, wrong image), pause, fix, and restart

After the test

  • Review click maps for each task — note where clicks concentrate and where they scatter
  • Check success rate per task — flag any below 80%
  • Check time-to-click per task — flag any where average exceeds 5 seconds
  • Identify elements that attracted significant incorrect clicks (misclick targets)
  • For each problem: classify as labeling issue, visual hierarchy issue, or positioning issue
  • Recommend specific design changes for each problem area
  • If comparing variants: summarize which performed better per task and overall
  • Write a short report with click maps, success rates, problem areas, and recommendations
  • Share with the design team; plan a follow-up test if changes are made