Start at the first impression.
Record the URL, the issue, and the consequence as you go.
- Can a new visitor tell what the business does, who it helps, and where to go next without decoding internal language?
- Does the main action match the page’s promise?
- Are service boundaries, geographic reach, and any important conditions stated accurately?
- Do images explain real work or merely fill space?
Write down the first question the page leaves unanswered. Do not solve it by adding more general copy. Answer the question where it occurs.
Follow a real path.
Choose one task, such as comparing a service, requesting a quote, or finding support. Follow it from the landing page to completion. Check navigation labels, links, pricing language, form fields, error messages, confirmation, and the expected follow-up. Repeat with a keyboard and narrow viewport. If a step cannot be completed, record the exact step and device.
Inspect trust and accessibility.
Check that names, client work, reviews, and outcome claims have permission and context. Read the privacy and contact information. Check heading order, visible focus, text contrast, image alternatives, zoom and reflow, and any moving element with reduced motion enabled. These checks help you find barriers, but they are not a formal accessibility certification.
Inspect the system behind the page.
- Confirm that the important pages are indexable on purpose, linked from relevant pages, and have distinct titles.
- Check the speed and stability of pages on a real connection and device.
- Verify form delivery, notifications, spam handling, and the team’s response ownership.
- Check whether analytics records meaningful events without exposing private form data.
- Know who updates content, plugins, hosting, and backups.
What happens after someone submits a request? A working button is only the start of a working journey.
Turn findings into a plan.
Group issues by customer impact and effort. Fix broken contact paths, false or missing information, and accessibility barriers before polishing small visual details. Assign an owner and a verification step to every change. Recheck the same task after the fix. A screenshot of an edit is not proof the journey now works.
For launch-specific tests, use the website launch checklist. For search-specific issues, use the SEO checklist. If you want help deciding what to fix first, talk to a specialist with the pages and observations you recorded.