How Sensei scoring works
Sensei scores a public page by extracting its structure, evaluating it against three weighted UX layers, and translating those findings into a report a product team can act on.
The framework behind each score is grounded in design psychology, usability heuristics, conversion research, and competitive benchmarking — not ad-hoc rules. Every criterion maps to a documented discipline with real-world weight behind it.
Functional UX: 35%
Task clarity, navigation, feedback, accessibility, mobile markup signals, and whether the page helps a visitor understand what to do next.
Aesthetic quality: 35%
Visual confidence, hierarchy, restraint, typography, information density, and whether the page feels calm enough to trust.
UX practices: 30%
Known design psychology and conversion heuristics, including cognitive load, choice pressure, signifiers, social proof, and CTA quality.
What we examine
The scanner fetches the public HTML and extracts headings, body copy, CTAs, forms, links, image alt text, accessibility attributes, metadata, and structural landmarks. When a capture includes a screenshot, visual evidence can supplement those markup signals.
What we do not examine
Sensei does not inspect logged-in states, paywalled content, full interaction flows, live analytics, real Core Web Vitals, checkout completion, or private user data.
Mobile assessment
Mobile-responsiveness criteria are assessed from markup signals, viewport metadata, responsive patterns, and screenshots when available - not from a rendered mobile viewport. That keeps the current score honest about what the scanner can observe.
Stability and changes
Same URL + unchanged content + same methodology version should return the same score. Scores change when page content changes, the scoring methodology is versioned, or provider fallback introduces bounded model variance.