PageSpeed Insights

Google’s tool for performance analysis. Shows Core Web Vitals and optimisation recommendations.

In brief

PageSpeed Insights (PSI) is a free tool from Google that analyses a web page’s performance on mobile and desktop. It combines field data from the Chrome User Experience Report (CrUX) with lab data (Lighthouse), returning a score from 0 to 100 and actionable optimisation recommendations.

What PageSpeed Insights shows

  • Performance Score — overall score from 0 to 100
  • Core Web Vitals — LCP, INP, CLS (based on field data)
  • Lab Data — Lighthouse simulation
  • Opportunities — actionable speed improvements
  • Diagnostics — detailed technical analysis

Field Data vs Lab Data

  • Field Data — real visitor data from Chrome UX Report (28‑day average). The most reliable source.
  • Lab Data — one‑time test in a simulated environment (Lighthouse). Useful for debugging, but may differ from real experience.

Score interpretation

  • 90–100 — good: maintain current performance.
  • 50–89 — needs improvement: optimise.
  • 0–49 — poor: urgent fixes required.

Key recommendations

  • Eliminate render‑blocking resources — inline critical CSS, use defer/async for JavaScript.
  • Properly size images — use srcset and responsive images.
  • Serve images in next‑gen formats — WebP, AVIF.
  • Reduce unused JavaScript — code splitting, tree shaking.
  • Minimise main‑thread work — optimise heavy JS tasks.

API automation

JAVASCRIPT
// PageSpeed Insights API call example
const url = 'https://www.googleapis.com/pagespeedonline/v5/runPagespeed';
const response = await fetch(`${url}?url=https://example.com&key=YOUR_API_KEY`);
const data = await response.json();
console.log(data.lighthouseResult.categories.performance.score);
A perfect lab score does not guarantee good real‑user speed. Always compare field data (CrUX).

Common questions

Lab tests depend on server load, network conditions, and device emulation. Test multiple times at different hours for consistency.
Follow the recommendations: optimise images, minimise CSS/JS, use CDN and caching, reduce the number of requests.
Actual speed (measured through CrUX and analytics). The score is an indicator, not the goal. Focus on Core Web Vitals and user satisfaction.
Direct contacts

Discuss your project?

Share your goals and website context — I will suggest a practical next step.

PageSpeed Insights — What is it?