What is a page speed checker?
A page speed checker is a tool that measures how quickly a web page loads and how stable and responsive it feels while loading. It runs your page through a performance test and reports a score — typically 0–100 — plus the specific signals behind it, so you can see whether your site feels fast to real visitors and, if not, what's slowing it down.
Speed matters for two concrete reasons: visitors abandon slow pages, and page experience is part of how Google evaluates sites. A faster page tends to convert better and competes more easily in search. This checker runs its own five-signal analysis in seconds — no API key, no sign-up — and ranks what to fix first.
How to check your page speed (step-by-step)
- Enter your URL. Paste the full page address (not just the domain) into the field above — speed varies page by page.
- Pick a device. Test Mobile and Desktop; mobile is usually slower and is what Google weighs most heavily.
- Run the test. You'll get a performance score, a five-signal breakdown, a resource summary, and a ranked list of fix-first opportunities in under five seconds.
- Work the fix list top-down. Start with the HIGH-impact items — fixing one large render-blocking script often moves the score more than a dozen small tweaks.
How to read your results
The five signals we score
Rather than a single opaque number, this checker breaks performance into five signals you can act on, each scored 0–100:
- Speed — server response time plus how long the HTML takes to download.
- Page weight — the size of the HTML payload; lean pages render faster on mobile.
- Render-blocking — scripts and stylesheets in the
<head>that delay first paint. - Image hygiene — lazy-loading, explicit width/height and alt text, which drive layout stability.
- Transport quality — HTTPS, HTTP/2 or HTTP/3, compression and caching headers.
Core Web Vitals: LCP, INP and CLS
Core Web Vitals are the three metrics Google uses to summarize real-world page experience. Our five-signal check is a fast diagnostic of the things that drive these vitals; for the official field measurements, run your URL through Google PageSpeed Insights (linked from the results above). Here's what each one means:
LCP
Largest Contentful Paint — time until the biggest visible element loads. Good: ≤ 2.5s.
INP
Interaction to Next Paint — how fast the page reacts to a tap or click. (Replaced FID in 2024.) Good: ≤ 200ms.
CLS
Cumulative Layout Shift — how much the layout jumps as it loads. Good: ≤ 0.1.
Hit the "good" threshold on all three and your page passes Core Web Vitals.
Lab data vs field data (CrUX)
There are two kinds of speed numbers. Lab data is a single controlled test in a simulated environment — great for debugging and reproducible (this is what our checker and Lighthouse produce). Field data comes from Google's Chrome User Experience Report (CrUX): the actual experience of real Chrome users over the prior 28 days. Field data is the truth about what your visitors feel; lab data is the diagnostic you use to fix it. New or low-traffic pages may not have enough field data yet — in that case, lean on the lab results.
Why your mobile and desktop scores differ
Mobile scores are almost always lower, because the test simulates a mid-tier phone on a slower connection. Since most traffic is mobile and Google evaluates the mobile experience, treat the mobile score as the one that matters most — a great desktop score won't save a slow mobile page.
What is a good page speed score?
For the 0–100 performance score: 90–100 is good (green), 50–89 needs improvement (orange), and 0–49 is poor (red). But the score is a means, not the goal — what you're really chasing is passing Core Web Vitals on real-user (field) data, because that's the part tied to page experience.
A practical target: aim for a mobile score of 90+ and green Core Web Vitals in the field. If competitors ranking above you are slower, speed is a lever you can pull; if they're already fast, treat parity as the baseline, not a differentiator.
How to improve your page speed
Quick wins: images, caching, fonts
Most speed problems start here, and these are the cheapest fixes:
- Compress and correctly size images; serve modern formats (WebP/AVIF) and lazy-load below-the-fold images.
- Enable browser caching and use a CDN so repeat and distant visitors load faster.
- Preload your main font and avoid invisible-text flashes; trim unused font weights.
Bigger fixes: JavaScript, server response, third-party scripts
When the quick wins aren't enough:
- Reduce and defer JavaScript; remove unused code and split large bundles so the page becomes interactive sooner (usually the biggest INP lever).
- Improve server response time (aim under ~600ms) with better hosting, caching, or a faster backend.
- Audit third-party scripts — analytics, chat widgets, ad tags. Each one should justify its cost; they're a leading cause of slow, janky pages.
Does page speed affect SEO rankings?
Yes, but with nuance. Page experience — including Core Web Vitals — is a confirmed Google ranking signal, but it's a tiebreaker, not a primary one. Google has been explicit that relevant, high-quality content beats a faster competitor with weaker content. Speed rarely vaults a page to the top on its own; what it does is remove a disadvantage and improve the user metrics — bounce, conversions — that matter regardless of rankings.
The honest framing: fix speed because slow pages lose visitors and can hold you back among otherwise-equal competitors — not because a 100 score is a magic ranking button.
Does page speed affect AI search visibility?
Indirectly. AI Overviews, ChatGPT and other answer engines decide what to cite based on relevance and trust, not your performance score. But speed and technical health affect whether your pages get crawled and rendered efficiently in the first place — a page that's slow, JavaScript-heavy or unstable is harder for any automated system, search crawler or AI, to access and parse cleanly.
So fast, technically sound pages don't earn AI citations by being fast, but slow, broken ones can quietly exclude themselves. Speed is table stakes for discoverability; content and authority earn the citation — which is what generative engine optimization is about.
How to use this checker
Benchmark against your competitors
Test your top three competitors' key pages on mobile. Their scores tell you what's realistically achievable in your space — and whether speed is a gap you can exploit or a baseline you need to match.
Track your speed over time
Speed degrades quietly as you add scripts, images and features. Re-test important pages after every significant change, and check periodically, so a new plugin or tag doesn't silently tank your Core Web Vitals.
Page speed checker vs PageSpeed Insights, GTmetrix and Pingdom
Those tools run distributed Lighthouse tests and surface CrUX field data — authoritative, but often a wall of developer-oriented findings. This checker is built for a different moment: a fast, no-key pre-flight that scores five real signals and hands you a ranked, plain-English fix list in seconds, with the underlying resources laid out so you can verify everything yourself. Use PageSpeed Insights for the full Lighthouse lab run and real-user Core Web Vitals; use this one to triage quickly and decide where to spend your time first.
Frequently asked questions
Enter your page URL in the tool, choose mobile or desktop, and run the test. It's free with no sign-up or API key, and returns a 0-100 performance score with a five-signal breakdown and a ranked fix-first list in under five seconds.
On the 0-100 performance scale, 90 or above is good, 50-89 needs improvement, and under 50 is poor. For Google’s Core Web Vitals, aim for LCP 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or less on real-user data.
Core Web Vitals are Google's three page-experience metrics: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). Together they summarize how fast and stable a page feels to real users.
Mobile tests simulate a mid-range phone on a slower connection, so scores are typically lower than desktop. Because most traffic is mobile and Google prioritizes the mobile experience, the mobile score is the one to focus on.
Yes, as part of Google's page-experience signals, but it's a tiebreaker rather than a primary factor. Relevant, high-quality content outweighs speed, but a fast page improves user experience and removes a disadvantage against equally relevant competitors.