PageSpeed Insights
Lab and field metrics for URLs — Core Web Vitals and audits without installing Lighthouse locally.
Why it earns a place
Why I use it
Fast feedback on real URLs and mobile vs desktop — pair with Search Console field data so you do not optimize lab scores that users never feel.
Use cases
Best for
- Diagnosing a live website with measurable evidence
- Creating a baseline before changing performance, search, or tracking
- Verifying that a shipped change improved the visitor experience rather than only the implementation
Start small
Quick start
- 01Start from one live page or property
Choose the URL/property and one question you need answered. Avoid opening every report.
- 02Record the baseline
Run the relevant PageSpeed Insights report and save the metric, date, device/segment, and any caveat that changes interpretation.
- 03Ship one change and repeat
Make the smallest meaningful improvement, then rerun under comparable conditions before moving to the next issue.
Repeatable workflows
Things I come back for
Run a focused diagnostic
Turn a score or report into one next action.
- 1
Open the exact production URL/property.
- 2
Identify the single metric or issue that blocks the current goal.
- 3
Record the baseline and fix one cause before rerunning.
Verify after deployment
Keep before/after comparable.
- 1
Wait until the change is actually live.
- 2
Repeat the same device, URL, date range, or test conditions.
- 3
Keep the change only when the user-facing outcome moves in the right direction.
Reference