PageSpeed Insights Checker

Analyze your website's performance using the same data and methodology as Google's PageSpeed Insights. Our checker evaluates Core Web Vitals including Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift, providing both lab data from simulated tests and field data from real Chrome users. Get a comprehensive performance report with prioritized optimization recommendations that directly improve your search rankings and user experience.

Key Features of Our PageSpeed Insights Checker

Core Web Vitals Assessment

Evaluates all three Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Each metric is scored against Google's official thresholds with clear good, needs improvement, or poor classifications.

Mobile and Desktop Analysis

Test performance from both mobile and desktop perspectives. Since Google uses mobile-first indexing, the mobile score directly impacts rankings. Desktop scores help identify opportunities for improving the experience of non-mobile visitors.

Performance Score Breakdown

Receive a 0-100 performance score with a detailed breakdown showing how each metric contributes to the total. Understand exactly which metrics are dragging your score down and how much each improvement would affect the overall result.

Prioritized Optimization Opportunities

Get a ranked list of specific optimization actions sorted by estimated impact. Each opportunity includes the potential time savings, affected metric, and implementation guidance, allowing you to focus development resources on the highest-value improvements first.

Field Data from Real Users

Access Chrome User Experience Report data showing how real visitors experience your page across the 75th percentile. Field data reflects actual conditions including diverse devices, networks, and geographic locations, making it the most accurate representation of user experience.

Detailed Diagnostic Audits

Review over 50 individual performance audits covering image optimization, JavaScript execution, CSS delivery, server response time, caching policies, render-blocking resources, DOM size, and third-party script impact.

Resource Loading Waterfall

Visualize the sequential and parallel loading of every resource on your page. The waterfall diagram reveals blocking dependencies, slow resources, and inefficient loading patterns that delay critical rendering milestones.

Treemap Visualization

See a visual representation of your page's JavaScript bundle sizes, helping you identify bloated scripts, unused code, and third-party resources that consume disproportionate bandwidth and processing time.

How to Use the PageSpeed Insights Checker

01

Step 1

Enter the full URL of the page you want to analyze into the input field. Use the exact URL that search engines index, including the protocol (https://) and any path segments, to ensure the results reflect your indexed page's actual performance.

02

Step 2

Select whether to analyze mobile performance, desktop performance, or both. Prioritize mobile analysis because Google's mobile-first indexing means the mobile score is what impacts your search rankings.

03

Step 3

Click analyze to start the test. The tool will run a Lighthouse simulation and query CrUX data if available, which may take 15 to 30 seconds depending on your page's complexity and loading time.

04

Step 4

Review the Core Web Vitals section first. Check whether LCP is under 2.5 seconds, INP is under 200 milliseconds, and CLS is under 0.1. These are the metrics Google uses directly in its ranking algorithm.

05

Step 5

Examine the performance score and its component breakdown. Note which metrics contribute most to a low score, as these represent the highest-priority optimization targets for improving both rankings and user experience.

06

Step 6

Work through the Opportunities section from top to bottom, implementing the suggestions with the largest estimated impact first. Common high-impact fixes include properly sizing images, eliminating render-blocking resources, and reducing JavaScript execution time.

07

Step 7

After implementing changes, re-run the analysis to measure improvement. Compare Core Web Vitals, performance scores, and specific metric values against your baseline to verify that optimizations are producing the expected results.

Ready to Analyze?

Try PageSpeed Insights Checker now — completely free, no registration required

Use Tool Now

What Is PageSpeed Insights?

PageSpeed Insights (PSI) is Google's official performance analysis tool that evaluates how well a web page performs on both mobile and desktop devices. Originally launched in 2010 as a simple speed test, PSI has evolved into a comprehensive performance diagnostic platform that combines real-world Chrome User Experience Report (CrUX) data with Lighthouse lab testing to provide the most authoritative performance assessment available.

Our PageSpeed Insights Checker leverages the same analytical framework to deliver performance data that directly reflects how Google evaluates your pages for ranking purposes. This is not a third-party approximation; it uses the same metrics, thresholds, and scoring methodology that Google applies when assessing your site's page experience signals.

The tool provides two distinct types of performance data:

Field Data (Real User Metrics): Collected from actual Chrome users who visit your page over a rolling 28-day period. Field data represents the real-world experience of your visitors across diverse devices, network conditions, and geographic locations. This is the data Google uses for Core Web Vitals assessment in search rankings. Field data is available only for pages with sufficient traffic to generate a statistically significant sample.

Lab Data (Simulated Testing): Generated by running your page through Lighthouse, Google's open-source performance auditing tool, in a controlled, simulated environment. Lab data uses a fixed device and network profile, typically a mid-tier mobile device on a throttled 4G connection, to ensure consistent, reproducible results. Lab data is available for any URL regardless of traffic volume and provides detailed diagnostic information that field data cannot offer.

The performance score ranges from 0 to 100 and is calculated as a weighted average of six lab metrics: First Contentful Paint (10%), Speed Index (10%), Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), and any applicable bonus from unused audit scores. Scores of 90 and above are classified as good (green), 50 to 89 as needs improvement (orange), and below 50 as poor (red).

Understanding these scores and the underlying metrics is essential because Google has made page experience, and Core Web Vitals specifically, an official ranking signal. Pages that meet Core Web Vitals thresholds have a measurable advantage in search results, and this advantage compounds across large sites where marginal improvements apply to thousands of indexed pages.

Why PageSpeed Insights Matters for SEO Rankings

PageSpeed Insights is not just a performance benchmarking tool; it is the definitive source for understanding how Google perceives your page's user experience. The connection between PSI metrics and search rankings is direct, documented, and increasingly significant.

Core Web Vitals as a Confirmed Ranking Signal

In June 2021, Google officially incorporated Core Web Vitals into its ranking algorithm through the Page Experience Update. The three Core Web Vitals metrics, LCP, FID (now replaced by INP), and CLS, are extracted from CrUX data, the same field data displayed in PageSpeed Insights. Google has confirmed that pages meeting all three Core Web Vitals thresholds receive a ranking boost, and pages failing these thresholds may see reduced visibility.

The Shift from FID to INP

In March 2024, Google officially replaced First Input Delay (FID) with Interaction to Next Paint (INP) as the responsiveness Core Web Vital. INP is a more comprehensive metric that measures the latency of all interactions throughout the entire page lifecycle, not just the first one. This change means many pages that previously passed Core Web Vitals with a good FID score may now fail under the stricter INP measurement. Our PageSpeed Insights Checker evaluates INP to give you current, accurate responsiveness data.

How Performance Scores Translate to Rankings

Google uses Core Web Vitals as a tiebreaker and differentiator among pages with similar content quality and authority. In highly competitive search verticals where dozens of pages offer comparable content, the page experience signal can determine which pages earn positions on page one versus page two. A study by Searchmetrics found that pages in the top 10 Google results have measurably better Core Web Vitals scores than those on page two, with LCP scores averaging 1.8 seconds for top-ranking pages compared to 3.2 seconds for lower-ranking ones.

Mobile-First Indexing and Performance

Google indexes and ranks all websites based on their mobile version. Mobile devices typically have less processing power and slower network connections, amplifying performance issues. A page that scores 95 on desktop may score 55 on mobile due to unoptimized images, heavy JavaScript, or render-blocking resources. Since rankings are determined by the mobile experience, the mobile PageSpeed Insights score is the one that matters most for SEO.

User Behavior Impact

Performance directly affects user behavior metrics that correlate with rankings. Google research shows that when page load time increases from 1 to 3 seconds, bounce probability increases by 32 percent. At 5 seconds, it increases by 90 percent. Amazon found that every 100 milliseconds of latency cost them 1 percent in sales. These behavioral impacts create a feedback loop: slow pages generate worse engagement signals, which can further suppress rankings.

Search Console Integration

Google Search Console now includes a dedicated Core Web Vitals report that groups your URLs by their CrUX performance status. Pages classified as poor or needs improvement appear as potential ranking issues. The data in this report comes from the same CrUX database that feeds PageSpeed Insights, making PSI scores a reliable predictor of how your pages are classified in Search Console.

Core Web Vitals Explained: LCP, INP, and CLS

Core Web Vitals are the three specific metrics that Google has designated as official ranking signals within its page experience framework. Each metric addresses a distinct aspect of user experience: loading, interactivity, and visual stability.

Largest Contentful Paint (LCP)

LCP measures the time from when the page starts loading to when the largest content element is rendered within the viewport. The largest element is typically a hero image, featured video thumbnail, or large heading block. LCP reflects the moment users perceive the page as loaded with meaningful content.

Google's thresholds: Good is 2.5 seconds or less. Needs improvement is between 2.5 and 4.0 seconds. Poor is above 4.0 seconds. The most common causes of slow LCP include unoptimized images that are the LCP element, slow server response time delaying the initial HTML delivery, render-blocking CSS and JavaScript that prevent the browser from painting content, and client-side rendering where the LCP element depends on JavaScript execution.

To improve LCP: optimize and compress the LCP image element, preload critical resources with <link rel="preload">, reduce server response time through caching and CDN usage, eliminate render-blocking resources, and ensure the LCP element is available in the initial HTML without requiring JavaScript.

Interaction to Next Paint (INP)

INP replaced FID as the responsiveness metric in March 2024. While FID only measured the delay of the first interaction, INP measures the latency of all interactions throughout the page's lifecycle and reports the worst interaction (at the 98th percentile). This makes INP a much more comprehensive measure of a page's responsiveness.

Google's thresholds: Good is 200 milliseconds or less. Needs improvement is between 200 and 500 milliseconds. Poor is above 500 milliseconds. High INP is typically caused by long-running JavaScript tasks that block the main thread, preventing the browser from responding to user input. Complex event handlers, heavy third-party scripts, and inefficient DOM manipulation are common culprits.

To improve INP: break long JavaScript tasks into smaller chunks using requestIdleCallback or setTimeout, defer non-critical JavaScript, remove or delay heavy third-party scripts, optimize event handlers to minimize processing time, and use web workers for computationally intensive operations.

Cumulative Layout Shift (CLS)

CLS quantifies how much visible content shifts unexpectedly during the page's lifetime. Layout shifts occur when elements move from their initial position without user interaction, typically caused by images loading without dimension attributes, dynamically injected content, and late-loading web fonts. CLS measures both the distance and size of the shifted elements.

Google's thresholds: Good is 0.1 or less. Needs improvement is between 0.1 and 0.25. Poor is above 0.25. To improve CLS: always specify width and height attributes on images and video elements, reserve space for ad slots and dynamic content using CSS, preload web fonts and use font-display: swap, avoid inserting content above existing visible elements, and use CSS contain property to limit layout recalculation scope.

Common Performance Issues and How to Fix Them

PageSpeed Insights audits consistently flag the same categories of performance issues across different websites. Here are the most impactful problems and their proven solutions.

Unoptimized Images

Images are the single largest contributor to page weight on most websites, often accounting for 50 to 80 percent of total page bytes. Common issues include serving images at their original resolution when the display size is much smaller, using legacy formats like JPEG and PNG instead of modern WebP or AVIF, and not implementing lazy loading for below-the-fold images.

Solutions: Convert images to WebP format, which provides 25 to 35 percent better compression than JPEG at equivalent quality. Use responsive images with the srcset attribute to serve appropriately sized versions. Implement native lazy loading with loading="lazy" on images below the fold. For the LCP image, do the opposite: preload it with <link rel="preload"> and never lazy-load it.

Render-Blocking JavaScript and CSS

External CSS and JavaScript files loaded in the document head block the browser from rendering any content until they are fully downloaded and parsed. This directly impacts First Contentful Paint and LCP.

Solutions: Inline critical CSS needed for above-the-fold rendering directly in the HTML. Load non-critical CSS asynchronously. Add the defer attribute to JavaScript files that are not needed for initial rendering. Use async for scripts that can load independently. Identify and eliminate unused CSS and JavaScript that are loaded but never executed on the page.

Excessive JavaScript Execution

Heavy JavaScript bundles take time to download, parse, compile, and execute. Long-running scripts block the main thread, degrading INP scores and delaying interactivity. Third-party scripts from analytics, advertising, and marketing tools are frequent offenders.

Solutions: Audit all JavaScript with the Coverage tool in Chrome DevTools to identify unused code. Implement code splitting to load only the JavaScript needed for the current page. Defer third-party scripts until after initial load. Replace heavy JavaScript libraries with lighter alternatives or native browser APIs. Use web workers for computationally intensive tasks.

Slow Server Response Time

Time to First Byte (TTFB) above 800 milliseconds indicates server-side performance issues that delay the entire loading cascade. Causes include slow database queries, lack of server-side caching, inadequate hosting resources, and absence of a CDN.

Solutions: Implement server-side page caching with tools like Varnish, Redis, or platform-specific caching plugins. Optimize database queries and add appropriate indexes. Upgrade hosting if current resources are consistently maxed out. Deploy a CDN to reduce geographic latency. Enable HTTP/2 or HTTP/3 for multiplexed resource delivery.

Font Loading Issues

Web fonts that block rendering create a Flash of Invisible Text (FOIT) that increases LCP and FCP times. Late-loading fonts can also cause layout shifts as text reflows from the fallback font to the web font, increasing CLS.

Solutions: Preload critical font files with <link rel="preload" as="font">. Use font-display: swap to show text immediately in a fallback font while the web font loads. Subset fonts to include only the characters your site actually uses. Self-host fonts instead of loading from external services to reduce DNS lookup and connection overhead.

Frequently Asked Questions

Everything you need to know about PageSpeed Insights Checker

A performance score of 90 or above is classified as good by Google. Scores between 50 and 89 need improvement, and scores below 50 are poor. However, for SEO purposes, the individual Core Web Vitals metrics matter more than the overall score. A page could score 85 overall but still fail Core Web Vitals if LCP exceeds 2.5 seconds. Focus on getting all three Core Web Vitals into the green zone first, then optimize for a higher overall score.

PageSpeed Insights uses Lighthouse as its lab testing engine but adds real-world Chrome User Experience Report field data that Lighthouse alone does not provide. Lighthouse runs in a simulated environment with fixed conditions, while CrUX data reflects actual visitor experiences across real devices and networks. PageSpeed Insights combines both to give a complete picture. Additionally, PSI runs Lighthouse on Google's servers, eliminating local hardware variables that affect Lighthouse scores when run locally.

Mobile scores are generated using a simulated mid-tier mobile device on a throttled 4G connection, which has less processing power and bandwidth than the unthrottled desktop simulation. This amplifies the impact of heavy JavaScript, large images, and slow server responses. Additionally, mobile pages must render at smaller viewport widths, which can trigger different layout behaviors. Since Google uses mobile-first indexing, the mobile score is the one that impacts your rankings.

Interaction to Next Paint (INP) measures the latency of all user interactions throughout the page's lifecycle and reports the worst one at the 98th percentile. It replaced First Input Delay (FID) in March 2024 because FID only measured the first interaction, which often occurred before heavy JavaScript loaded. Many pages had good FID but poor subsequent interactivity. INP provides a more complete and honest assessment of a page's responsiveness throughout the entire user session.

Check after every significant code deployment, content change, plugin update, or hosting modification. Establish a weekly baseline test for your most important pages to detect gradual performance degradation caused by accumulating third-party scripts, growing content, or infrastructure changes. Before launching any new page or campaign, run a performance check to verify it meets Core Web Vitals thresholds. Set up automated monitoring if your site changes frequently.

Yes, many high-impact improvements can be made without coding. Image optimization, which is often the single biggest factor, can be done with image compression tools or CMS plugins. Caching plugins for WordPress and other platforms can dramatically improve performance. Removing unused plugins and third-party scripts reduces JavaScript bloat. Choosing a faster hosting provider or enabling a CDN improves server response time. These non-technical changes often deliver the majority of available performance gains.

No. The PageSpeed score is one of many ranking signals, and content relevance, backlink authority, and user intent matching remain far more important. A score of 100 will not help a page with thin content outrank authoritative competitors. However, among pages with comparable content quality and authority, better Core Web Vitals scores provide a measurable ranking advantage. Focus on meeting the Core Web Vitals thresholds rather than chasing a perfect score, as the ranking benefit comes from passing the thresholds rather than from the absolute score number.

Lab scores can fluctuate by 5 to 10 points between tests due to variations in server response time, network conditions during the test, and resource loading timing. This is normal and expected. Focus on the trend over multiple tests rather than any single result. Field data from CrUX is more stable because it represents a 28-day rolling average across many visitors. If your score varies dramatically between tests, the instability itself may indicate performance issues like inconsistent server responses or race conditions in resource loading.

Related SEO Tools

Explore other tools to improve your SEO strategy

Popular

Page Speed Checker

Test your page loading time and performance metrics

Page Size Checker

Check the total file size and weight of any webpage

Responsive Design Checker

Test how your website looks on different screen sizes and devices