How to test a website manually?

3 June 2026 · By John Carlsson

Write test cases for the key user journeys, such as sign-up, checkout and forms, each with a clear expected result. Run them in Chrome, Firefox, Safari and Edge on different screen sizes, try unusual inputs as well as normal ones, and record every problem with exact steps to reproduce it.

When you test a website manually, the process involves creating structured test cases covering key user journeys, forms and navigation, testing across multiple browsers and devices, and documenting any issues with clear reproduction steps.

Start with structured test cases

To test a website manually, begin by creating structured test cases that cover key user journeys — signing up, completing a purchase, submitting a form — along with navigation and interactive elements. Each test case should have a clear expected outcome so it's obvious when something has failed.

Cross-browser and cross-device testing

Test across multiple browsers such as Chrome, Firefox, Safari, and Edge, as well as various devices and screen sizes, since layout or functionality issues can be specific to certain environments and easily missed if you only test on one setup.

Edge cases and documentation

Use both typical and unusual input data to uncover edge cases that average users might not trigger. When you find problems, document them clearly with step-by-step reproduction instructions so developers can replicate and fix them efficiently, and allow time for free exploratory testing to catch what scripted cases miss.

Manual testing vs automated testing

Automated tests are excellent at quickly re-checking the same known scenarios repeatedly, but they can't replicate genuine human curiosity and unpredictability. Manual exploratory testing — where a tester deliberately tries unexpected actions — often catches issues automated scripts were never written to check for in the first place.

A simple checklist to test a website manually

A practical starting checklist covers: does every link go where it should, do all forms submit successfully with both valid and invalid data, does the site look correct on at least one mobile and one desktop browser, and do any payment or signup flows complete fully from start to finish without errors.

Keeping a simple test log over time

Even a basic spreadsheet logging what was tested, when, and what was found creates a valuable record over time — making it easier to spot recurring issues, confirm whether a previously fixed bug has resurfaced after a later update, and demonstrate due diligence if a client or stakeholder asks how thoroughly a site has been checked.

What to prioritise when time for testing is limited

When time is short, prioritise testing the paths that directly generate revenue or capture leads — checkout flows, signup forms, contact forms — since failures here have the most immediate business impact. Cosmetic issues on rarely visited pages can reasonably wait for a later, more thorough testing pass.

Key Takeaways

Manual exploratory testing catches issues automated scripts were never written to check.
Cover links, forms, cross-browser rendering and full signup/payment flows at minimum.
Manual and automated testing work best as complements, not alternatives.

Frequently asked questions

What should a checklist include when you test a website manually?

A practical starting checklist covers four areas. First, check that every link goes where it should. Second, confirm that all forms submit successfully with both valid and invalid data. Third, make sure the site looks correct on at least one mobile browser and one desktop browser. Fourth, check that any payment or signup flows complete fully from start to finish without errors. Each structured test case should have a clear expected outcome, so it is obvious when something has failed, and issues should be documented with step-by-step reproduction instructions.

Is manual testing still needed if you have automated tests?

Yes. Automated tests are excellent at quickly re-checking the same known scenarios repeatedly, but they cannot replicate genuine human curiosity and unpredictability. Manual exploratory testing, where a tester deliberately tries unexpected actions or unusual input data, often catches issues that automated scripts were never written to check for in the first place. Manual and automated testing work best as complements rather than alternatives, with automation handling repetitive regression checks and manual testing uncovering edge cases and problems no one anticipated.

Which browsers and devices should a website be tested on?

Manual testing should cover multiple browsers such as Chrome, Firefox, Safari and Edge, as well as a range of devices and screen sizes. Layout or functionality problems can be specific to certain environments and are easily missed if you only test on one setup. When time is limited, prioritise the paths that directly generate revenue or capture leads, such as checkout flows, signup forms and contact forms, across these environments. Keeping a simple test log over time also helps you spot recurring issues and confirm fixed bugs have not resurfaced.