Start a project

A website testing checklist to run before you launch

3 min read

Forty checks to run before a website goes live, grouped by journeys, browsers, forms, speed, accessibility and search. Use it as your pre-launch list.

A hand ticking off items on a handwritten checklist in a notebook

Launch day is a bad time to find out the contact form sends nothing. This is the list we work through before a site goes live. It is ordered so that the checks most likely to cost you money come first.

1. The journeys that earn money

Test each one from the first click to the final confirmation, as a new visitor.

  • Sign up, including the confirmation email arriving and its link working
  • Log in, log out, and reset a forgotten password
  • Search, filter, and open a result
  • Add to basket, change quantity, remove an item
  • Check out with a real test payment, and a declined card
  • The confirmation page and the confirmation email
  • The contact form, and where its message actually lands

2. Browsers and devices

  • Chrome, Safari, Firefox and Edge on a laptop
  • Safari on an iPhone and Chrome on an Android phone
  • A small phone (around 360 px wide) and a tablet
  • Portrait and landscape
  • The page at 200% zoom

Safari on iPhone deserves its own pass. It is the browser most often missed and one of the most used.

3. Forms

  • Every required field refuses to submit when empty
  • Error messages say what is wrong and how to fix it
  • The form keeps what was typed when an error appears
  • Email, phone and date fields open the right keyboard on a phone
  • Pressing Enter submits the form
  • Double-clicking Submit does not send it twice
  • Very long input and unusual characters do not break the page

4. Content

  • No placeholder text or test data left anywhere
  • No broken links (run a link checker over the whole site)
  • No broken or stretched images
  • The 404 page exists and helps people find their way
  • Prices, currencies, dates and phone numbers are in the right format
  • Legal pages are present: privacy policy, terms, cookie notice if you need one

5. Speed

Measure on a mid-range phone, not your development machine. Google's Core Web Vitals give you three targets:

  • Largest Contentful Paint under 2.5 seconds: the main content appears quickly
  • Interaction to Next Paint under 200 milliseconds: the page reacts when tapped
  • Cumulative Layout Shift under 0.1: things do not jump around while loading

Also check that images are compressed and sized for the screen, and that the page is usable before every script has loaded.

6. Accessibility

  • Every action works with the keyboard alone
  • The focused element is always visible
  • Images that carry meaning have alt text
  • Text has enough contrast against its background
  • Form fields have labels, and errors are announced

7. Search engines and sharing

  • Every page has its own title and description
  • There is one h1 per page
  • The sitemap exists and lists the right pages
  • robots.txt is not blocking the whole site (a common leftover from staging)
  • The staging "noindex" tag has been removed
  • Sharing a link shows the right title, description and image

8. The things around the site

  • HTTPS works, and http:// and www redirect to one address
  • Analytics is recording visits
  • Forms and orders reach the right inbox
  • Backups run, and you have restored one at least once
  • Someone gets an alert if the site goes down

How to use this

Do not try to do all of it in the last hour. Run sections 1 to 3 a week before launch, so there is time to fix what you find, then run section 1 again on launch day.

Write down what you tested and on which browser. "We tested it" is not a record. "Checkout passed on Safari iPhone 15 and Chrome Android on 12 March" is.

If you would rather have someone outside the team run it, that is what our website testing is. For the speed and accessibility sections in depth, see performance testing and accessibility testing.

Chat with us