PageSpeed Test
Real Lighthouse audit, mobile + desktop in one go. Core Web Vitals, real-user metrics from CrUX, and a prioritized list of what to fix.
PageSpeed tests can take 20-60 seconds. Public URLs only — won't work on localhost.
What to fix — grouped by area
Click "Copy as ticket" on any issue to get a developer-ready snippet on your clipboard.
Page diagnostics
What these numbers mean
Core Web Vitals (the ones Google ranks on)
- LCP — Largest Contentful Paint. How fast the biggest visible element renders. Good ≤ 2.5s, poor > 4s.
- INP — Interaction to Next Paint. How fast the page responds to clicks/taps. Good ≤ 200ms, poor > 500ms.
- CLS — Cumulative Layout Shift. How much the page jumps around as it loads. Good ≤ 0.1, poor > 0.25.
These three are direct Google ranking factors. Pages in the "good" tier rank measurably higher than "poor" pages on equivalent content.
Lab data vs. field data
Lab data — what Lighthouse measures right now in a controlled environment. Useful for debugging but doesn't reflect real users.
Field data (CrUX) — what real Chrome users actually experienced over the last 28 days. This is what Google uses to rank your page. Only available for sites with enough traffic.
Why this matters for AEO
Google AI Overviews and Search Generative Experience demote slow pages even more aggressively than classic search. AI engines also use real-user data — if your site is slow for actual users, AI engines deprioritize you as a source.
The biggest wins, usually
- Convert images to WebP/AVIF and add
loading="lazy" - Set explicit
width+heighton images and videos - Eliminate render-blocking JavaScript (defer non-critical scripts)
- Self-host fonts with
font-display: swap - Enable text compression (Gzip/Brotli) on the server