Website Page Speed Test

Run a full Google PageSpeed Insights analysis on any URL — mobile and desktop scores, Core Web Vitals, and specific fixes.

Analyzing website performance... This may take 10-20 seconds.

Mobile
Desktop
0

Mobile Performance

Google PageSpeed Insights Score

Core Web Vitals
Opportunities
Performance Best Practices
Resource Summary
Passed Audits
0

Desktop Performance

Google PageSpeed Insights Score

Core Web Vitals
Opportunities
Performance Best Practices
Resource Summary
Passed Audits

Related Tools

HTML Previewer
Try tool →
Domain Age Checker
Try tool →
Google SERP Snippet Preview
Try tool →
Robots.txt Generator
Try tool →
Website Hit Counter
Try tool →
Color Picker
Try tool →
CSS / Js Minifier
Try tool →
Mobile Friendly Test
Try tool →
Favicon Generator
Try tool →

A slow website costs you in two ways — users leave before the page loads, and Google ranks you lower than faster competitors. This tool runs a full PageSpeed Insights analysis on any URL and shows you mobile and desktop scores, Core Web Vitals measurements, and a list of specific issues to fix.

Enter your URL and get results in 10–20 seconds.

How to Use This Page Speed Test

  1. Enter your URL — paste any webpage address and click Check Speed
  2. Wait 10–20 seconds — the tool calls Google’s PageSpeed Insights API to fetch real performance data
  3. Review mobile and desktop scores — both appear side by side so you can compare
  4. Check Core Web Vitals — LCP, FID/INP, and CLS scores show whether your page passes Google’s thresholds
  5. Read the opportunities — each flagged issue includes an estimated time saving and a description of what to fix
  6. Download PDF report — save the full analysis for sharing with a developer or tracking over time

What Is a Good PageSpeed Score?

PageSpeed Insights scores pages from 0 to 100 across four categories: Performance, Accessibility, Best Practices, and SEO. The Performance score is what most people refer to when they say “page speed score.”

Score ranges:

  • 90–100 — Good. Your page is fast and well-optimized.
  • 50–89 — Needs Improvement. There are performance issues worth addressing.
  • 0–49 — Poor. Significant problems that are likely affecting user experience and rankings.

Important context: A perfect 100 is neither realistic nor necessary for most sites. A score of 75–85 on mobile is strong for content-heavy sites. E-commerce sites with lots of images typically score lower. The goal is consistent improvement, not perfection.

Mobile scores are almost always lower than desktop scores — mobile devices have slower CPUs and users are often on cellular connections. Focus on your mobile score first since that’s what Google uses for ranking.

Core Web Vitals — What They Are and Why They Matter

Core Web Vitals are a set of specific metrics Google uses to measure real-world user experience. They became official Google ranking signals in 2021 and are measured for both mobile and desktop.

LCP — Largest Contentful Paint Measures how long it takes for the largest visible element on the page to load — usually a hero image, large heading, or featured photo. Google’s threshold: under 2.5 seconds is Good, 2.5–4 seconds Needs Improvement, over 4 seconds is Poor.

Common LCP fixes: compress and properly size images, use WebP format, add loading="eager" to hero images (opposite of lazy loading for above-fold images), and reduce server response time.

FID / INP — First Input Delay / Interaction to Next Paint FID measured how long until a page responded to the first user interaction (a click or tap). Google replaced FID with INP (Interaction to Next Paint) in March 2024. INP measures the responsiveness of all interactions throughout the page visit, not just the first one. Under 200ms is Good.

Common INP/FID fixes: reduce JavaScript execution time, defer non-critical JS, avoid long tasks that block the main thread.

CLS — Cumulative Layout Shift Measures visual stability — how much page elements move around as the page loads. When images, ads, or fonts load and push content down, CLS increases. Under 0.1 is Good.

Common CLS fixes: always set explicit width and height on images and video elements, reserve space for ads, avoid inserting content above existing content after load.

Why Page Speed Directly Affects SEO Rankings

Page speed has been a ranking factor for desktop searches since 2010. Google extended it to mobile searches in 2018. Core Web Vitals became a ranking signal in 2021 through Google’s Page Experience update.

What this means in practice: two pages with similar content and backlinks will have different rankings if one is significantly faster. Fast pages don’t automatically rank first — content relevance and authority still matter more — but slow pages with poor Core Web Vitals are at a measurable disadvantage.

Beyond rankings, speed affects user behavior directly. Research consistently shows that every additional second of load time increases bounce rates. A page that loads in 1 second has a much lower bounce rate than the same page loading in 3 seconds. Lower bounce rates and longer session times send positive engagement signals to Google.

Most Common Page Speed Issues and How to Fix Them

Unoptimized images — The single most common cause of slow pages. Large images that haven’t been compressed or resized are loaded at full resolution even when displayed at small sizes. Fix: compress images before uploading, use WebP format, and set correct dimensions.

Render-blocking JavaScript and CSS — Scripts and stylesheets that load in the <head> block the browser from rendering anything until they finish downloading. Fix: defer non-critical JavaScript with the defer attribute, and inline critical CSS.

No browser caching — Without caching headers, browsers re-download the same assets on every visit. Fix: configure your server to send Cache-Control headers for static assets.

Slow server response time (TTFB) — Time to First Byte measures how long the server takes to respond. Over 600ms is a problem. Fix: upgrade hosting, use a CDN, or enable server-side caching.

Too many HTTP requests — Every image, script, font, and stylesheet is a separate request. Fix: combine files where possible, use CSS sprites for icons, and remove unused plugins or scripts.

No CDN — Serving all assets from a single server location means users far from that location experience higher latency. Fix: use a content delivery network to serve static assets from servers close to each user.

Page Speed Test vs Google PageSpeed Insights

This tool uses Google’s PageSpeed Insights API directly, so the scores and data you see here are the same as what you’d get from running the test on PageSpeed Insights itself. The difference is convenience — you can run the test, read the results, and access related tools all in one place without switching tabs.

For ongoing monitoring and tracking trends over time, Google Search Console’s Core Web Vitals report shows field data (real user measurements) rather than lab data (simulated measurements). Lab data shows what’s possible; field data shows what real users actually experience.

Frequently Asked Questions (FAQ)

For SEO purposes, aim for a Performance score of 90 or above on desktop and 70 or above on mobile. Mobile scores are naturally lower because mobile devices have less processing power and users are often on slower connections. More important than the overall score are the Core Web Vitals — LCP under 2.5 seconds, INP under 200ms, and CLS under 0.1. These are Google’s actual ranking signals. A score of 75 on mobile with passing Core Web Vitals is more valuable for SEO than a score of 90 with failing vitals.

Mobile scores are almost always lower than desktop scores. PageSpeed Insights simulates a mid-tier mobile device on a 4G connection when testing mobile performance — conditions significantly slower than a desktop computer on broadband. Heavy images, render-blocking scripts, and large JavaScript bundles hit mobile performance much harder. Focus on compressing images, deferring non-critical JavaScript, and ensuring your critical content loads quickly. The mobile score is what matters most for Google rankings since Google uses mobile-first indexing.

Core Web Vitals are three metrics Google uses as ranking signals: LCP (Largest Contentful Paint — how fast the main content loads), INP (Interaction to Next Paint — how responsive the page is to interactions), and CLS (Cumulative Layout Shift — how stable the layout is while loading). This tool shows all three for both mobile and desktop. To pass, you need LCP under 2.5s, INP under 200ms, and CLS under 0.1. Google Search Console’s Core Web Vitals report shows field data from real users, which is the most accurate measure.

For WordPress sites, the most impactful fixes are: install a caching plugin (WP Rocket, W3 Total Cache, or LiteSpeed Cache), compress and convert images to WebP (Smush, ShortPixel, or Imagify), use a CDN, and switch to a fast hosting provider. Deactivate unused plugins — each active plugin adds code that loads on every page. Use a lightweight theme rather than a heavy page builder if speed is a priority. After making changes, run this test again to measure the improvement.

LCP (Largest Contentful Paint) measures how long it takes for the largest visible element — usually a hero image or large heading — to appear on screen. Over 2.5 seconds is poor. To fix slow LCP: preload your hero image with <link rel="preload">, compress and serve it in WebP format, set loading="eager" on above-fold images (not lazy loading), reduce server response time, and eliminate render-blocking resources that delay the page from starting to render.

CLS (Cumulative Layout Shift) happens when elements move after the page has started loading — typically because images, ads, or web fonts load and push content down. The most common fix is to always specify explicit width and height attributes on all images and video elements so the browser can reserve space before they load. For ads, use a fixed container with a minimum height. For web fonts, use font-display: optional or font-display: swap in your CSS to prevent invisible text and layout shifts during font loading.

Run a test whenever you make significant changes to your site — after installing a new plugin, adding a new page template, changing your theme, or publishing a page with heavy images. Also run it periodically (monthly) as a routine health check, since third-party scripts, new ad placements, and plugin updates can quietly degrade performance over time. If you notice a ranking drop, checking Core Web Vitals is one of the first diagnostic steps.