How to test a website manually?
Start with structured test cases
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.
Building a simple manual test checklist
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.