Free Page Speed Checker
Run Google PageSpeed Insights on any URL. Get real Core Web Vitals, Lighthouse scores and optimisation opportunities in seconds. Powered by Google's official API.
Please check the URL and try again.
Running Lighthouse audit…
Google is analysing your page. This usually takes 15–30 seconds.
Core Web Vitals
Lab data (Lighthouse)Enter a URL to get started
Paste any public URL above and click Run Test. We'll run a real Lighthouse audit powered by Google's PageSpeed Insights API.
What Is Page Speed?
Page speed is how fast a web page loads and becomes usable for visitors. It's measured in real time by Google's PageSpeed Insights API, which runs a synthetic Lighthouse audit and combines it with real-world data from the Chrome User Experience Report (CrUX).
Since 2021, Core Web Vitals have been a Google ranking signal. Speed is not a trump card — relevance wins first — but faster pages consistently rank better in tied situations, convert better and reduce bounce rate.
The 3 Core Web Vitals
| Metric | What it measures | Good target |
|---|---|---|
| LCP | Largest Contentful Paint — how fast the biggest element (usually hero image or heading) becomes visible. | < 2.5 s |
| INP | Interaction to Next Paint — how fast the page responds to clicks, taps and key presses. | < 200 ms |
| CLS | Cumulative Layout Shift — how much visible content jumps around while loading. | < 0.1 |
What the 4 Lighthouse scores mean
- Performance — the overall speed score derived from LCP, FCP, TBT, CLS and Speed Index. This is the one that most affects SEO.
- Accessibility — how well the page works for screen readers, keyboard users and people with visual impairments. Colour contrast, ARIA labels, alt text.
- Best Practices — HTTPS, no console errors, correct image aspect ratios, no deprecated APIs.
- SEO — meta tags, crawlability, mobile-friendliness, structured data, legible font sizes, tap target sizes.
What's a good PageSpeed score?
- 90–100 (green) — Fast. Great for SEO and user experience.
- 50–89 (orange) — Needs improvement. Significant wins are usually available.
- 0–49 (red) — Slow. Losing traffic to competitors. Fix urgently.
For SEO, aim for at least 90 on mobile. Mobile scores are always lower than desktop because Google simulates a mid-tier phone with 4G and 4× CPU throttling. Desktop uses a fast connection with no throttle.
Why mobile scores are lower
Lighthouse uses different throttling presets:
- Mobile: 4× CPU slowdown + simulated slow 4G (1.6 Mbps down, 750 Kbps up, 150 ms latency).
- Desktop: 1× CPU (no throttle) + simulated cable connection (10 Mbps).
A 90 on mobile typically means near-perfect performance on actual devices. A 90 on desktop is a lower bar.
Common speed problems & fixes
- Unoptimised images. Convert to WebP, compress, and use responsive
srcset. This is the single most common fix. - Render-blocking resources. Inline critical CSS, defer non-critical JS, use
font-display: swap. - Too much JavaScript. Code-split, tree-shake, remove unused libraries. JS is the #1 cause of poor INP.
- No text compression. Enable Brotli or gzip on your server — instant 70% reduction in HTML/CSS/JS size.
- No caching. Set long
Cache-Controlheaders on static assets. - Slow server response. Improve TTFB with a CDN, HTTP/3, or a faster host.
- Layout shift from ads and embeds. Reserve space with
widthandheightattributes or CSSaspect-ratio. - Too many third-party scripts. Analytics, chat widgets, ads, A/B tools — each adds hundreds of KB and main-thread work.
Lab data vs field data
PageSpeed Insights shows two types of data:
- Lab data (Lighthouse) — a single synthetic test run in a controlled environment. Good for debugging specific issues.
- Field data (CrUX) — real-user measurements aggregated over the last 28 days. This is what Google uses for rankings. Only shown for pages with enough traffic.
If your field data shows a worse score than your lab data, real users on slower devices are struggling. If field data is missing entirely, your page may not have enough traffic to be included in CrUX yet.