Page speed in 2026 is about field data, not lab scores
Lab scores from Lighthouse are useful as a development checkpoint but Google ranks based on real-user field data from CrUX. A Lighthouse 95 means nothing if real users on slow networks see 4-second loads. Use both: lab scores for catching regressions before deploy, field data (via the Core Web Vitals Checker) for what Google actually grades.
This page speed test runs Lighthouse against any URL on simulated mobile and desktop, returning Performance, SEO, Accessibility, and Best Practices scores plus the underlying lab metrics: LCP, FCP, CLS, TBT, Speed Index, and TTI.
What each Lighthouse score means
Performance is the headline number, weighted across the lab metrics below. Above 90 is good, 50 to 89 needs work, under 50 is failing. SEO is a basic on-page check (meta tags, robots, link text, crawlability). Accessibility scores ARIA, contrast, and semantic markup. Best Practices flags HTTPS, deprecated APIs, console errors, and image aspect ratios.
SEO and Best Practices scores at 100 are the bar. Accessibility 100 is harder but achievable with a careful template. Performance is where most sites lose points and where work has the largest SEO payoff.
The lab metrics that drive Performance score
Largest Contentful Paint (LCP) measures when the largest visible element renders. Under 2.5 seconds is good. The largest element is usually the hero image or H1; optimize whichever it is. Common fixes: preload the hero image, reduce render-blocking JS and CSS, upgrade to HTTP/2 or HTTP/3.
First Contentful Paint (FCP) measures when any visible content appears. Under 1.8 seconds is good. Cumulative Layout Shift (CLS) measures visual stability; under 0.1 is good. CLS issues come from images without dimensions, ads, dynamically injected content, and web fonts loading late.
Total Blocking Time (TBT) measures main-thread blocking during load. Under 200ms is good. Heavy JavaScript is the usual culprit. Speed Index measures how visually populated the page is over time. Time to Interactive (TTI) is when the page becomes fully responsive. Both are derivatives of FCP and TBT.
Mobile vs desktop performance
Google primarily uses mobile-first indexing, so mobile scores matter more than desktop for ranking. Mobile is also where most sites fail badly: simulated mobile uses a 4x CPU slowdown and Slow 4G network throttle, which mimics real conditions for users on cheap Android phones.
The classic gap is desktop 95+ Performance, mobile 35 to 50. That gap usually comes from heavy JavaScript that desktop CPUs chew through but mobile cannot. Cutting bundle size, lazy-loading non-critical scripts, and removing unused libraries close the gap fastest.
Common reasons Performance scores stay low
Render-blocking resources are the #1 issue. CSS and JS in the head block first paint. Inline critical CSS, defer non-critical CSS via media queries, and use async or defer on script tags.
Unoptimized images. Serving 4000x3000 JPEGs to mobile phones wastes bandwidth and decode time. Use responsive srcset, modern formats (WebP, AVIF), and lazy-loading on below-fold images.
Third-party scripts. Analytics, chat widgets, A/B test scripts, tag managers, and tracking pixels often add 1 to 2 seconds of load time each. Audit aggressively. Defer or remove scripts that do not justify the performance cost.
Page speed and AI search
AI crawlers (GPTBot, ClaudeBot, PerplexityBot) have stricter timeouts than Googlebot. Slow pages get partial parsing or skipped entirely. Sites with consistent sub-2-second load times get cited more often in AI Overviews because the AI parsers can actually finish reading the page before timing out.
AI search will not directly show you a "performance ranking" signal, but the correlation between fast sites and frequent AI citations is increasingly clear in observation.