Add a public-page check to your release review.
Use an external observation alongside your own application tests. Keep the evidence narrow enough that the team knows what passed and what remains unknown.
Start with one public page
No account is needed for the public check. Results depend on the page and available measurement providers. A scan does not submit forms or change your site.
Review tasks
- Before a release
- Record the current public-page behavior that matters to the change. Use your own test environment for private or authenticated functionality.
- After deployment
- Review the affected page and compare available configuration and performance checks with prior evidence.
- During investigation
- Separate a check failure from a measurement failure. A timeout should not silently become a passing result.
Where it fits
A header configuration change
Inspect the response observed after a deployment and verify the intended policy with the application owner.
A template or dependency update
Use page findings to guide further investigation, then run the application and browser tests required for the change.