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.
- 01Measure inline style and style-tag volume
- 02Find repeated declarations across pages
- 03Identify truly critical above-the-fold rules
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.
- 01Extract shared rules into cached assets
- 02Keep a small measured critical path if justified
- 03Use design tokens instead of repeated literal values
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.
- 01Compare first render and repeat navigation
- 02Check CSP style rules
- 03Test server and client rendering consistency
Common pitfall
A shortcut to avoid
Moving all critical CSS out of the document can introduce a flash or additional render-blocking work.
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.