Conversion Rate Optimization
User testing and usability
This is the narrowest useful unit of Conversion Rate Optimization: watch real people try to use the thing, which reliably finds what analytics cannot.
User testing and usability, defined
Watch real people try to use the thing, which reliably finds what analytics cannot. In practice that means task-based testing with participants who resemble actual buyers, and then the harder half: moderated sessions where the reasoning can be probed.
Why this work exists
Almost every engagement that stalls on this discipline stalls here, and almost nobody predicts it.
This is one part of Conversion Rate Optimization, described separately because it is usually the first thing anybody needs.
The nearest piece of work to it is making the primary action obvious without making it shouty. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
The working version gets updated by whoever notices, not by whoever owns it.
The gap between that and where most accounts start is why this is scoped as user testing and usability rather than as a line inside something larger. Working out which trust signals this audience actually reads is the usual second step once it is in place.
When this is the right work
The tells:
- The team cannot agree on why conversion is low
- No actual customer has ever been observed using the site
- Accessibility was checked with an automated tool and declared fine
If none of those is true, something else is probably the constraint, and the Conversion Rate Optimization overview maps the alternatives. The usual neighbours are finding the error message that sends people back to the start and testing the thank-you page because the journey does not end at submit.
What the work covers
In order, the work is:
- Task-based testing with participants who resemble actual buyers. This is the piece a client can verify themselves, which matters more than it sounds.
- Moderated sessions where the reasoning can be probed. The effort here scales with the size of the estate, not with the size of the brief.
- Unmoderated testing at volume for breadth. The output here is what everything after it is built from.
- Accessibility testing with assistive technology, not just an automated checker, usually the first thing to show a result, so it goes early.
How it runs
The sequence, and why it is that sequence.
Setting the guardrails
Limits get agreed early: what will not be touched, what needs sign-off, what can be changed without asking. Arguments about scope mostly trace back to skipping this.
Testing on the awkward cases
Whatever gets built is checked against the messy real examples rather than the clean ones, because the clean ones were never going to be the problem.
Writing it down for the next person
The reasoning gets recorded alongside the result, so a decision taken in March can still be defended in September by somebody who was not there.
What each part runs into
The obstacles differ by part and by market:
- Task-based testing with participants who resemble actual buyers, harder in Ahmedabad because of a market where buyers qualify by area rather than by city
- Moderated sessions where the reasoning can be probed – in Abu Dhabi, complicated by the fact that a competitive set that changes street by street
- Unmoderated testing at volume for breadth, which in Leeds runs into a decision made by somebody who never visits the site
- Accessibility testing with assistive technology, not just an automated checker: the Dallas version of this has to deal with a procurement step nobody accounted for
The mistake most often made here
Testing with colleagues. People who know the product cannot see what confuses someone who does not.
This is the version most often delivered, which is why the discipline has a worse reputation than it deserves.
How it is measured
Severity-weighted issue count, and conversion change after the fixes. Agreed up front and reported every period, with the raw data available rather than only a summary.
Two people should be able to calculate it independently and get the same answer. If they cannot, it is the wrong measure.
What you end up with
The tangible result is recorded sessions with findings prioritised by severity and frequency, including accessibility findings.
It includes what was looked at and ruled out, which is usually the more useful half.
How it differs by sector
The same piece of work changes shape depending on the sector it is done for:
- B2B services brings its own limit: a buying committee, a long cycle, and attribution that has to survive both.
- Ecommerce and retail, constrained by the fact that margin per order decides everything, and the product feed is usually the weakest asset.
- Home and trade services: Emergency intent, service-area geography, and a phone that has to be answered. so this work has to account for that before anything else.
The industry pages carry the rest of that detail. B2B services and Ecommerce and retail are the two where this piece of work most often decides the outcome.
Common questions
How many people do you need for usability testing?
Five to eight per audience segment finds most of the significant problems, because the same issues recur quickly. Beyond that the return drops sharply. If there are two distinct audiences, test both rather than averaging them into one group of eight.
Is automated accessibility testing enough?
No. Automated tools catch a minority of real accessibility problems, mostly the mechanical ones like missing alternative text and contrast failures. Keyboard navigation, focus order, screen reader comprehension and whether a task can actually be completed need a person and assistive technology.
Does this work at our size?
The diagnosis does, at any size. Whether the work that follows is worth the money depends on what an improvement in severity-weighted issue count, and conversion change after the fixes is actually worth to the business, which is the first thing to settle. Nonprofit and NGO is the reference page for this. Real estate and property is the one with the examples.
Can this be scoped on its own?
Yes, where the diagnosis says it is the constraint. More often it runs inside a Conversion Rate Optimization engagement, because the adjacent work is what makes the result hold. The scoping conversation settles which. AI Automation and Workflows is the part that scales. AI Platform Optimization is the part that never will.
How long does this take?
The diagnostic part is usually two to three weeks. What follows depends on what the diagnosis finds, and we scope the second phase after the first rather than quoting both upfront. The short version is here. Lead form or Landing page and Local SEO or National SEO are the long ones.
Ask about user testing and usability
Give us the site and one question. If the honest answer is that you do not need this, we will say so.
Replace the assumptions with measurements
Send what you have. We read it before the call, so the call is about decisions rather than discovery.