A designer who has spent three weeks on a homepage has looked at it more often than at their own front door. That familiarity creates blind spots: the team remembers the strategy, compromises and intended meaning, while a first-time visitor sees only what the screen actually communicates.
A client's customer has none of that context. They arrive from a search result or a link in a message, and they give the page about five seconds to answer one question: am I in the right place?
This guide explains how to recover that five-second view before launch instead of after it.
A quick exercise for any delivery team
Open the homepage in progress and look at it for five seconds. Close the tab, then write down from memory:
- What does this company do?
- Who is it for?
- What would a visitor click first?
A hesitation on any of the three is a warning sign. The person answering knows the project inside out, so a stranger will struggle more. Keep the answers: they become useful evidence at the end of the test.
Why teams stop seeing their own work
This is the curse of knowledge. Once someone knows something, it becomes difficult to remember what it was like not to know it. Three blind spots appear repeatedly:
- Insider words: project names, internal service labels and shorthand from the kickoff call that never became plain English.
- Remembered intent: the team sees a photo and remembers what it was meant to communicate; a visitor just sees a photo.
- Learned layout: the team knows where everything lives, so scanning the page feels effortless.
Clients are often affected even more. They live inside the business every day, so their own homepage can feel obvious even when it is unclear to a new customer.
The four silent questions
First-time visitors rarely say these questions aloud, but the opening screen needs to answer them quickly.
| The silent question | What it needs from the page |
|---|---|
| What is this? | A headline in plain words |
| Is it for me? | A clear sign of who the page speaks to |
| Can I trust it? | One real proof point: a name, number, face or result |
| What do I do now? | One clear next step |
A page that answers the first and last questions but skips the second can read like a brochure for nobody in particular.
How to run a five-second test in one afternoon
A lab is not required. A screenshot, a timer and five people are enough.
- Pick the screen. Test only the first screen, with no scrolling. A Figma frame works, so testing can happen before anything is built.
- Find five outsiders. Choose people who have not seen the project and are ideally close to the client's real customer.
- Show the screen for five seconds, then hide it.
- Ask three questions: What does this company do? Who is it for? What would you click first?
- Record their exact words. Summaries lose detail, and the wording is the evidence.
- Repeat on a phone-sized screen. The first screen on mobile is effectively a different page.
Ask questions that reveal understanding
Some questions produce evidence. Others invite politeness. Replace broad preference questions with prompts that test what the visitor actually understood.
| Weak question | Better question |
|---|---|
| Do you like it? | What do you think this company does? |
| Is it clear? | Who do you think this is for? |
| Does the headline work? | What is the first thing you would click, and why? |
| What do you think of the colours? | What do you remember from the page? |
How to read the answers
The aim is to find patterns, not collect opinions. Answers usually fall into three groups:
- Blank: nobody can say what the company does. This usually points to a headline problem.
- Wrong: people answer confidently but differently. The image, headline and navigation may be telling different stories.
- Right, but slow: people understand only after a pause or a scroll. The right message exists, but the hierarchy is too weak.
One person's answer is a story. The same answer from three people is a finding.
Turn the findings into changes
Make changes in a deliberate order because each decision affects how the next element is read:
- The headline
- The first image
- The main button label
- One trust signal near the top
After each meaningful change, show the revision to two fresh people. Do not reuse the original five because they have already learned the answer.
Show the results to the client
A client can argue with a designer's opinion. A stranger's own words are harder to dismiss. Share the raw answers instead of announcing a verdict: “We asked five people who had not seen the project what they thought it was. Here is what they said.”
This keeps the conversation curious instead of defensive and moves the discussion away from one person's taste against another's.
Where the test fits in the delivery process
The cheapest moment to run the test is while the design still lives in Figma, before approval. A headline change there takes minutes. After development, the same change can affect templates, responsive layouts and CMS content. This applies to focused marketing websites and larger platform projects alike: the later a change lands, the more it costs.
Run a second test before launch as part of final checks. The Agency Website QA Checklist and the website copy checklist pair well with it.
A 10-minute check for the delivery team
- The headline says what the company does in words a customer would use.
- The first image supports the message instead of merely decorating it.
- One obvious main button is visible.
- The first screen has been checked on a phone.
- Five outsiders have seen it for five seconds.
- Their answers are written down word for word.
Back to the first three answers
Compare the three answers the team wrote at the start with what outsiders said. The gap between them is the part of the page the team can no longer see.
Agencies that want to catch these gaps earlier can begin with Oncreation's free agency website brief template, which helps establish the audience and goals before design begins. Agencies looking for a white-label web design partner UK can also review how Oncreation supports strategy, responsive design and development behind the scenes.
Turn the guidance into a dependable delivery system.
Oncreation works behind agencies on website structure, custom UI, development, QA and launch—with the agency remaining in control of its client relationship.
