Test a journey from beginning to end.
Choose the actions that matter to the business and follow them as a visitor. Start on a landing page, find the relevant service, open a project and attempt the next step. A working button does not prove that the whole journey makes sense.
For a contact form, check validation, the sending state, failure recovery and the confirmation page. Then confirm that an authorised test enquiry reaches the intended inbox. A success message alone is not evidence of inbox delivery.
Define the journeys before design begins using our website brief guide. That gives the final review a clear starting point.
- Can visitors find the next step?
- Are errors understandable and recoverable?
- Does the enquiry arrive where the team expects?
Review the small screen as a complete experience.
Read every heading and paragraph at narrow widths. Check navigation, touch targets, image crops and long names or email addresses. Test a landscape layout as well as a portrait layout.
Use a keyboard to move through links and forms. Focus should remain visible, menus should be escapable and error messages should help someone continue. Review the experience with reduced motion enabled too.
For an example of desktop and mobile presentation, look through the Black Moon Tattoo project.
Check the information search engines receive.
Give each public page a useful title, description and canonical URL. Check that the sitemap uses the live domain and includes the pages intended for search. Confirmation pages should stay out of it.
Review redirects from important old URLs and verify that missing pages return a real 404 response. Structured data should describe what a visitor can actually read; it should not introduce claims that the page cannot support.
Look beyond the first fast connection.
Check image sizes, loading behaviour and the amount of work triggered by animation. A hero should remain understandable if an optional visual effect cannot run.
Use measured performance results to investigate problems, then verify the experience on everyday devices. A single desktop score is a useful signal, not a complete account of how every visitor experiences the site.
Leave the next person a working system.
Confirm who owns the domain, hosting, source repository and sending service. Record how content is updated, how a deployment is recovered and who responds when an enquiry fails.
Keep a short list of what was tested and anything still awaiting verification. A clear handover makes the website easier to maintain after the launch conversation ends.
For client work delivered under your brand, review our white-label agency partnership approach and agree who owns each handover task.
Frequently asked questions.
Does a successful form message prove email delivery?
No. A provider may accept an enquiry before it reaches the inbox. Use an authorised test submission, check delivery status and confirm receipt in the intended mailbox.
Should the thank-you page appear in the sitemap?
A confirmation page is generally not a search landing page. Keep it out of the public sitemap and give it a noindex directive, while retaining the navigation visitors need after submitting.
Can a desktop performance test replace mobile checks?
No. Check real visitor journeys at smaller widths and on available everyday devices. Performance measurements help identify issues, but layout, touch interaction and readability also need review.
What should be handed over after launch?
Document account ownership, content editing, deployment and recovery steps, enquiry routing and the support contact. Include the checks completed and any items still awaiting verification.
Put the thinking to work.
Tell us about your website, your next project or the problem you need to solve.
Start a conversation