How fast is your page for real visitors?

This checker runs Google's PageSpeed Insights for you and lays out what matters. It shows two different measurements, and mixing them up is the most common mistake people make with speed reports.

1. 1Field data

   Real Chrome users over the last 28 days, from the Chrome UX Report. This is what Google uses for Core Web Vitals.

2. 2Core Web Vitals

   LCP (loading), INP (responsiveness) and CLS (visual stability), each judged at the 75th percentile of visits.

3. 3Lab data

   One Lighthouse run on an emulated mid-range phone or a desktop. Repeatable, so it's good for debugging.

4. 4Four scores

   Performance, accessibility, best practices and SEO, each out of 100.

5. 5Filmstrip

   Frames from the load, so you can see when content appears and what shifts.

6. 6Fixes

   Lighthouse's opportunities and diagnostics, ordered by estimated time saved.

Slow LCP is usually one of four things: a slow server response (check TTFB), render-blocking CSS and scripts, a large hero image, or a hero image the browser finds late because it's lazy-loaded or injected by JavaScript. Serve the hero image in a modern format at the size it's displayed, don't lazy-load it, and give it fetchpriority="high".

Poor INP means the main thread is busy when people tap or type. Long tasks from large JavaScript bundles, tag managers and chat widgets are the usual cause. Ship less JavaScript, split work into smaller chunks, and load third-party scripts after the page is interactive. Total Blocking Time in the lab test is the closest proxy.

High CLS comes from content that moves after it appears: images and embeds without width and height, ads and banners inserted above content, and web fonts that swap in at a different size. Reserve the space up front.

Redirect chains add a full round trip before the page even starts loading. Our redirect checker shows every hop.

AI assistants fetch pages live when they answer questions, and their fetchers work on tight time limits. A page that takes seconds to send its HTML, or that only shows its content after heavy JavaScript runs, risks being cut off or read empty.

Fast server response and content in the initial HTML help both people and these crawlers. Check what a crawler that doesn't run JavaScript sees with the JavaScript visibility checker.