Point the scan at a URL. A runner loads your live site or app in a real browser, navigates, clicks and fills things in, and reports where a real person would get stuck — alongside a read of your product by eight population groups.
Only what the runner really does. Nothing here is aspirational.
You supply one or more URLs. For a protected page you can add a test login — use a demo account, not a personal one. The details are used to click through your app and are not kept after the test.
The run is reported step by step — navigate, click, fill, scroll — with screenshots taken along the way, so you can see the path the runner took rather than trusting a summary.
The runner cannot get past two-factor authentication, SMS codes or captchas. When a login fails, that is written into your report as a friction point and the test continues on whatever is reachable without signing in.
Alongside the click-through, eight archetypes go through your input and report first impression, friction, and what they need — with a clarity and appeal score per group.
Live prices. A quick review reads what you submit; the in-depth tier is the one that puts a runner through your live product.
Quick review
$12
A short report per population group, based on what you submit — text, a URL's visible content, or screenshots.
Extensive
$25
The full breakdown per group: first impression, friction, what they need, and clarity and appeal scores.
In-depth
$39
A real runner opens your URLs in a browser and clicks through the product, with a step-by-step journey and screenshots in the report.
You know where every button is. That is exactly why you cannot tell what is confusing. A run gives you a first-time path through your own flow.
The scan walks it and reports the point where it stalls, with the screenshot of the screen it stalled on.
Eight population groups react to the same product, so you can see where clarity holds for one group and collapses for another.
It is not an accessibility audit, a performance benchmark or a security test. It does not replace watching a real user, and it cannot get past two-factor authentication, SMS verification or captchas.
Treat the output the way you would treat a sharp colleague clicking through your product for the first time: fast, specific, worth acting on, and not evidence.
Start with the wizard: describe what you are testing, add your URLs, pick a tier.
Start a UX scan