PageSpeed & Core Web Vitals

Test any URL for Core Web Vitals (LCP, CLS, TBT), performance score, SEO score, accessibility score, and best-practices score using Google's official PageSpeed Insights API. Mobile and desktop views supported. If your current host is slow, you'll see it here — and you'll see why moving to NVMe+LiteSpeed hosting fixes it.

3 / 3 free runs left today · Sign up free for 30/day

About the PageSpeed & Core Web Vitals

Page speed is a confirmed Google ranking factor and — more importantly — the single biggest driver of bounce rate on mobile. Every extra second of load time cuts conversion by roughly 7% (Google/SOASTA study). This tool calls Google's official PageSpeed Insights API, which runs a full Lighthouse audit against your URL and returns scores for Performance, SEO, Accessibility, and Best Practices, plus the full Core Web Vitals: LCP, FCP, CLS, TBT, Speed Index, and Time to Interactive.

How to read your results

Performance Score

Weighted composite of 6 metrics. 90+ is fast, 50–89 is average, below 50 is slow. Mobile scores are almost always 15–25 points lower than desktop — do not panic, just compare mobile to mobile and desktop to desktop.

LCP (Largest Contentful Paint)

The time until the biggest visible element (usually a hero image or headline) finishes rendering. Google wants this under 2.5 seconds. The #1 cause of slow LCP is a large unoptimized hero image — convert to WebP/AVIF and add width/height attributes to skip the fix most teams spend weeks chasing.

CLS (Cumulative Layout Shift)

How much the page jumps around as it loads. Below 0.1 is good. Caused by: images without dimensions, ads loading in, web fonts swapping (FOUT/FOIT), or JavaScript injecting DOM nodes after paint. Reserve space for dynamic content with aspect-ratio boxes.

TBT (Total Blocking Time)

How long the main thread was blocked by long JavaScript tasks. Below 200 ms is good. The culprit is almost always a heavy third-party script — tag managers, chat widgets, ad networks. Defer or async-load everything non-essential and watch TBT drop 40%+.

SEO / Accessibility / Best Practices

These three are usually in the 90s unless you are missing an alt attribute, have a failed HTTP resource, or ship insecure content. They are cheap wins — fix anything that drops below 95.

Frequently asked questions

Why is my mobile score so much lower than desktop?

Lighthouse simulates a slow 4G connection on a mid-range Android phone (Moto G4 class) throttled to 4x slowdown. Most real users are on faster hardware than this. The mobile score is intentionally worst-case so you catch problems that real users with bad connections will actually experience.

My CLS is 0.3 but the page looks fine to me — why?

You probably have a fast connection and a warm cache, so the elements that shift loaded before you noticed. On a cold 4G load, the shifts are visible and disorienting. The PSI lab test always runs cold and throttled, which is why it catches things you miss while developing locally.

Does passing Core Web Vitals guarantee a ranking boost?

Not a boost — it avoids a penalty. Google's page experience signal is a "tiebreaker" between two pages of similar content quality. Great speed on bad content still will not rank; slow speed on great content will lose to a competitor with comparable content at speed parity.

The tool shows different results each time I run it. Why?

Lighthouse lab tests have ~10% variance by design — every run simulates a fresh user with a clean cache and a throttled connection, and network jitter affects every metric. Run the test 3–5 times and take the median. Do not chase single-run score changes.

What about field data (real user metrics)?

If Google has enough Chrome User Experience (CrUX) data for your URL, the response includes a "loadingExperience" block with real user data from the last 28 days. Small or new sites will not have this — CrUX needs minimum traffic to aggregate.

Do I need to add a Google API key?

Only if you run the tool dozens of times per hour. Without a key, Google's rate limit is low but sufficient for occasional use. Admins can add a free PageSpeed Insights API key in Settings → Free Tools to lift the limit.

Should I optimize for Performance or for the other three scores?

All four, but in order of diminishing ROI: Performance first (biggest ranking + conversion impact), then SEO (quick wins — add missing meta tags), then Accessibility (legally required in many jurisdictions), then Best Practices. Accessibility also improves Performance indirectly because semantic HTML loads faster.

Why does my LCP say "image not found" but the image is clearly visible?

Lighthouse could not identify the LCP element — usually because it is a CSS background-image (not an ) or it is inside a lazy-loaded iframe. Switch background images to elements for above-the-fold content. Below-the-fold background images are fine.

Related tools, articles & authoritative sources

Hand-picked internal pages and external references from sources Google itself considers authoritative on this topic.