Test any page’s speed on mobile or desktop: Google performance score, Core Web Vitals from real users (LCP, INP, CLS), lab metrics and the top fixes.
Find out how fast your page really is, the way Google measures it. The website speed test runs Google’s PageSpeed Insights on any URL and shows two things side by side: Core Web Vitals from real Chrome users over the last 28 days (LCP, INP and CLS, the data Google uses in ranking), and a fresh Lighthouse lab test with your performance score, load metrics, a screenshot and the fixes that would save the most time. Test on mobile, which Google uses for ranking, or on desktop.
Test your homepage, a key landing page or a blog post. Each page is measured separately because each loads different code and images.
Mobile simulates a mid-range phone on a slow 4G connection, which is the version Google indexes and ranks.
Real-user data decides whether you pass. If the page has too few visitors, the origin (whole-site) data or the lab test is shown instead.
The fixes are ordered by the time they could save: start at the top, deploy, then test again.
Google’s own PageSpeed Insights engine (Lighthouse)
Real-user Core Web Vitals from the Chrome UX Report
Mobile and desktop tests
Fixes ranked by time saved
Screenshot of how the page finished loading
Free, no sign-up
Need more depth? Try Full SEO Audit →
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading: when the main content appears | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP (Interaction to Next Paint) | Responsiveness to taps and clicks | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | Visual stability: content jumping around | ≤ 0.1 | 0.1–0.25 | > 0.25 |
A page passes Core Web Vitals when at least 75 % of visits are “good” on all three. INP replaced FID as a Core Web Vital in March 2024.
Field data comes from the Chrome UX Report: real visits on real devices over the past 28 days. It is what Google uses for the page experience signal, but it needs enough traffic and changes slowly after a fix. Lab data is a single Lighthouse test in a controlled setting. It updates immediately, which makes it the best way to check a fix, but your score can move a few points between runs.
Then run the website SEO checker for the rest of your on-page and technical SEO, and check page weight with the page size checker.
It uses the same engine: Google’s PageSpeed Insights API runs Lighthouse and returns Chrome UX Report data. This page presents the results with Core Web Vitals first and the fixes ordered by time saved.
90–100 is good, 50–89 needs improvement and under 50 is poor. The score is a lab measurement; for rankings, passing Core Web Vitals with real users matters more than a perfect score.
The mobile test simulates a mid-range phone on a slow 4G connection, so every script and image costs more time. Google ranks the mobile version, so focus on the mobile result.
Lab tests vary with server response time, ads and third-party scripts. Differences of a few points are normal. Field data from real users is steadier but takes up to 28 days to reflect a fix.
The Chrome UX Report only includes pages and sites with enough Chrome visitors. New or low-traffic pages show origin (whole-site) data or only the lab test.
Yes, as part of the page experience signals, but it is a smaller factor than relevance and content quality. A faster page also lowers bounce rates and improves conversions, which is often the bigger win.