Prioritized findings
Three changes to reduce the first-run drop-off.
High priority · Observed
“Start testing” opens the returning-user sign-in state.
Reproduction: From the public homepage, activate the primary “Start testing” CTA. It routes to /signin and initially renders “Welcome back. Enter your credentials.” A first-time visitor must then find “Create an account” below the form.
Why it matters: The CTA describes a new-user action, but the destination asks for an existing account. That is an avoidable decision and a likely dead end for anyone scanning quickly.
Change: Route acquisition CTAs directly to the create-account state and label them “Run my first test free.” Keep “Sign in” as the returning-user navigation action.
Acceptance check: A signed-out visitor who activates any “Start testing” CTA sees the create-account heading and the “100 free minutes · 14 days · no card” terms without another click.
High priority · Reproduced
The auth switcher is not keyboard-semantic, and inactive forms remain exposed.
Observed: “Create an account” and “Forgot password?” are <a> elements with no href, role, or tab index. They did not appear as interactive controls in the browser accessibility snapshot. The same snapshot exposed the headings and copy for Sign in, Create account, Reset password, and Set new password at the same time, although only one state was visible.
Change: Use real buttons for in-page state changes or links with real destinations. Remove inactive panels from the accessibility tree with the native hidden attribute or equivalent state management, then restore focus to the active heading.
Acceptance check: A keyboard-only user can reach every auth action in order, and an accessibility snapshot contains only the currently visible form.
Medium priority · Reproduced at 438 CSS px
The mobile auth page introduces horizontal scrolling.
Observed: In a 438-pixel-wide browser viewport, the auth page measured 423 pixels of document width and 558 pixels of scroll width—135 pixels of horizontal overflow. The desktop navigation remains expanded above the form, and a horizontal scrollbar is visible.
Change: Reuse the homepage's compact mobile navigation on auth pages, constrain the auth shell to the viewport, and audit fixed or minimum widths in the header.
Acceptance check: At 320, 375, 390, and 438 CSS pixels, scrollWidth === clientWidth, the form fields fit without panning, and the primary action remains fully visible.