Free Page Speed & Core Web Vitals Checker
Real-user Core Web Vitals from Google's Chrome data and a Lighthouse run, on mobile and desktop, with the fixes that save the most time. Free, no account.
Enter a page. Google loads it on a phone and a desktop.
Real-User Data vs Lab Data
Google ranks pages on what real Chrome users experienced over the last 28 days, at the 75th percentile. That field data is what decides the Core Web Vitals verdict above. The Lighthouse score is one simulated run: it is how you find fixes, but it swings between runs and Google doesn't rank on it, so it is shown and never scored.
INP needs real interactions, so there is no lab value for it. A page with too little traffic of its own shows the whole site's real-user data instead, and says so.
How to Improve Each Core Web Vital
- LCP: serve the hero image small and early. Preload it, never lazy-load it, and cut render-blocking CSS and JavaScript.
- INP: break up long JavaScript tasks, defer third-party scripts, and keep click handlers light.
- CLS: set width and height on images and embeds, and reserve space for ads and banners that load late.
How to Test and Improve Page Speed
- 1
Enter the page
Test the pages that earn traffic, such as the home page, top articles and product pages. Each page has its own speed.
- 2
Check the Core Web Vitals verdict
Google passes a page only when LCP, INP and CLS are all good for 75% of real visits. Start with whichever one fails.
- 3
Work through the top fixes
The fixes are ordered by how much time each one saves in the lab run. The LCP breakdown shows which phase of loading the main content is slowest.
- 4
Re-test after shipping
Lab results change straight away. Real-user data covers the last 28 days, so it catches up over the following weeks.
Speed is one part of the picture
The free audit includes these Core Web Vitals, plus titles, canonicals, schema, links and AI-search readiness.
Page Speed Checker FAQ
What are Core Web Vitals?
Google's three page experience metrics: Largest Contentful Paint (how fast the main content appears, good is 2.5 s or less), Interaction to Next Paint (how fast the page responds to taps, good is 200 ms or less) and Cumulative Layout Shift (how much the layout jumps, good is 0.1 or less).
What is the difference between field data and lab data?
Field data is what real Chrome users experienced over the last 28 days, and it is what Google uses for ranking. Lab data is one Lighthouse run on a simulated device: useful for finding fixes, but it swings by several points between runs. Only field data is scored here.
Why is there no real-user data for my page?
Google only publishes it for pages and sites with enough Chrome traffic. When a page has too little, the site-wide figure is shown instead, and when the whole site has too little, only the lab run is available.
Does page speed affect SEO?
Yes, as part of Google's page experience signals, mostly as a tie-breaker between pages of similar relevance. The bigger effect is on visitors: slow pages lose them before they read anything.
Is this the same data as PageSpeed Insights?
Yes. It calls Google's PageSpeed Insights and Chrome UX Report APIs, the same sources Google's own tool uses.
Is the page speed checker free?
Yes, with no signup.
Need to check more than one issue? Run our free SEO audit tool for 210 automated SEO and AI search checks, with evidence and priority fixes in a shareable report. No email or signup required.