Time on task: how long it takes to find what matters

Key takeaways

Time on task is how long a participant takes to complete a task, such as finding a price. It shows effort even when people succeed: a task that takes two minutes signals confusing navigation. Measure it in usability tests from the moment the task starts to success, report the median rather than the average, and compare like with like.

• Time from task start to success.
• Report the median, because a few slow attempts skew averages.
• Long times on success still signal confusing navigation.
• Use with task success, not instead of it.

What is time on task?

Time on task is a usability measure of the elapsed time between a participant starting a task and completing it. In navigation testing, it shows how quickly visitors can find information. It is different from 'time on page' in analytics, which measures attention on live traffic without a known goal.

• How clear website navigation improves user experience
• Task success rate: the simplest navigation measure

Why does time matter if people succeed?

Success hides effort. A participant who finds the price after two minutes of searching succeeded in the test, but a real visitor might have left after 30 seconds. Long times show where navigation makes visitors work hard, even when it eventually works.

How do you measure it?

Start the clock when the participant begins the task and stop it at success. Most testing tools do this automatically. Record failed attempts separately, rather than mixing their times in. With small samples, report the median, because one participant who gets distracted can distort an average.

• Start when the task begins.
• Stop at the defined end point.
• Record only successful attempts in the time.
• Report the median for small samples.
• Compare the same tasks across rounds.

What is a good time?

There is no universal benchmark; it depends on the task. As a working rule, core tasks such as finding a phone number, a service or a price should take seconds, not minutes, for first-time visitors. Compare your times with your own earlier tests and, where possible, with a competitor's site on the same task.

Can analytics measure time on task?

Not directly, because analytics does not know what visitors were trying to do. You can approximate it for a known journey, such as the time from landing to reaching the contact page, using GA4 explorations, but treat that as a rough signal.

• Navigation metrics: proof visitors find their way
• GA4 path exploration: see the routes visitors really take

What does this look like in practice?

A pattern we see: five of five participants find a firm's fees page, but the median time is well over a minute, because fees sit three levels down under 'About'. Moving the link to the main menu typically brings the time down to a few seconds without changing the page.

• See client work
• Website Design & Development for UK businesses

Time on task checklist

• Time core tasks in every test.
• Record success and time separately.
• Report the median.
• Compare the same tasks over time.
• Investigate tasks that take minutes.

• First-click testing: is the first step the right one?
• Did the new menu work? Measure navigation before and after

Next step

Time yourself finding your own price list from a blog post. Then ask a customer to try.