User testing basics for small sites

Why user testing matters

You know your website inside and out. But real users see it differently. They do not know where things are or how things work.

User testing reveals problems you cannot see yourself. It shows where people get stuck, what confuses them, and what works well.

What user testing is

User testing is watching real people use your website. You observe what they do, where they struggle, and what they understand.

It does not need to be formal or expensive. Simple testing with a few people reveals most problems.

What to test

Key journeys

Test the journeys that matter most to your goals.

• Finding information about your services.
• Contacting you or making an enquiry.
• Completing forms or making purchases.
• Understanding what you do and why it matters.

Specific tasks

Give users specific tasks to complete.

• Find information about a specific service.
• Work out how to contact you.
• Complete a form or make a purchase.
• Understand your pricing or process.

Simple testing methods

Informal testing with friends or colleagues

Start with people you know.

• Ask them to complete specific tasks.
• Watch what they do without helping.
• Ask what they think and what confuses them.
• Note where they get stuck or frustrated.

Remote testing

Test with people remotely using screen sharing.

• Use video calls to watch people use your site.
• Ask them to think aloud as they navigate.
• Record sessions to review later.

Guerrilla testing

Test quickly with people in your area.

• Ask people in coffee shops or co-working spaces.
• Keep it short, five to ten minutes.
• Focus on one or two key tasks.

How to run a test

Before the test

Prepare what you want to test.

• Choose one or two key tasks.
• Write down the tasks clearly.
• Prepare your site or prototype.
• Decide what you want to observe.

During the test

Let users explore without helping.

• Give them the task and let them work.
• Watch what they do, not what they say they would do.
• Ask them to think aloud.
• Do not help or guide them.
• Take notes on what you observe.

After the test

Ask questions to understand their experience.

• What was easy or difficult?
• What confused them?
• What did they expect to find?
• Would they use this site again?

What to look for

Problems

Watch for signs of problems.

• Users cannot find what they need.
• Users get stuck or give up.
• Users click the wrong thing.
• Users do not understand what to do next.
• Users express frustration or confusion.

Success

Also note what works well.

• Users complete tasks easily.
• Users understand what they see.
• Users know what to do next.
• Users express satisfaction.

Accessibility testing

Include accessibility in your testing [1]Source 1 .

• Test with keyboard navigation only.
• Test with screen readers if possible.
• Test at different zoom levels.
• Test with users who have disabilities [2]Source 2 .

How many people to test

You do not need many people to find problems.

• Three to five people reveal most usability problems.
• More people find more problems, but with diminishing returns.
• Better to test with a few people regularly than many people once.

Acting on findings

Prioritise problems

Not all problems are equal.

• Focus on problems that block key tasks.
• Fix problems that affect many users.
• Address problems that cause frustration.

Make changes

Use what you learn to improve your site.

• Fix the problems you found.
• Simplify confusing areas.
• Make successful patterns more prominent.

Test again

Test after making changes to see if they help.

• Verify that fixes work.
• Check that you did not introduce new problems.
• Continue testing regularly.

Common mistakes

• Testing with too many people at once.
• Helping users during testing.
• Only testing with people who know your site.
• Not testing with people who have disabilities [2]Source 2 .
• Testing once and never again.
• Not acting on what you learn.

When to test

Test at different stages of your project.

• Test early with prototypes or wireframes.
• Test during development to catch problems early.
• Test before launch to fix critical issues.
• Test after launch to see how real users behave.
• Test regularly to catch problems as they emerge.

Simple testing checklist

A basic test might include:

• Choose one or two key tasks.
• Find three to five people to test.
• Give them the tasks and observe.
• Take notes on what you see.
• Ask questions after they complete tasks.
• Identify the main problems.
• Fix the problems.
• Test again to verify fixes.

Next step

Start with one simple test. Choose your most important user journey. Find three people to test it. Watch them use your site and take notes. Fix the problems you find. Then test again. Regular testing with a few people improves your site more than occasional testing with many people. If you need help with user testing or improving your site's usability, UX and UI services can help you understand how users interact with your site. For help with accessibility testing, see what an accessibility audit includes.