How to test my website before visitors see it

The owner tests from inside the site. They are logged in, the cookie banner was dismissed months ago, and they know which menu item comes next. A stranger arrives from an old bookmark, and that link points at a page that moved. The first failure shows in the address bar, as a certificate warning on one version of the domain. The second is a footer link to a preview behind a password. The third is a form that shows a thank you while the message lands in an inbox nobody reads. One pass by the owner misses all three, because the owner never reaches those stops.

• Open the address in a private window on a phone. Does it load with no warning and no password screen?
• Click every menu item and footer link. Note the address each one lands on, and whether it is yours.
• Send one normal entry through each form, then read the message on screen, not only the thank you line.

The address comes first, and a small site often gets it wrong. A site can answer at the www version and not at the bare domain, so one of them shows a certificate warning. A redirect can send the old address to a page that no longer exists. Open each version in a private window. The address that finally shows should be the one you want people to save, with no warning.

Then look at what the page loads before anything else. A script or image from a server that is down leaves a gap, and a blank page is a stop the visitor never reports. The developer tools list each request with its status code: a 404 means a missing page, a 500 means the server broke, and a request that never finishes is waiting on something that will not answer.

Test a site before launch

A visitor reads the page from the top and tries the first thing that looks like the answer. Walk it in that order: the hero button, then the menu, then the links in the body, then the footer. Each link should open a page you meant to publish, on your own address. A footer link to a preview, a staging copy or a draft is an easy stop to miss, because the team rarely clicks the footer on its own site.

The forms come last, and they fail more quietly. A contact form can show a thank you message while the request fails in the background, or it can send the message to an address that nobody checks. Send one normal entry and read the confirmation on the screen. If the form sends the visitor a copy, check that it arrives in their inbox and not in spam, and that the link in it opens a page that exists.

When a stop happens, the address bar is your first piece of evidence. If it shows an address that is not yours, the visitor was sent elsewhere, usually by a link or a redirect. If it shows your address with a not found message, the page was moved or deleted. If the page is blank, check the Console for a script error, because one broken embedded widget can stop the rest of the page from drawing. A simulated run records the same stops, with the step, a screenshot and any JavaScript error, so you can match the address to the step.

Each menu edit, domain change or new contact form can send a link somewhere new. Run the walk again after every change, and once more when the domain goes live. With paid credits, a run can use a site password or bypass secret on a protected preview, so the visitors can reach the pages behind it.