How To Test Your Website Before You Tell Anyone It Is Live

There is a moment between the site being finished and anybody knowing about it. Most people spend it writing the announcement email.

Spend fifteen minutes of it on something else instead. The failures that make a new site look amateur are nearly all findable in one pass, and much cheaper to find before the first hundred visitors arrive than after.

The launch-day failures people actually notice

Nobody looks at a new site and remarks on the spacing. What they notice is much blunter than that.

A form that appears to send and goes nowhere. A menu link that opens a page saying Not Found. A phone number printed as plain text so it cannot be tapped. A photograph running off the right-hand edge on a phone, so the whole page slides sideways when they scroll. A first load slow enough that they wonder whether they typed the address wrong.

None of these are subtle, and none get reported to you. The visitor leaves, and if they were a prospective customer you never learn they existed.

That matters more at launch than at any other time, because the first wave of visitors is the one you invited personally: customers, suppliers, the people on your email list, the ones most likely to mention it to somebody else.

Test one: every form, submitted for real

Not a glance at the form. A real submission, with your real name and phone number, on every form the site has: contact, quote request, booking, newsletter signup, the little one in the footer.

Send it from outside. Use a personal email address rather than one at your own domain, because mail from your own domain can take a shortcut a stranger’s will not.

Then go and find it. Check the inbox. Check the spam folder, where a great many first submissions land. Check the address it delivers to still belongs to somebody who works for you. A form quietly feeding a former employee’s mailbox is one of the most common faults on a new site, and it produces no error at all.

Watch what the visitor sees. After submitting, does anything confirm it worked? A thank-you page, or a message where the form was. If the page simply reloads and empties, some people will send it again and the rest will assume it failed.

Then break it deliberately. Leave a required field blank and submit. You should get a clear message pointing at the field, not a silent refusal. Do this on a phone as well as a laptop.

Work through the site one page at a time and click everything. Dull, and about ten minutes on a small site.

Start with the navigation, then the buttons in the body, then the footer, where faults collect because nobody reads it. Check the logo goes back to the homepage. Check the phone number and email address are real tap-to-call and tap-to-email links. Check any PDF downloads, and is the current version.

The same failures repeat across launches. A button still pointing at a placeholder that goes nowhere. A link to the staging address the site was built on, showing the unfinished version or nothing. A social icon pointing at a profile you stopped using. A privacy or terms link to a page nobody ever wrote.

Check the outward links too (the supplier, the trade association, the directory listing). If one has moved, your page is the one that looks careless.

Test three: a real phone, not a narrow window

Dragging the browser window narrow tells you the layout reflows. It does not tell you what using the site is like, because your laptop has no thumbs, no mobile signal and no on-screen keyboard. Pick the site up on an actual phone and go through it as a visitor would.

Look for anything you cannot reach. Buttons too close together to hit reliably. A fixed header covering the top of a section when you jump to it. A popup whose close button sits off the edge of the screen.

Open and close the menu a few times. The collapsed navigation is the most common thing to be wrong on a phone, because it is the one part that behaves completely differently from the desktop version.

Try scrolling sideways. Put a finger on the page and drag left. Nothing should move. If it does, something is wider than the screen, usually an image or a table.

Fill in a form with the keyboard up. Check the field you are typing into is still visible, and that the keyboard offers numbers for the phone field.

If you can, borrow a handset of the other make. An iPhone and an Android do not always agree.

Test four: speed, and the one number to watch

Run the homepage and one busy inner page through a free speed testing tool, and read the mobile results, not the desktop ones.

You will get a page of numbers, most of which you can ignore. The one worth understanding is largest contentful paint, which sounds technical and means something ordinary: the moment the biggest thing in the visible part of the page, usually the main photograph or the headline, has finished drawing.

It is a good measure because it matches what a person means by "it has loaded", not the first pixel, not the last invisible script, but the moment the page looks like it has arrived. The tools grade it for you and say plainly whether it is good, needs work, or poor.

If it is poor, look at the main image first. A photograph straight off a camera is the usual culprit, and resizing and compressing it before re-uploading often moves the grade by itself.

The list to keep for next time

Write down what you found. Not a checklist copied from somewhere, but the specific things that were wrong on your site, because those are the ones most likely to be wrong again.

Every content change afterwards is a small launch. A new page, a swapped photograph, an edited form: the same faults reappear, and your own five-line list makes the check a two-minute habit rather than a project. Keep it in the notes app on your phone.

Running that pass after every change is exactly the sort of thing that gets skipped at the end of a busy week, and it is part of what a maintenance plan is for.