A senior designer reviews every screen
Ten findings per area, ranked by impact
A PDF report in three working days
Why by hand
What Only a Human Can Check
A reviewer walks the store the way a customer does, mistypes a search, carries a cart into the checkout and signs in to an account, watching where the journey stalls. That is why each finding names the screen it was found on, the moment it costs you the sale, and the change that fixes it, with two stores that solved the same problem well beside it.
Human review
A Designer Reviews Your Store, Not a Crawler
An automated scan reads what a page is built from. This audit reads what it is like to shop there.
A Senior Designer, Start to Finish
One reviewer walks the whole journey and carries what they learned on the homepage into the search results, the product page and the checkout.
Evidence on Every Finding
Each problem arrives with the screen it was found on and the element in question outlined, so nobody has to hunt for what we mean.
Ten Findings in Every Area
Each area of the store gets its own list: the ten problems that cost the most, ordered by what they cost.
A Report Your Team Can Work From
Problem, fix, evidence and two reference implementations, written so a designer or a developer can pick it up without a meeting first.
Audit scope
Every Stage of the Journey, Reviewed in Order
Homepage
What the store sells, who it is for, and whether the range is visible in the first screen.
Navigation
Menu structure, labels, depth, and whether people can reach a category without searching.
Search
Query handling, suggestions, zero-result pages, and what happens to a misspelt word.
Product Listings
Grid density, what each card carries, pagination, and how quickly a shopper can compare.
Filtering and Sorting
Which filters exist, how they combine, and whether the result set keeps up with them.
Product Page
Imagery, copy, variant choice, stock, delivery, and everything between the price and the button.
Cart
Editing, totals, shipping estimates, and the moment people decide to leave.
Checkout
Steps, fields, the guest flow, payment choice, and every place the form fights back.
Customer Account
Registration, order history, returns, and whether the account earns its keep.
What you receive
What a Manual Audit Hands Back
The audit is a fixed piece of work, not an open ended review. You know before it starts how much of the store is covered, how many problems come back from each area, and the day the finished report is in your hands.
9 areas reviewed
From the homepage and navigation through search and listings, to filtering, the product page, the cart, the checkout and the customer account.
10 findings per area
The ten problems in each area that do the most damage, ranked so the first fix is the one worth making first.
3 days to the PDF report
The finished report lands in your inbox within three working days of the audit starting.
How we judge
The Standards Behind Every Finding
Nothing in the report is a matter of taste. Each finding is argued from published research, from established usability principles, or from work our team has shipped and measured.
Ecommerce Usability Research
Findings lean on Baymard Institute's large-scale ecommerce usability research rather than on taste. That research says what shoppers do on stores like yours. The audit says what your store does about it, screen by screen.
Baymard Institute
Applied, Not Quoted
Checked on Your Store
No Taste Arguments
Established Usability Heuristics
Interfaces are read against Jakob Nielsen's ten usability heuristics, published in 1994 and still the common language of the field: visibility of system state, a match to the real world, recognition over recall, and error prevention before error recovery. Each finding names the one it breaks, so the argument is open to challenge rather than taken on trust.
Nielsen's Ten Heuristics
A Match to the Real World
Recognition Over Recall
Prevention Before Recovery
From What Was Seen to What to Change
Every finding travels the same road: the screen it was found on, the principle it breaks, the cost it carries, the change we recommend, and two stores that already made it. Nothing arrives as an opinion with a screenshot attached.
WCAG Success Criteria
Contrast, focus order, labels, keyboard operation and document structure are checked against the WCAG success criteria, so the report covers people your analytics never shows you.
Contrast
Focus Order
Labels and Structure
Keyboard Operation
Patterns We Have Shipped and Measured
The last layer is practice. Our team has built, tested and corrected these patterns on live stores, and knows which ones moved the numbers afterwards and which ones only looked better.
Built on Live Stores
Tested, Not Assumed
Measured Afterwards
Corrected When Wrong
Verified reviews
What Our Clients Say
2.1s
faster largest contentful paint
This team consistently goes above and beyond in terms of helping to ascertain the most viable and feasible outputs and outcomes for our evergrowing business needs.
Anthony Perrotta
E-Commerce Operations Manager
4 yrs
as their sole technical partner
They designed for where the product was going, not just what we asked for. Early on we described a single-company setup; they built the data model and permission layer so multi-tenancy wouldn’t require a rewrite later.
Alex Tee
CTO
Anatomy of a finding
What You Get for Each of the Ten Problems
Every finding is written the same way, so the report reads alike whether the problem sits in search or in the checkout.
The Problem, Stated Plainly
What breaks, who it happens to, and what it costs, in language someone outside the design team can act on.
The Fix, Written Out
The change we recommend, specific enough to brief a developer, with the reasoning that makes it worth doing.
A Marked-Up Screenshot
The screen the problem was found on, with the element in question outlined and a caption saying what to look at. There is no argument about what we mean, and nobody has to reproduce the problem before they can start on it.
Two Stores That Solved It
Two real implementations of the pattern we are recommending, each with its screenshot and a note on what makes it work. The fix becomes something you can see rather than something you have to imagine.
Named stores, not anonymous
A screenshot of the pattern
A note on what makes it work
From brief to report
How the Audit Runs, Step by Step
No access to your admin, nothing installed on your site, and no waiting weeks for the result.
Your Store URL
What Matters Most to You
No Admin Access
Nothing Installed
Every Area, in Order
Screens Captured and Marked
Findings Ranked by Impact
Reference Stores Collected
One PDF Document
Within Three Working Days
Ordered by Impact
Yours to Share
Trusted by 100+ companies
Keep reading
Our Ecommerce Knowledge Hub
FAQ
Questions, Answered
Still have questions?
Tell us about your store and we will come back with straight answers.
Book a call
What does the manual UX audit cover?
Nine areas, in the order a customer meets them: homepage, navigation, search, product listings, filtering and sorting, product pages, cart, checkout and the customer account. Each area returns its own list of the ten problems that cost you the most.
How is this different from an automated audit?
An automated audit measures what can be read from the outside: speed, markup, structure. A manual review uses the search box, carries a cart into the checkout, signs in to an account, and explains why a step confuses people rather than only how long it took. The two answer different questions, and most stores benefit from both.
How long does it take?
The finished report arrives as a PDF within three working days of the audit starting.
What do you need from me?
The store URL and a short note on what matters most to you. No admin access, no credentials, and nothing installed on your site.
What does a single finding look like?
The problem in plain language, its impact level, the fix we recommend, a screenshot of the screen with the element outlined, and two stores that solved the same problem well.
Can my developers work straight from the report?
That is what it is written for. Each finding names the change, the screen it belongs to and the reasoning behind it, so it can go into a backlog without another round of questions.
Do you also implement the fixes?
We can, and often do. The report is yours either way, and it is written to be useful to whichever team picks it up.
Let’s build something great together!
Book Your Manual UX Audit
Tell us which store to review and a senior designer walks the whole journey, then sends the findings, the fixes and the evidence as a PDF within three working days.