Five-Second Test
Showing a design briefly and asking what people remember, which tests hierarchy and clarity of message.
Definition
Participants view a design for about five seconds, then answer questions about what they saw and what they think it is for. It measures first impression and visual hierarchy rather than usability.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
On this plate
Reach for this when
- Evaluating a landing page or hero message.
- Checking whether visual hierarchy directs attention as intended.
- Comparing two headline treatments for what actually registers.
Common mistakes
- Using it to evaluate functional interfaces.
- Framing questions that give away the answer.
- Reading a clear recall of the brand as evidence that the message landed.
Questions worth asking afterwards
- What is this page for?
- What could you do here?
- What stood out most?
- Who is this for?
Running one
- 1
Say nothing about the product first
Any framing sentence you offer becomes the answer you get back. Show the design cold.
- 2
Show it for five seconds, once
A second viewing tests memory of the first, not first impression.
- 3
Ask recall before interpretation
What do you remember, then what is it for. Reversing the order lets the second question rewrite the first.
- 4
Count the misses, not the hits
The finding is what nobody mentioned. If the price, the audience or the action never comes up, the hierarchy is not carrying it.
Do
- Test the page as it loads, above the fold, at a realistic width.
- Run it on the current design and the proposal, with different people.
- Include the recall question about what they could do here, not only what it is.
Do not
- Describe the company before showing the screen.
- Use it to judge a form, a table or any flow with steps.
- Treat what people liked as a result. It measures what registered.
In practice
- i.
The hero that hid its own product
Landing pagesParticipants recalled the photograph and the brand name, and not one could say what the product did. The headline was accurate and generic, and the hierarchy gave it less weight than a stock image.
Commonly confused with
Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.
First-Click Testing
Research methodParticipants are asked where they would click for a task, and only the first click is recorded.
Key difference
A first-click test asks where you would go, and records one click. A five-second test shows the design briefly and asks what you remember. One measures whether navigation leads people right; the other measures whether the page communicates at a glance.
Use Five-Second Test when
- The question is first impression, not task completion.
- You are testing hierarchy, headline clarity or what stands out.
- There is no task yet, only a page that has to explain itself.
Use First-Click Testing when
- There is a task and a path, and you want to know if the path is found.
- The question is labelling, placement and information scent.
- You want a number that predicts eventual task success.
Local chart
RES·008 · Region IV · Grid G1
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Principles behind this
The reasoning this solution is an application of.
- Aesthetic-Usability EffectLAW·011 · Law
Often used with
These usually appear in the same screen or the same decision.
Related concept
Connected closely enough to change how you apply this.
- Guerrilla TestingRES·016 · Research method
- Usability TestingRES·001 · Research method
- EmphasisFND·018 · UI foundation
- Visual HierarchyFND·001 · UI foundation