Five-second website test: what do visitors understand?
Run a five-second first-impression test for your website, ask neutral questions and turn observations into clear design changes.
Article language: English

In this article
Show someone the opening screen of your website, hide it after five seconds and ask: what did the company offer, who was it for, and what could you do next? This first-impression test can reveal an unclear message. It does not measure the whole site's usability or a magical limit on human attention. If the answer is “something elegant, perhaps technology”, you have a clue for editing the page, even if everyone in the room loved the photograph.
Five seconds is a chosen length for the exercise. It is not a universal attention limit or the point at which every visitor closes the tab. Nielsen Norman Group describes the method as a way to study first impressions and recommends other kinds of tests for assessing task performance. See its guide to testing visual design.
What question should the test answer?
Choose one main uncertainty. Do people recognise the firm as a law practice for businesses? Do visitors understand that the offer is for a website? Do the photograph and headline point towards the same meaning? Without a research question, it is easy to collect a set of preferences that gives you little reason to choose one change over another.
Write down who the page is for and the circumstances in which they will see it. Someone arriving through a referral may already know the company's name. A person coming from an advert expects an answer to a particular promise. Prepare the test for the entry point you have chosen rather than mixing those contexts into one assessment.
Decide what you will treat as a signal to revise the page. You might look for a recurring misunderstanding of the service or uncertainty about the next step. You do not need a made-up industry benchmark. You need clear observations connected to what the page needs to achieve.
Who should you invite, and what should you show?
Invite people who resemble the intended audience and were not involved in the project. A colleague who knows the sales presentation is more likely to fill in missing information. A conversation with that person can help you prepare the test, but keep it separate from observing someone new to the offer.
Show the screen at a size that corresponds to the device people will use. If most visits from the planned campaign are expected on phones, start with a phone. Use a finished version with the actual copy and imagery. A layout with placeholder text can help you assess composition, but it will not tell you whether a customer understands the offer.
If you compare variants, change a limited number of elements. Otherwise, you will not know whether a difference came from the headline, the photograph, the colour or an entirely new offer. Record the order of presentation: seeing one version first may make the next one easier to understand.
How do you run a short test without leading people?
Prepare a neutral introduction. Do not summarise the company's work beforehand. After showing and hiding the screen, ask open questions: what does the company do, who might its offer be for, what did the participant remember, and what was missing that would have helped them understand the page? Let people answer in their own words. If the exercise will be completed independently online, plan an unmoderated study with clear instructions and an obvious ending (in Polish) instead of relying on the author to explain it afterwards.
Record responses as accurately as you can. Separate what someone said unprompted from answers given after a follow-up question. If you want to ask about a particular element, do it after collecting the first reaction. “Was the gold button visible enough?” already supplies a clue that an ordinary visitor would not have received.
Do not correct participants while they answer. A mistaken reading of the offer is exactly the result you want to see. Once that part is over, you can show the page again and ask the person to complete a task, such as finding the scope of the service.
What ten things should you review afterwards?
Use this list to examine the design after collecting the initial reactions. It is not a set of ten things participants must remember in five seconds.
- The company name and a line explaining what it does.
- A headline that says what the offer is about.
- An indication of the audience or the situation in which the service helps.
- A concrete scope rather than claims of quality alone.
- An image that supports the offer's meaning and is described honestly.
- Text that is readable against its actual background.
- One recognisable primary next step.
- A button label that says what will happen when it is clicked.
- Navigation that lets people find details and contact information.
- Trust signals the company can substantiate with its own materials.
Also check whether motion makes people wait for the key message. A headline that appears only after a long animation makes visitors wait before they can understand it. During the test, record when the countdown began and what was already visible.
How do you separate first impressions from usability and accessibility?
A person may describe the brand's character correctly and still be unable to find the contact details. After the first-impression exercise, prepare short tasks on the working site. The participant has already seen the first screen and answered questions. If you need to observe how someone uses that screen for the first time, run a separate test with people who have not seen it before. Observe the first choice, mistakes and places where the person needs help. Do not assume that “everything is clear” means they can complete the action.
Assess accessibility separately. Text contrast can be checked against WCAG. W3C explains the 4.5:1 threshold for normal text and 3:1 for large text, subject to the stated exceptions. The details are in its explanation of the WCAG 2.2 minimum contrast criterion. A first-impression test alone does not confirm that the criterion has been met.
Include checks for keyboard use, enlarged text, phone use and reduced motion in the acceptance process. These tests answer different questions, but together they provide a basis for a considered publication decision.
How do you report results without false precision?
For a small study, keep the participants' words and recurring observations. Do not turn a handful of conversations into statistics describing the entire market. Record who took part, which screen they saw, its size and the order in which it was shown. The person reading the report can then judge the limits of the finding.

Use three separate fields in the observation record: the participant's words, the team's interpretation and the proposed change. An example such as “I thought you sold ready-made templates” may suggest a hypothesis that the service description is unclear. It does not yet prove that the whole visual direction needs to change. Try a simpler revision first and repeat the appropriate test.
How do you write a scenario that does not give the answer away?
This practice example concerns a company that designs websites for B2B services. The facilitator might say: “You are about to see a company's website; look at it as you would on a first visit.” They should not first add that the study concerns a web design offer. Some of the correct answer would then come from the instruction.
Keep a question about meaning separate from a question about preference. “What does this company do?” and “Do you like the design?” serve different purposes. An attractive website might be mistaken for an interiors magazine even though it offers architectural services. That mismatch calls for an understanding of what the image and text are doing, not an automatic conclusion that a beautiful photograph is a mistake.
How do you tell unclear copy from weak visual hierarchy?
After showing the page again, check whether the participant finds the explanation and understands it without further comment. If they still do not understand after reading it, look at the copy. If the meaning becomes clear only after someone points out a small caption, the hierarchy may be the problem. These are hypotheses to test, not automatic diagnoses from one response.
In the first case, writing a service page (guide) (in Polish) can help: name the scope, the audience and an outcome the company can honestly promise. A working example such as “We create the future of your brand” can be compared with a more specific description of the service. Do not add clients, figures or results the company has not confirmed.
In the second case, examine typography on a premium website (in Polish). The distinction between headline, explanation and button should support the reading order. Simply making all the text larger does not create a hierarchy. Check line breaks on a phone, the space around the image and whether a less important label competes with the explanation people need.
How do you record an observation, a hypothesis and a follow-up test?
A working note might read: observation: the participant described the company as a template seller; hypothesis: the opening screen lacked information about bespoke design; change: clarify the short description; check: repeat the neutral exercise. This is a methodological example, not a claim about the results of a real company.
If a larger part of the site needs to be redesigned, state that you are comparing whole concepts. Do not present the result as proof that one particular word or colour was superior.
For images, check whether they show what the company actually does or are clearly presented as illustrations. Brand photography on a website (guide) (in Polish) can help establish the image's purpose. A generated interior should not masquerade as a completed project, and a fictional portrait of a team member is not evidence of expertise.
How do you move from recognising the offer to completing a task?
After the recall exercise, show the page again and ask the participant to find information needed before a conversation. In the layout and supporting evidence for a B2B service page (guide) (in Polish), plan a route from the opening promise to the scope, working process and contact. The first screen does not have to contain every detail. Assess the rest of the route through a moderated prototype usability test (in Polish), observing the task and places where the person stops, not just what they remember from the first view.
If someone recognises the service correctly but reaches a different offer, look at the labels and the site's information architecture (guide) (in Polish). If they find the right form but cannot submit it, the result concerns functionality. Keep separate notes so you do not try to repair a technical failure by changing a slogan.
When should you stop revising the opening screen?
Return to the question set before the study. If the main misunderstanding has disappeared in subsequent observations and the full route works, record the decision, its reasons and the limits of the test. A new aesthetic comment does not have to reopen the entire project. Set a review point tied to a change in the offer or new evidence instead of revising the same headline indefinitely.
In the final note, keep the option that was not chosen and the reason. During the next campaign, that will make it easier to see whether the audience, the promise or simply the author's preference has changed. The team will not have to repeat the same conversation without access to the earlier observations.
Run a separate exercise on your own team page. The guide to presenting a team on a website (in Polish) can help define what the page should communicate. Ask which skills the participant remembered and whom they associate with responsibility for the service. Recognising friendly faces and understanding how the collaboration would work are two different findings.
How do you turn a finding into a specific change?
For each observation, record its source, a possible cause and a proposed revision. If people misunderstand the scope of the service, start with the headline and description. If they understand the offer but do not know how to start a conversation, check the button and the explanation of the next step. Do not change everything at once.
After the revision, repeat the appropriate exercise with people who have not seen the previous version. Keep the result and the design decision. The next discussion about the headline can then return to observations instead of starting from scratch.
Record the page's purpose in your project brief beforehand. The guide to preparing a website brief (in Polish) explains what to agree before design. If you are choosing between a single landing page and a broader website, read the comparison of those scopes (guide) (in Polish). The Aeneia Design offer brings together design, content and acceptance criteria.
After assessing the first impression, move on to acceptance of the whole user journey (in Polish). That exercise covers contact, errors and keyboard use, none of which a brief first look can assess.











