UX audit
Where your users drop off, measured instead of guessed.
Users drop off, and everyone on the team has a different guess why. In the UX audit, I set up analytics in your application and measure where, when and how many users leave. No estimates, no guesses, just data, and from it the changes that make the biggest difference.
What the UX audit examines
Setting up measurement
I set up analytics in your application and track every step of your most important flows, such as sign-up, checkout or application. Privacy-compliant and tailored to the questions you want answered.
Drop-offs and their causes
I analyze at which step how many users drop off, at what time and on which device. Where something stands out, I take a closer look: clicks, scrolling, inputs and error messages.
The right tool
Every analytics tool has its own strengths and weaknesses: funnels and events, heatmaps or recorded sessions. I combine the ones that fit your application and your questions instead of measuring everything with one tool.
What you have in hand after the UX audit
Drop-off data per flow
For every important flow, at which step how many users leave, broken down by device and time period.
Prioritized findings
Every obstacle with the numbers that prove it, sorted by how many users it costs you.
Action plan
A concrete proposal for every finding in a sensible order, and the metric you use to measure success.
Measurement that stays
The measurement stays in your application so you can see whether the changes work. In the final meeting, we go through the results together.
Example finding from a UX audit
This is how every finding in the report is structured. The example is made up and shows how specific the results are.
Finding
41% of users leave the sign-up form, 58% on smartphones. Two thirds of them leave right after an error message at the password field.
Impact
The recorded sessions show why: errors only appear after submitting, and the password field is cleared. Anyone who makes a typo has to enter everything again.
Recommendation
Validate inputs right at the field and keep the password after an error. Effort about two hours. The same measurement shows after the release whether it works.
How the audit works
Request the audit
You pick your audit and briefly describe your application.
Fixed price and analysis
You get the fixed price for your application, then I review it.
Findings and action plan
You receive prioritized findings and a plan for the next steps.
Frequently asked questions about the UX audit
Why measure instead of just reviewing?
An expert review finds obstacles but does not tell you how many users they actually cost. With data, you see where, when and how often something happens, and invest first where it demonstrably pays off.
What do you need from me for the UX audit?
Access to the application and the option to add the measurement, or someone on your team who takes care of it. Plus a short description of who uses the application and which flows matter most. I also make use of existing analytics data.
What does the UX audit cost?
The audit comes at a fixed price from €1,500. I tell you the exact price before I start, it depends on the size of your application. If a follow-up project comes out of it, the audit price is credited towards it.
How long until the data is reliable?
That depends on how many users your application has. Two to four weeks are usually enough. We agree on the period together before the start.
Request the audit or talk first
Request your audit directly and you get the fixed price and time frame, with no obligation. Not sure which audit fits? Then we sort that out in a free initial call.
Problem
Your users don't reach their goal
Drop-offs, support requests and frustrated employees. I find the spots where your application slows users down and fix them.