How is a website tested before launch?

A new website should be thoroughly tested before launch, because the first visitors are often the ones you paid to attract through ads or announcements. Broken forms, slow phones or a missing page can waste that attention. A structured test plan catches these problems while they are still cheap to fix.

Here is what a good test covers, and a checklist you can use yourself.

What gets tested before launch

Devices and browsers

Most visitors use phones, so mobile testing comes first. Check menus, buttons and forms with your thumb, on both iPhone and Android if possible. Then check the main desktop browsers. Look for overlapping text, cut-off images and buttons that are too small.

Forms, links and content

Submit every form and confirm the message reaches the right inbox. Click every link in menus and footers. Read every page once more for typos, outdated prices and placeholder text. Broken links and “lorem ipsum” are the most common launch-day embarrassments.

Speed and SEO

Run key pages through Lighthouse or PageSpeed Insights. Google’s Lighthouse overview explains the scores. Check that each page has a unique title and description, that search engines are allowed to index the site and that a sitemap exists.

Accessibility

A quick accessibility check improves the site for everyone. Check colour contrast, add alt text to images, make sure forms have labels and test that you can move through the page with the Tab key. The W3C’s evaluation resources offer easy first checks.

Launch-day checks

1. Point the domain and confirm HTTPS works everywhere.
2. Set up redirects from any old URLs.
3. Confirm analytics and conversion tracking are recording.
4. Submit the sitemap in Google Search Console.
5. Take a fresh backup.

Example: what testing caught

A consultancy’s new site was tested before launch over three days. The checks found that the booking form sent emails to an old address, the mobile menu hid the phone number and two service pages were blocked from search engines by a leftover setting. All were fixed in an afternoon. Without testing, the launch campaign would have sent paid visitors to a site where enquiries vanished. Every site we build is tested before launch using this checklist.

Do it yourself in 30 minutes

• Open the site on your phone using mobile data.
• Submit every form and check your inbox.
• Click every menu and footer link.
• Read the home page and contact page aloud for errors.
• Run our speed checker on the home page.

Testing after changes, not just at launch

A site that was tested before launch can still break later, when plugins update, content changes or new features are added. Repeat a short version of the checklist after every significant change: submit the forms, check the main pages on a phone and run a speed test. Stores should place a test order after any checkout or payment change. Treat testing as a habit, not a one-off event. The same discipline that kept the site safe when it was tested before launch keeps it reliable for years afterwards.