Why QA beats hope

Why this matters

Many site issues are not hard to prevent. They are hard to spot after launch, when you only notice them because enquiries drop or users complain.

A short checklist beats a long post-mortem.

When to run this checklist

• Before any release that affects layout, navigation, forms, or scripts.
• Before launching a campaign page.
• Before running ads to a landing page.
• After any CMS, dependency, or plugin update.

Accessibility checks

Keyboard journeys

• Use Tab from the top of the page. You reach all controls [1]Source 1 .
• Focus moves in a sensible order [1]Source 1 .
• Focus is visible at all times [1]Source 1 .
• You open and close the main navigation with keyboard only [2]Source 2 .
• You use submenus with keyboard only, if you have them [2]Source 2 .

Forms

• Every input has a visible label [1]Source 1 .
• Required fields are explained [1]Source 1 .
• Submit with errors. Errors explain what to fix [1]Source 1 .
• Focus moves to a clear error summary for longer forms, or to the first error [2]Source 2 .
• Success states are clear. Confirmation messages appear and make sense [1]Source 1 .

Structure

• Headings follow a logical order [1]Source 1 .
• Links make sense out of context [1]Source 1 .
• Interactive controls are buttons or links, not generic elements pretending [2]Source 2 .

Performance checks

Page weight and requests

• Key pages remain within your page weight budget [4]Source 4 .
• Request count does not jump without a good reason [4]Source 4 .
• Images are sized correctly and compressed [3]Source 3 .

Core Web Vitals risk areas

• The main content appears promptly on mobile [3]Source 3 .
• Interactions feel responsive. Menus, filters, forms, and buttons [3]Source 3 .
• The page does not shift unexpectedly while loading [3]Source 3 .

Third-party scripts

• No new third-party tags have been added without review [5]Source 5 .
• Tags load only where needed, not site-wide by default [5]Source 5 .
• Cookie and consent tools do not block the page or cause layout shift [5]Source 5 .

Tracking checks

Tracking failures are common. They also hide problems because you stop seeing what users do [9]Source 9 .

• Form submissions trigger the expected event [9]Source 9 .
• Primary CTA clicks trigger the expected event [9]Source 9 .
• Thank you pages load and are tracked [9]Source 9 .
• Phone and email links work on mobile and are tracked if needed [9]Source 9 .

Content checks

• Titles and descriptions exist and look sensible [6]Source 6 .
• Broken links are fixed, especially in navigation and footer.
• Images have useful alt text where needed [1]Source 1 .
• Pages have a clear call to action.
• Dates, prices, and contact details are correct.

Release safety checks

• You roll back quickly if something breaks.
• Forms and email delivery have been tested end to end.
• No accidental noindex or robots changes have shipped [7]Source 7 .
• Redirects are in place if any URLs changed [8]Source 8 .

A simple way to keep this consistent

Put the checklist in one place. Use it the same way each time.

• Run it on the homepage, one landing page, and one conversion page.
• Record the result in a short change log.
• Fix failures before shipping, unless you accept the risk deliberately.

Next step

Start small. Run this checklist for your next release. It will catch problems early and reduce emergency fixes later. For ongoing QA and release management, maintenance and support services can help you keep releases safe and reliable. For more on maintenance, see maintenance plans that pay for themselves.