Free Google PageSpeed Insights Checker — Test Core Web Vitals Instantly
Website performance directly impacts search rankings, user engagement, and conversion rates. Google's Page Experience signals — anchored by Core Web Vitals metrics — have been a confirmed ranking factor since 2021, and their influence continues to grow through 2025 as Google refines how performance data shapes search results. This free PageSpeed checker analyzes any URL using Google's official PageSpeed Insights API v5, delivering both real-user field data and controlled lab diagnostics for mobile and desktop in a single test. No account, no sign-up, and no usage limits — enter a URL and receive a comprehensive performance breakdown in seconds.
How This PageSpeed Test Works: API Architecture
The tool queries Google's pagespeedonline/v5/runPagespeed endpoint with the PERFORMANCE category for both mobile and desktop strategies simultaneously. Two parallel fetch() requests are executed via Promise.all(), which means mobile and desktop analyses run concurrently rather than sequentially — cutting total wait time roughly in half compared to sequential testing. The API returns two distinct datasets for each strategy that the tool renders into separate sections.
The real-user experience section pulls from the Chrome User Experience Report (CrUX), which aggregates anonymized performance data from millions of actual Chrome users. The tool extracts four field metrics — FCP (First Contentful Paint), LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint) — each reported as a percentile value with a category classification (FAST / AVERAGE / SLOW). The CLS value is normalized from the API's integer format (e.g., 50 becomes 0.50) for accurate display.
The lab data section draws from Lighthouse's controlled simulation, which loads the page in a emulated environment with throttled CPU and network conditions. Five diagnostic audits are extracted: First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift, and Speed Index. Each audit receives a numeric score (0–1) mapped to the same three-tier color system — green for scores ≥ 0.9, amber for ≥ 0.5, and red below 0.5.
How to Test Your Website Speed — Step-by-Step
Step 1: Enter Your URL
Type or paste any website URL into the input field. The tool automatically prepends https:// if you omit the protocol, so both example.com and https://example.com work identically. Click "Analyze URL" to begin the test.
Step 2: Wait for the Dual Analysis
A loading spinner appears while both mobile and desktop tests run in parallel. Google's API typically returns results within 10–30 seconds depending on the complexity of the target page. The button changes to "Analyzing..." and is disabled during the request to prevent duplicate submissions.
Step 3: Review the Performance Score
The results open on the Mobile tab by default, displaying a circular score gauge rendered with CSS conic-gradient. The gauge fills proportionally — 90–100 in green (good), 50–89 in amber (average), 0–49 in red (poor). Click the Desktop tab to switch views; both datasets are cached locally so toggling between tabs is instantaneous.
Step 4: Analyze Core Web Vitals and Lab Data
Below the score gauge, two metric grids display field data and lab data side by side. Each metric card shows the measured value, the category classification (color-coded to match the score gauge), and a label indicating whether it represents real user data or a lab simulation. Focus on field metrics for real-world impact and lab metrics for diagnostic guidance on what to fix.
Understanding the Metrics That Matter in 2025
Google evaluates site performance using three Core Web Vitals. Largest Contentful Paint (LCP) measures how long the largest content element (hero image, heading, video) takes to render — the threshold is 2.5 seconds or less for a "good" rating. Interaction to Next Paint (INP), which replaced First Input Delay (FID) in March 2024, measures the full latency of every user interaction (click, tap, keypress) from the initial event through to the next visual update — 200 milliseconds or less is good. Cumulative Layout Shift (CLS) quantifies visual stability by measuring unexpected layout movements during page load — a score below 0.1 is considered good. All three metrics must pass their thresholds simultaneously for a page to qualify for the "good" Core Web Vitals assessment in Google Search Console.
PageSpeed Insights Checker vs. Other Testing Tools
The web performance testing landscape includes several distinct tools, each serving different purposes. Google's own PageSpeed Insights (which this tool queries) provides the unique advantage of combining real-user CrUX field data with Lighthouse lab diagnostics in a single response — no other free tool offers both datasets natively. GTmetrix uses Lighthouse for its lab data but supplements it with YSlow rules and its own waterfall analysis, and requires a free account for some features. WebPageTest by Catchpoint offers deep diagnostic capabilities (multi-step transactions, filmstrip view, connection throttling profiles) but presents a steeper learning curve. Pingdom and Dotcom-Monitor focus primarily on synthetic monitoring and uptime, not Core Web Vitals. This tool's advantage is simplicity and zero friction — enter a URL, get Google's own authoritative performance assessment immediately, with no registration wall or feature gating.
Common Performance Issues and How to Fix Them
The most frequent performance bottlenecks in 2025 are uncompressed or unoptimized hero images (converting to WebP or AVIF and serving responsive srcset sizes can reduce image payload by 40–70%), unminified JavaScript and CSS blocking the main thread (use build tools like Vite, esbuild, or webpack with Terser for JS and cssnano for CSS), excessive third-party scripts (analytics, chat widgets, ad loaders) that inflate Total Blocking Time, and render-blocking resources that delay First Contentful Paint. Server-side optimizations like HTTP/2 or HTTP/3 multiplexing, Brotli compression, and proper Cache-Control headers also yield significant improvements, particularly for repeat visitors.
Frequently Asked Questions
Is this the same data as Google's official PageSpeed Insights?
Yes. This tool queries the same pagespeedonline/v5/runPagespeed API endpoint that powers the official PageSpeed Insights website. The scores, metrics, and audit results are identical — this interface simply provides a streamlined, no-login way to access them.
What is the difference between field data and lab data?
Field data (Core Web Vitals) comes from the Chrome User Experience Report — real performance measurements from millions of actual Chrome users visiting your site over the past 28 days. Lab data comes from Lighthouse's controlled simulation, which loads your page in an emulated environment with throttled CPU and network. Field data reflects real-world user experience; lab data provides actionable diagnostics for improvement.
Why might field data be unavailable for my site?
Google requires a minimum threshold of real-user navigations before including CrUX data for a URL. New sites, low-traffic pages, and recently published content may not have accumulated enough data yet. In these cases, only lab data will appear in the results.
Why does my mobile score differ from my desktop score?
Google's mobile testing simulates a mid-tier Android device (Motorola Moto G Power) on a throttled 4G connection with 1.6x CPU slowdown and 150 ms RTT. Desktop testing uses a simulated desktop environment with no throttling. The same page often scores 20–40 points lower on mobile due to slower CPU, limited network bandwidth, and less aggressive browser caching on mobile connections.
How often should I test my website's speed?
For actively maintained sites, testing weekly or after every significant deployment (new features, theme updates, plugin installations) is recommended. Core Web Vitals field data updates on a rolling 28-day window, so improvements may take 2–4 weeks to fully reflect in Google's assessment.
Can I test pages behind authentication or on localhost?
Google's public API cannot access pages behind login walls, password protection, or private networks. For authenticated pages, use Lighthouse directly in Chrome DevTools (which runs in your browser context with active session cookies) or WebPageTest with an authenticated scripting option.
Related Tools You May Find Useful
Once you have identified performance bottlenecks with this tool, our Image Compressor can reduce image file sizes by 40–80% directly in your browser — one of the highest-impact optimizations for improving LCP scores. For optimizing web assets that affect Total Blocking Time, the TTF/OTF to WOFF2 Converter compresses font files by 30–50% using Brotli, accelerating font loading and reducing render-blocking resource weight.