Google Uses Page Speed as a Ranking Signal. How’s Yours?
Core Web Vitals aren’t just performance metrics, they’re ranking factors. Google confirmed it. LCP over 2.5 seconds? Your page ranks lower. CLS over 0.1? Your page ranks lower. This tool runs your URL through the Google PageSpeed Insights API and gives you the exact numbers.
Enter a URL, wait 10-30 seconds for the Lighthouse audit, and get a 0-100 performance score with individual breakdowns for LCP, CLS, FCP, Total Blocking Time, and Speed Index. Everything color-coded: green is good, yellow needs work, red is hurting you.
The Numbers You Need to Hit
LCP (Largest Contentful Paint): under 2.5 seconds. This measures how long until the biggest visible element loads. Usually it’s a hero image or a heading block. If your LCP is 4.2 seconds, you’ve got an image optimization problem.
CLS (Cumulative Layout Shift): under 0.1. This measures how much stuff moves around while the page loads. Images without width/height attributes, dynamically injected banners, web fonts swapping in, all these cause layout shifts that frustrate users.
FCP (First Contentful Paint): under 1.8 seconds. How quickly does anything appear on screen? A blank white page for 3 seconds makes people hit the back button.
What Score Means What
90+ is good. 50-89 needs improvement. Below 50 is actively hurting your SEO and user experience. Mobile scores are usually lower than desktop because Google simulates slower network conditions and weaker CPUs. And since Google primarily uses mobile scores for ranking, that’s the number that matters.
Quick Wins for Speed
Compress and resize images, this is almost always the biggest fix. Switch to WebP format. Lazy-load anything below the fold. Set explicit width and height on images to prevent CLS. Minimize and defer JavaScript. Reduce third-party scripts (every analytics tag, chat widget, and A/B testing tool adds load time).
Scores vary between tests because of server response variability and network conditions. Run the test 2-3 times and take the median for a reliable baseline.
Use the HTTP Headers Viewer to check whether your caching headers are set correctly, a max-age=0 when you meant max-age=86400 is a common configuration mistake that kills repeat-visit performance.