You have spent thousands of dollars driving traffic to your website, but your phone isn't ringing. When this happens, business owners often blame their advertising campaigns. But the truth is, your ads might be working perfectly; it is your website that is turning people away.
While tools like Google Analytics can tell you what is happening on your site, they cannot tell you why. Why do users abandon their shopping cart? Why do they click the contact page but never fill out the form? The only way to find out is to watch real people try to use your website. This guide explains how to run practical, budget-friendly usability testing to fix your user experience (UX) and turn frustrated visitors into paying customers.
Why does website usability testing matter?
Usability testing matters because it reveals exactly why potential customers abandon your website. While analytics tools show you where users drop off, observing real people navigate your site uncovers the hidden frustrations, confusing menus, and broken forms that are actively costing you sales.
Many New Zealand businesses focus entirely on Search Engine Optimisation (SEO) to get people to their site, completely forgetting what happens once they arrive. A great ranking means nothing if your website is a nightmare to navigate.
Quantitative tools like Google Analytics 4 (GA4) or Microsoft Clarity are fantastic for tracking raw numbers like scroll depth and bounce rates. But these tools lack human context. Qualitative usability research fills that gap, providing deep, actionable insights into human behaviour that data alone simply cannot deliver.
How many users do you need for a usability test?
You only need three unique users per round of testing to uncover the vast majority of usability issues. Instead of testing fifteen people at once, running five iterative rounds of three users allows you to fix problems quickly and retest the improvements.
The classic benchmark from the Nielsen Norman Group suggests running three rounds of five users. However, in our experience working with Kiwi small businesses, we have found that rapid, iterative testing works even better. Testing just three people will quickly expose your most glaring errors. You can then fix those errors immediately, and test a fresh group of three people to see if your fix actually worked.
How do you structure a usability testing session?
You should structure a usability session to last 30 to 45 minutes, split into three parts: a brief introduction to set expectations, 15 to 20 minutes of predefined website tasks, and a final debrief to gather open-ended feedback about their overall experience.
Keep it short and respectful. Offer a small compensation for their time e.g. a $50 Prezzy card or a coffee voucher is usually plenty.
- Intro (5–10 mins): Make them comfortable. Explain what the test is for and ensure they know there are no wrong answers.
- Tasks (15–20 mins): Have them perform the predefined actions on your website.
- Debrief (10–15 mins): Sit down with them to discuss what frustrated them and gather open-ended feedback.
What tasks should you ask test participants to do?
You should ask participants to complete specific, scenario-based tasks that mimic real customer journeys, such as finding a specific service, downloading a brochure, or submitting a contact form. Always instruct them to perform these tasks on a mobile phone first to ensure mobile usability.
Context matters. Do not just say, "Click the contact button." Give them a real-world scenario to put them in the right mindset.
For example, if you were testing the Adhesion website, you might use this scenario: “You recently launched a pet accessory business and want to invest in online marketing. You found Adhesion, an Auckland-based agency. Try to find the best online advertising option for your business.”
Then, give them tasks of increasing difficulty:
- The 15-Second Scan: "Open the homepage. Spend 15 seconds looking around. What exactly does this company do?"
- Service Discovery: "Find the specific page for Google Ads management. Explain why you chose it."
- The Action: "Fill out the contact form to ask a question, but stop right before hitting submit."
What are the best practices for running a usability test?
The best practices for running a usability test involve reducing participant bias by explaining you are testing the website, not the user. Encourage honest feedback, ask open-ended questions using the 'Five Whys' technique, and always record the screen and audio to capture natural reactions.
When a user gets stuck, their instinct is often to apologise and feel foolish. You must immediately reassure them that if they are confused, it is the website's fault, not theirs.
Watch for hesitation. If their mouse hovers over a button for ten seconds, ask them what they are thinking. Use simple screen recording software (even QuickTime Player with audio enabled) to capture their screen and their voice. Finally, never re-test the same person in a future round; once they have learned how to navigate your site, their perspective is no longer fresh.
What metrics should you track during UX research?
During UX research, you should track concrete metrics like the time spent on specific pages, exactly how users navigate your menus, where they abandon the checkout or contact process, and the specific verbal feedback they give when they suddenly feel stuck or confused.
Testing takes time and money, so you need to record everything practical. Pay close attention to:
- Did they use the top navigation menu, or did they scroll down the page to find links?
- Did they spend time reading your paragraphs, or did they just skim the headlines?
- At what exact point in your conversion funnel (like a checkout or a multi-step form) did they hesitate or drop off?
How do you choose the right participants for a UX test?
You must carefully screen participants to ensure they represent your actual target market, deliberately filtering out web developers or digital marketers who view sites differently than normal consumers. Using a structured screening survey guarantees you collect accurate, relevant feedback for your specific business.
If you offer plumbing services, testing your website on a group of software engineers will give you skewed results. You need to test your site on actual local homeowners. Use a quick screening survey to filter out anyone with a professional background in web design, as they will look at the code and structure rather than acting like a natural consumer.
Need expert help improving your website experience?
A beautiful website is completely useless if it is frustrating to use. Often, the biggest UX roadblock is simply a slow-loading template. At Adhesion, we solve this by building custom websites using fast headless architecture (like Next.js), completely eliminating the load-time frustrations that kill conversions.
We are a tight-knit Auckland team of fewer than 20 specialists, and we base our design decisions on real data and human behaviour, not just guesswork. If you are tired of losing leads to a clunky website, contact us today or request a comprehensive website audit to see exactly where your customers are getting stuck.
You might also be interested in...

Websites & Analytics
Choosing the Right CMS: What New Zealand Businesses Need to Know
Read MoreWebsites & Analytics
What is Google Analytics 4? (And Are You Actually Using It Right?)
Read More
Websites & Analytics
