Measure the affected page separately from the rest of the site. Business-critical website changes deserve a repeatable test. Use realistic products, page URLs and enquiries so the check reflects what customers can actually do.
Working through the details
Check oversized images, scripts and render-blocking assets before changing plugins.
A check you can repeat
Repeat the test under comparable conditions and record the change. Write down the expected result before testing. Keep a short record of the device, page or product tested, the outcome and the person responsible for any follow-up.
Test it on a practical example
As a working exercise, choose one live example you can check from start to finish. Write down the intended result before comparing versions, or it will be difficult to tell whether a later change improved anything.
- Check oversized images, scripts and render-blocking assets before changing plugins.
- Repeat the test under comparable conditions and record the change.
- Compare the final result with the intended use, and record who will confirm that it is ready.
Test a straightforward purchase or edit alongside a case with an exception. Choose a real combination of device, product and customer action. Check both sides of the workflow: what the visitor sees and what appears in the administration area, inbox or order record. Compare each result with the expected outcome before deciding what to change.
What to record before sign-off
Keep a short handover with the test data, expected result and person responsible for follow-up. For changes to a live shop, identify how to restore the earlier behaviour if an important task stops working.
For help with this work, explore our website maintenance in East Kilbride and Glasgow or tell us about your project.