Choose a language

Web project manager reviewing a test plan before launch

Website Acceptance Testing Checklist: Ship With Confidence

Published November 5, 2026 · Mis à jour le November 16, 2026 · 19 min read

You can run a complete pre-launch QA pass on a small site in one afternoon. The trick is order: broken forms and links cost money the moment you go live, while a missing alt tag does not. This checklist runs in that order, and every item tells you what to click, where to look, and what proves a pass.

You will get a three-tier checklist (stop-ship, should-fix, backlog), six testing blocks covering conversion paths, links, SEO, speed, mobile, accessibility, security and analytics, plus a short 72-hour post-launch re-test. Everything is written for one non-engineer testing alone.

The path in 7 steps

The steps of this page, in order.

  1. 01 Know your blockers Sort every issue into stop-ship, should-fix or backlog before you start clicking.
  2. 02 Test the money path Walk every form, signup and checkout the way a real visitor would.
  3. 03 Check links and index Crawl the site for 404s, bad redirects and duplicate canonical tags.
  4. 04 Measure speed Run key templates through a field or lab performance tool and compare to published thresholds.
  5. 05 Try small screens Open your top pages on a real phone and a second browser.
  6. 06 Sweep access, security, tags Check alt text, contrast, keyboard use, HTTPS, exposed paths and analytics events.
  7. 07 Re-test for 72 hours After launch, confirm forms, redirects and tags still fire on the live domain.

01 / 12

What absolutely has to be tested before launch?

Test in this order: conversion paths, links and index tags, speed on key templates, mobile, accessibility basics, security hygiene, then analytics and consent.

The first four items on the list move revenue or rankings right away. The last three protect you from silent damage that compounds over time. Fix them in this order so the most expensive problems get caught first.

A solo tester at a small business can finish the stop-ship tier in two to three hours on a small site, and the full pass in one afternoon. What you can actually cover depends on your CMS, your hosting and whether you have staging. Note those three before you start.

  1. Open staging and set a baseline

    Load the site in a clean browser profile. Note the CMS, hosting and staging setup, then start a timer.

  2. Test conversion paths

    Submit every form, complete a checkout or signup, and confirm confirmation emails arrive and data lands where it should.

  3. Click primary navigation and footer links, verify 301s point to the right pages, and confirm no stray noindex tags or wrong canonicals.

  4. Measure speed on key templates

    Run PageSpeed Insights or Lighthouse on home, a product or service page, and a blog post. Record LCP, INP and CLS against Google's published thresholds.

  5. Verify mobile, accessibility and security basics

    Resize to a phone viewport, tab through forms, check heading order and alt text, and confirm HTTPS, security headers and no exposed admin pages.

  6. Use browser dev tools or a tag inspector to watch pageviews, key events and consent signals trigger in real time before you sign off.

Test checklist next to a laptop showing a web page

02 / 12

Is the site fast enough on the pages that matter?

Measure only the templates that carry traffic or revenue, homepage, top landing pages, a product or service page and the blog post template.

Start with field data: the Chrome UX Report (CrUX) shows how real visitors experienced your URLs over the last 28 days. If a template has no field data, run Lighthouse or PageSpeed Insights in lab mode and treat the result as a hypothesis, not a verdict.

Compare against Google's published Core Web Vitals thresholds, an LCP of 2.5 s or less, INP of 200 ms or less, CLS of 0.1 or less at the 75th percentile. A 95 performance score with a failing LCP is still a fail; the score is not the metric.

Worked example

From raw LCP delay to a passing LCP

Largest contentful element
Hero image (product page)
Measured LCP (field, 75th percentile)
3.1 s
  1. TTFB0.6 s

    server response + connection

    HTML arrives after 600 ms.

  2. Resource load time1.8 s

    download + decode of the hero image

    The image is served at 2400 px wide for a 600 px slot.

  3. Render delay0.7 s

    main-thread work before paint

    A third-party chat script blocks rendering.

  4. LCP before fix3.1 s

    0.6 + 1.8 + 0.7

    Above the published 2.5 s threshold.

  5. Hero image saving−0.8 s

    resize to 600 px + convert to WebP/AVIF

    Resource load drops from 1.8 s to 1.0 s.

  6. LCP after fix2.3 s

    0.6 + 1.0 + 0.7

    Below 2.5 s without touching TTFB or the third-party script.

What this result assumes
  • Field data varies by device, network and geography; re-measure after the change.
  • The 800 ms saving is an example for this configuration, not a universal gain.
  • LCP is one of the three Core Web Vitals; INP and CLS still need to pass.

03 / 12

What should I have ready before I start clicking?

Gather five things first, or you will bounce between tabs and lose the thread.

Set up a staging URL that mirrors production content, a CMS login, and a test email inbox you control. Without all three, you cannot verify a form submission or check what a real confirmation message looks like.

Then write down your top five pages by traffic or revenue, and inventory every form, signup, and checkout on the site. Keep one spreadsheet or issue tracker open so each failure lands there with a screenshot and the exact URL.

Staging access

Confirm the staging URL loads the same content as production. Bookmark it so you never test on the live domain by accident.

CMS login

Log in once before the pass starts. If a password reset is pending, you will lose twenty minutes mid-checklist.

Test inbox

Use an email address you own and can open. This is where you confirm form notifications and autoresponders actually arrive.

Page list

Name your top five pages by traffic or revenue. Those get tested first, and they set the bar for everything else.

Form inventory

List every form, signup, and checkout on the site. A form you forgot to count is a form you will not test.

Issue tracker

Open one spreadsheet or tracker before you start. Every failure goes in with a screenshot, the URL, and the browser you used.

Two colleagues checking a site on a phone and a desktop screen

04 / 12

How do I test forms and the conversion path?

Submit every form the way a real visitor would, then confirm the success page, the error state and the email that lands.

Start with a valid submission: fill every required field, use an email address you can open right now, and keep the message short. Then break it on purpose. Submit with an empty required field, a made-up address and a 2,000-character message. You want to see a clear error next to the field, not a generic banner or a silent failure.

Once the success message appears, check that it names the right form. Then open the inbox: the confirmation email should arrive in a few minutes, not in spam. If you take payment, run a live test with a small amount when your processor supports it, or at least verify the sandbox end-to-end and confirm the live key is switched on.

Required fields

Submit with one required field blank. You should get a specific message next to that field, and the form should not send anything.

Validation messages

Type an email like test@test and a phone number with letters. Each field should show its own plain-English error, not a generic red banner.

Success state

Complete a valid submission. The page you land on should name the form you filled in, so you know it is the right one.

Error state

Force a failure: use a duplicate email, or temporarily block the send endpoint. The user should see a message with a next step, and no data should silently disappear.

Email delivery

Open the inbox you used. The confirmation should arrive within a few minutes and sit in the main inbox, not in spam or promotions.

CRM or autoresponder record

Search the CRM or email tool for the exact address you submitted. The record should exist with the right tags and list, within a minute or two.

Going further

See common form failures

06 / 12

Does the site work on phones and other browsers?

Open your top pages on one real iPhone, one real Android and one non-default desktop browser, not just the responsive preview.

Start with your three highest-traffic pages plus one form page. On each, check that tap targets are at least 44 pixels, body text is readable without pinch-zoom, and nothing forces horizontal scroll.

Then walk one full conversion path on a real phone: open the menu, tap the form, fill it, submit, and confirm the email arrives. Watch that the sticky header never covers the submit button and cookie banner buttons stay tappable.

Mobile and cross-browser sanity matrix

PageiPhone SafariAndroid ChromeDesktop ChromeDesktop Safari
HomepagePassPassPassPass
Top landing pagePassPassPassPass
Form / contact pagePassPassPassPass
Full conversion pathPassPassPassPass

Run this grid on real devices over Wi-Fi and one slower cellular connection. Mark any cell with a tap-target, zoom, horizontal scroll, header overlap or menu failure as a fail.

07 / 12

What accessibility basics should I check?

Four checks catch most real-world failures, and every one is doable without a screen reader.

Keyboard testing is the fastest signal: press Tab from the address bar and watch where focus goes. Every link, button and field needs a visible ring, in an order that matches the reading flow. A focus indicator hidden behind a sticky header fails, not just an invisible one.

Then check text alternatives: every image needs alt text that carries its meaning, and decorative images need an empty alt. Buttons and links must make sense read alone, and body text must hit WCAG 2.2 AA contrast, the W3C's 5 October 2023 standard.

Keyboard focus is visible

Tab through the homepage and landing page. Every interactive element must show a clear focus ring. If you cannot see where you are, keyboard users cannot either.

Focus order is logical

Tab from top to bottom. Focus should move in the same order you would read the page. A skip link should be the first thing a keyboard user reaches.

Images have alt text

Check each image in the inspector. Informative images need a short description of what they convey; decorative images need an empty alt attribute, not a missing one.

Read every link and button out of context. "Learn more" fails; "Download the 2026 benchmark" passes. This also helps screen reader users who navigate by links list.

Contrast meets WCAG 2.2 AA

Test each body-text and font pairing with a contrast checker. Normal text needs 4.5:1; large text (18pt or 14pt bold) needs 3:1. WCAG 2.2 was published by the W3C on 5 October 2023.

Form fields have labels

Every input needs a visible, programmatically associated label. Placeholder text is not a label. Check that error messages name the field and say how to fix it.

Going further

See what changed in WCAG 2.2

08 / 12

What security and privacy items should I verify?

Six hygiene checks catch the mistakes that put a small site in the news, and none of them require a security background.

Load every key page and watch the console. If a secure page pulls an image or script over insecure HTTP, that is mixed content, and the padlock may disappear or a warning may show. Browse the HTTP version of each URL too; it should redirect to the HTTPS one.

Try opening /admin, /wp-admin and /staging in a private window. They should not be reachable. On the CMS login, confirm 2FA is on (a second code from an app or text) and no default usernames remain.

HTTPS on every page

Load each key URL and confirm the address starts with https:// and the padlock is intact. If a page loads over HTTP, it fails.

No mixed content

Open the browser console and reload. Any line naming a http:// resource on an https:// page is mixed content and must be fixed.

HTTP redirects to HTTPS

Type the http:// version of a page. It should send you to the https:// version automatically. If it loads insecurely, it fails.

Admin and staging paths are not public

In a private window, try /admin, /wp-admin and /staging. You should get a login wall, a 404, or a block, never a live page.

No default credentials, 2FA on

Check the CMS user list for names like 'admin' or 'editor'. Turn on two-factor authentication for every account that can publish.

Confirm the privacy policy is dated and current. Before any non-essential cookie is set, a consent banner should ask the visitor to accept or reject it.

Going further

See the header checklist

10 / 12

What should I re-test in the first 72 hours?

The launch is not the finish line. Some checks that passed on staging can fail on the live domain, so re-run them within 72 hours.

Staging lies in small ways. Mail relays, spam filters and API endpoints usually point somewhere else on the live domain, so the same form that passed last week can silently drop submissions. Send one real test through every form on production and confirm the message arrives in the inbox you actually monitor.

Redirects and canonicals also resolve differently once DNS switches. Watch your analytics for new 404s and compare conversion volume with the prior week. Then confirm the cookie banner, privacy policy and consent log all match what is live, and log every error you find.

Form delivery (hour 1)

Submit each production form with a real address and confirm arrival, reply-to and spam placement.

Redirect map (hour 1)

Click every high-traffic legacy URL and verify it lands on the intended live page, not a soft 404.

404 log (hour 24)

Review server and analytics 404 reports for URLs that were live on staging but missing in production.

Analytics baseline (hour 24)

Compare sessions and conversions against the previous week to catch a broken tag or a silent drop.

Load the banner in a clean browser and confirm the recorded choice matches the live privacy policy.

Error log review (hour 72)

Read the application and CDN error logs once more, then move anything unresolved into your issue tracker.

11 / 12

Which of these issues must block the launch?

Only the stop-ship tier blocks the launch. Everything else can ship today with a named owner and a date.

Stop-ship covers anything that loses money or leaks access: a broken form or checkout, an exposed admin or staging path, missing HTTPS, a broken canonical on a top page, a dead consent banner. Fix these before the site goes live.

Should-fix within a week includes missing alt text on key images, one broken internal link on a low-traffic page, or a heavy image on a secondary page. Backlog is cosmetic issues, one-off warnings, and improvement ideas, record each one, name an owner, set a deadline.

12 / 12

Frequently asked questions

Frequently asked questions
The Web Insider editorial team
About the author The Web Insider editorial team

Web Insider is a practical magazine for people who build, run or grow a website. Every fact is checked against its official source, and every test shows its proof.

Your feedback

Was this page helpful?

Share

Could this page help someone?

Related reading

Read next

Abstract certification badge on a tag management interface
Guides & How-tos

Is There a Google Tag Manager Certification?

There is no official Google Tag Manager certification, only GTM training inside Skillshop and third-party certificates. Here is what each one actually proves to an employer.

·13 min
Two B2B professionals looking at a marketing dashboard
Guides & How-tos

B2B Inbound Marketing: A Simple Method That Works

B2B inbound marketing turns your website into a lead engine instead of a brochure. Here is a sequenced, small-team method you can start executing this quarter.

·16 min
Marketing team discussing a target audience around a computer
Guides & How-tos

Target Marketing: A Simple Method to Pick Your Audience

Target marketing means choosing one specific group of buyers and tailoring your product, message, and channels to them. Here is a repeatable five-step method, a scoring table you can copy, and a one-page audience brief.

·15 min
Team mapping a marketing workflow with cards next to a laptop
Guides & How-tos

Marketing Automation: Workflows to Plan First

Pick the workflows before the platform. This guide walks a small marketing team through the sequences worth building first, the data each one needs, and how to launch without breaking your CRM.

·22 min
Explore the topicData & Analytics

Audience measurement, Google Analytics 4 and Google Tag Manager: set them up, check them and keep your data reliable.

Explore the topicWebsites & Platforms

WordPress, Shopify, PrestaShop and WooCommerce: run, integrate and maintain a site without making it fragile.

Explore the topicGuides & How-Tos

Methods, training and practical benchmarks to scope a web project, test a site and make better decisions.

Explore the topicSecurity & Compliance

Backups, updates, GDPR, cookies and audience measurement: keep a site safe and compliant.