Site Loading Speed Test
The Page Speed Test measures every load-time metric that matters for SEO and conversion: total load time, Time to First Byte, First Contentful Paint, Largest Contentful Paint, Time to Interactive and total page weight.
- Results in seconds
- Pass / fail + fix guidance
- No account required
The Page Speed Test measures every load-time metric that matters for SEO and conversion: total load time, Time to First Byte, First Contentful Paint, Largest Contentful Paint, Time to Interactive and total page weight. We render the page in headless Chrome from a clean cache, capture the full waterfall, and produce a prioritised list of fixes — render-blocking scripts, oversized images, missing compression, slow third parties — sorted by the seconds each fix will recover.
What This Tool Checks
- Total load time and Time to First Byte (TTFB)
- Core Web Vitals (LCP, INP, CLS)
- Page weight and request count
- Render-blocking resources (CSS / JS)
- Image sizing and modern format usage
- Third-party script impact
- Server compression and HTTP/2
Why It Matters for SEO
Page speed is a confirmed Google ranking factor on both mobile and desktop, and the impact on conversion is even bigger than the impact on rankings. Every additional second of load time costs roughly 7-20% in conversion, and Google's page-experience ranking signal directly weights Core Web Vitals scores. Faster pages rank higher, convert better and reduce server costs simultaneously — making page speed one of the few SEO investments with measurable ROI in days rather than months.
How to Fix It
Move all non-critical JS to async / defer; inline critical CSS and lazy-load the rest. Compress and serve hero images in WebP / AVIF with explicit width and height. Audit third-party scripts and remove anything not generating clear value. Enable Brotli at the origin and put a CDN in front of the site. Re-test until LCP < 2.5s, INP < 200ms, CLS < 0.1.
How It Works
Headless Chrome navigates the URL with a clean cache, captures the full network waterfall and rendering metrics via the Performance Timeline API, then maps each blocking resource to its concrete speed impact. The resulting report ranks fixes by seconds-saved so you tackle the highest-leverage changes first.
Common Mistakes to Avoid
- Render-blocking JavaScript in the <head>
- Unoptimised hero images delaying Largest Contentful Paint
- Heavy third-party scripts (chat widgets, analytics, A/B test SDKs)
- Missing GZIP / Brotli compression at origin
- No CDN — long TTFB for users far from origin
Quick Checklist
- LCP under 2.5 seconds
- INP under 200 ms
- CLS under 0.1
- TTFB under 600 ms
- Page weight under 1.5 MB on first load
Put your whole site on autopilot — SEO and AI search
PositionMySite monitors every signal on this page across your entire website 24/7 — plus keyword rankings, competitor moves and AI-search readiness (llms.txt, schema, ChatGPT & Gemini visibility). When something breaks, you know before Google does.
Every feature unlocked · No commitment · Cancel anytimeFrequently Asked Questions
Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 ms, and Cumulative Layout Shift under 0.1. Above those thresholds you start losing rankings and conversions measurably.
Yes. Google's page-experience signal incorporates Core Web Vitals as a direct ranking input on mobile and desktop. Sites in the "Good" CWV bucket consistently outrank similar-content sites in "Poor".
Most commonly: oversized hero images, render-blocking JavaScript, and heavy third-party scripts. Fixing those three categories typically cuts load times by 30-60%.
Almost always yes. CDNs cache static assets at edge locations close to your users, cutting Time to First Byte from hundreds of milliseconds to tens. Most also enable Brotli compression and HTTP/3 transparently.
We provide live diagnostic data plus prioritised fixes. Google's PageSpeed Insights gives lab data and field data from real users (CrUX). Use both — this tool for daily debugging, PSI for the official Core Web Vitals score.