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.
- 01Map client entry points and imported dependencies
- 02Find server-capable components marked client
- 03Trace secrets and privileged operations
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.
- 01Move data and noninteractive rendering server-side
- 02Keep client components small and explicit
- 03Pass serializable data across the boundary
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.
- 01Inspect built client bundles
- 02Test hydration and navigation
- 03Confirm privileged code never enters browser output
Common pitfall
A shortcut to avoid
Moving everything server-side can create round trips and awkward interaction for state that belongs close to the user.
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.