First Click Testing

A first click test shows people a screen, gives them a task, and records the one place they would click first to start it. It answers a narrow question: does your layout and labelling send people down the right path? You can run it on a sketch, a wireframe, a clickable prototype or a live page, long before the rest of the journey exists.

How it differs from related tests

Test	What participants do	What it tells you
First click test	Click once on a static screen to start a task	Whether labels and layout point people the right way
Five Second Test	Look at a screen for a few seconds, then answer questions	What people notice, remember and understand at a glance
Full usability test (for example with a clickable or paper prototype)	Try to complete the whole task while you observe	Whether they can finish, and why they struggle

A first click test is fast and cheap because it stops after one click. That is also its limit: it can’t tell you whether people would complete the task.

Measure user comprehension and interface complexity

Presenting a flat screenshot or a mock up in order to subsequently ask users to click on the image to complete a task, can provide insights into how easy your interface is to comprehend – whether it is too complex to understand.

An analysis of scenario-based usability tests by Bob Bailey and Cari Wolfson, FirstClick Usability Testing, found that when a user’s first click was correct, he or she had an 87% chance of completing the task – and only 46% when the first click was incorrect. Jeff Sauro at MeasuringU cites the same figures. Treat them as a strong association from website navigation tasks, not a law: a correct first click doesn’t cause success, and the later steps still have to work.

Measuring the time it takes for users to find and click a target provides insights into how easily users can find it and will act as a useful benchmark for comparing the usability of design alternatives.

Similarly, depending on the task you give participants, first click testing can provide information about user expectations, visual clarity and whether your design patterns are readily understood.

Ask follow up questions

Especially for participants who dwell too long figuring out where to choose, it is interesting to find out more about what made them hesitate. Jeff Sauro suggests asking participants how confident they were after each task; low confidence on a correct click is a warning sign too. If you are conducting the test remotely using a software tool, trigger a follow up question as the user is done clicking.

Observing users do first-click testing in real life can help generate an understanding of their frustrations. If you have that luxury, watch their facial expressions and ask what goes through their mind when their body language shows discomfort or frustration.

Benchmark with the original

You are looking to find out whether your new design performs better than what it replaces. This is why it is essential to not only test your new design, but also the original. Testing the original will act as a benchmark and help you decide whether to roll out your new design or keep iterating.

How to run a first click test

1. Pick the tasks and mark every correct target. Choose 3 to 6 tasks that matter, and before testing, mark all the areas that would count as a correct first click. Some tasks have more than one right path.
2. Write task scenarios in your users’ words. Describe the goal, not the label: “You want to stop getting weekly summary emails”, not “Find notification settings”. Borrowing the words on the screen turns the test into a word-matching game.
3. Prepare the screens. Use the same fidelity for every version you compare. If you are testing a redesign, include the current design as a benchmark.
4. Recruit people who match your users, then run it. An unmoderated tool can collect a few dozen to a hundred responses in a day; HMRC’s researchers suggest 50 to 100 completed tests. Randomize the task order, record one click per task, and ask how confident people were.
5. Analyze where people clicked and how long it took. Calculate the share of correct first clicks with a confidence range, look at where wrong clicks cluster on the heatmap, and compare the median time to first click between versions.
6. Decide, then test the rest of the path. Fix what the wrong clicks reveal, re-test, and check the full journey with a usability test before you call the navigation done.

Worked example: from task to decision

This example is hypothetical. The product, people and numbers are invented to show the reasoning, not taken from a real company.

A project-management tool gets many support tickets from people who can’t turn off their weekly summary email. The setting lives under Notifications in the settings menu, next to Profile, Billing and Help.

• Task: “You no longer want the weekly summary email. Where would you click first?”
• Current design (60 participants): 27 click Notifications (45%, plausible range 33–58%), 21 click Profile (35%), and the rest scatter. Median time to first click is 9.8 seconds.
• Redesign (60 different participants): the item is renamed Email & notifications. 44 click it (73%, range 61–83%), and the median time drops to 5.1 seconds.

The ranges don’t overlap, so the improvement is unlikely to be chance. The wrong clicks are informative too: a third of people looked under Profile, which suggests they think of email preferences as personal settings. The team ships the rename, adds a link to email preferences from the Profile page, and runs a short usability test of the full path, because a correct first click doesn’t prove people can find the toggle on the next screen.

Reading the results

• Correct first-click rate. The headline number. Report it with a range: with 40 participants, 50% correct could plausibly be anything from about 35% to 65%.
• Where the wrong clicks go. Clusters of wrong clicks show what people expected. A cluster on one wrong label is a clear signal; scattered clicks suggest nothing on the screen matched the task.
• Time to first click. Use the median, because a few slow participants skew the average. A correct click that took a long time still points to hesitation.
• Confidence. Low confidence on correct clicks suggests people guessed.
• What it can’t tell you. Whether people complete the task, whether later screens work, or whether they would even try the task in real life. Pair it with a usability test for the full journey, and a comprehension test when the question is whether people understand the content.

Why use First-click testing for product research?

The method is aimed at evaluating the intuitiveness and efficiency of navigation within a digital interface.

First Click Testing focuses on understanding how users interact with a website or application interface when trying to complete specific tasks. By analyzing where users click first and how those actions correlate with task success, designers can identify potential navigational issues and opportunities for improvement. The goal is to create an interface that allows users to intuitively find what they are looking for, enhancing the overall user experience.