Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Record the network waterfall
- 02Identify render-blocking and priority inversions
- 03Check preloads, preconnects and lazy loading
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Prioritize the actual hero and critical styles
- 02Delay below-the-fold and optional resources
- 03Remove speculative hints that do not pay back
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Test cold cache on realistic networks
- 02Check largest contentful paint and bandwidth
- 03Compare pages with and without each hint
Common pitfall
A shortcut to avoid
Preloading many assets labels everything important and can delay the resource that actually matters.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.