Define the critical journey
Write where the visitor starts, what they try to do, and the successful end state.
Free browser checklist
Small sites · one critical journey · release-day focus
Check the path that matters before you launch.
Run these checks from a clean browser session. Record the exact URL, viewport, and evidence for anything that fails. Use only systems and data you are authorized to test.
Start from a clean session
Use a private window or a clean test profile so cached state does not hide a first-visit failure.
Open every primary action
Check the destination, page state, browser Back behavior, and any error or loading state.
Submit each key form safely
Try empty, invalid, corrected, and successful states with controlled test data.
Repeat at mobile width
At about 390 px, look for horizontal scrolling, clipping, overlaps, and actions below the viewport.
Repeat at tablet and desktop
Confirm layout changes do not hide navigation, break media, or separate labels from controls.
Use the keyboard
Tab through the page, activate controls, close overlays, and confirm focus always remains visible.
Inspect names and headings
Check form labels, repeated button names, link text, image alternatives, and heading order.
Compare the promises
Price, scope, turnaround, dates, and calls to action should agree across the page.
Search for private or stale values
Look for personal emails, tokens, staging domains, placeholders, TODOs, and obsolete offers.
Retest from the original steps
After a fix, repeat the same path and check nearby behavior for regressions.
Record the release decision
Choose Go, Conditional Go, or No-Go and list every unresolved high-impact issue and owner.
Need evidence and a handoff?
Ask about the $149 launch QA pilot.
Up to five public pages, one important journey, three viewport widths, and a prioritized report.