Every launch has a moment where someone opens the site on their own phone, taps the contact button and nothing happens. The difference between a good launch and an embarrassing one is whether that moment happens before the announcement or after it.
Check what people actually do, not what the page looks like
Most broken sites look fine. The layout holds, the images load and the headline is right. What breaks is the part that matters to the business: a form that never reaches the inbox, a checkout that fails for one payment method, a booking link that points to the staging server.
So testing starts with the journeys, not the pages. Someone tries to get in touch. Someone buys something. Someone signs up, forgets their password and resets it. Each journey is walked from start to finish, and each ends with proof that the right thing happened on the other side: the email arrived, the order was recorded, the account exists.
Test on the devices your audience uses
A site can be perfect in the latest desktop browser and awkward on a three-year-old Android phone with a small screen and a slow connection. For many audiences, that phone is the majority.
Analytics from an existing site tell you which browsers and screen sizes matter. Without them, a sensible spread is a recent iPhone, a mid-range Android, a tablet, and Chrome, Safari, Firefox and Edge on desktop. Real devices catch things emulators miss: the on-screen keyboard covering a field, a sticky bar hiding the button it was meant to promote, text that wraps into three lines where the design assumed one.
Break it on purpose
Users do not follow the happy path. They paste a phone number with spaces, submit a form twice, hit back in the middle of a payment and open the same page in two tabs.
Good QA includes a deliberate attempt to misuse the site. Empty fields, very long names, special characters, a slow network, a lost connection halfway through. Every one of these should end in a clear message, not a blank screen or a silent failure.
Check the parts nobody sees
Some of the most expensive mistakes are invisible on the page. A search setting left on "do not index" from the staging build. Analytics that fire twice, or not at all. Missing page titles, broken redirects from the old site, images with no descriptions, a privacy page that still describes the previous company.
We keep a written pre-launch list for these and go through it for every project, because memory is not a process.
Speed and access are part of the test
A page that takes six seconds to show its main content has failed, even if every link works. So has a page that cannot be used with a keyboard, or whose grey text disappears on a phone in sunlight. Performance and accessibility are measured before launch, not left for a later phase that rarely arrives.
Launch is a test too
The last check happens on the live site, minutes after it goes up. Domains, certificates, redirects, forms and tracking behave differently in production, and the only way to know is to test them there.
Then, a week later, we look again. Real traffic finds what testing missed, and it is better to hear about it from the error logs than from a customer.
