Choose representative pages
Include a normal landing page and a heavier journey such as search or an authenticated view. Note the device, connection, cache state and whether the user is signed in.
Inspect the waiting time
A slow initial response may need server, database or extension investigation. Large media and expensive scripts create different browser costs and need different changes.
Test caching carefully
Confirm which content can be shared and which depends on the user or session. A faster response is not an improvement if it exposes private or outdated information.
Measure the change
Repeat comparable checks and verify functionality. Use real-user evidence when available; a lab score is a diagnostic, not proof that every visitor's experience improved.