Skip to content
Home » Blog » How to Check How Fast Your Website Loads on Google PageSpeed

How to Check How Fast Your Website Loads on Google PageSpeed

I’ve had clients swear their site “feels fast” right up until I run it through PageSpeed Insights and show them a score in the 40s. Your own experience of a site isn’t a reliable measurement, especially on a fast home connection with a cached browser. Google PageSpeed Insights gives you the real numbers, and once you know how to read them, checking your site’s speed takes about two minutes.

What You’ll Need Before You Start

This is one of the easiest tools in the SEO world to get started with. You don’t need an account, a plugin, or any special access to your site.

  • Just the URL of the page you want to test, either your homepage or a specific inner page
  • A few minutes to wait while the test runs and to read through the results
  • Optionally, a Google account if you want to save reports or connect Search Console data later

📝 Note: PageSpeed Insights tests one page at a time. If you want a full site audit across every page, you’ll want a crawler tool like Screaming Frog or a site-wide report from something like GTmetrix instead.

Step 1: Go to PageSpeed Insights

Head to pagespeed.web.dev. This is Google’s own free tool, and it’s the same underlying engine that powers speed reports inside Search Console, so the numbers you see here are the ones Google actually uses when it thinks about your site’s performance.

💡 Tip: You might also see this tool called Lighthouse, since PageSpeed Insights runs on the same Lighthouse engine you’d find in Chrome DevTools. Same scores, same categories, just a different entry point.

Step 2: Enter Your URL and Run the Test

Paste your full URL into the box, including the https:// part, and click Analyze. The test usually takes 20 to 40 seconds, sometimes a bit longer for heavier pages loaded with images and third-party scripts.

Behind the scenes, the tool is running two different kinds of analysis at once: a lab test, which simulates a page load under controlled conditions, and where available, real field data pulled from actual Chrome users who’ve visited that page. This trips a lot of people up when their lab score and their field score don’t match.

⚠️ Warning: Field data only shows up if your page gets enough real-world traffic to qualify. Low-traffic pages will show lab data only, which is a simulation and can look better or worse than what actual visitors experience.

Step 3: Read Your Core Web Vitals Scores

At the top, you’ll see a performance score from 0 to 100, color coded green, orange, or red. That single number is useful for a quick gut check, but the real detail lives in the Core Web Vitals metrics below it.

Metric What it measures Good target
LCP (Largest Contentful Paint) How long the main content takes to load Under 2.5 seconds
INP (Interaction to Next Paint) How responsive the page feels when clicked or tapped Under 200 milliseconds
CLS (Cumulative Layout Shift) How much elements jump around while loading Under 0.1

These three are what Google actually uses as ranking signals, which makes them more important than the overall 0 to 100 score. In my experience, a site can have a mediocre performance score but still pass all three Core Web Vitals comfortably, and that matters more for SEO than chasing a perfect 100.

Step 4: Check Mobile and Desktop Separately

Near the top of the results, you’ll see two tabs, one for Mobile and one for Desktop. Always check both. It’s extremely common for a site to score well on desktop and struggle badly on mobile, since mobile testing simulates a slower connection and a less powerful device.

Google primarily uses mobile performance for ranking purposes, thanks to mobile-first indexing, so if you only have time to check one, make it mobile.

📝 Note: A 30 or 40 point gap between mobile and desktop scores is normal and doesn’t necessarily mean something’s broken. It’s the testing conditions doing their job, not a bug in your site.

Step 5: Review the Diagnostics and Opportunities

Scroll below the scores and you’ll find two lists: “Opportunities” and “Diagnostics.” This is where the tool stops just measuring your site and starts telling you what’s actually slowing it down.

Opportunities are ranked by estimated time savings, so the item at the top usually deserves your attention first. Common culprits include unoptimized images, render blocking JavaScript and CSS, and fonts that load slowly. Click any item to expand it and see the specific files or resources causing the issue.

✅ Tip: Don’t try to fix everything on the list at once. Tackle image optimization first since it’s usually the biggest win for the least effort, then move on to script and font loading issues afterward.

Pro Tips for Getting Accurate Results

  • Run the test three or four times. Lab results can vary run to run depending on server load and network conditions, so a single test isn’t always representative.
  • Test your homepage and a couple of your most important inner pages separately. A fast homepage doesn’t guarantee a fast product page or blog post.
  • If your host offers a staging environment, test there too and compare against production. Sometimes hosting configuration, not code, is the real bottleneck.
  • Check back a few weeks after making changes rather than immediately. Field data especially needs time to accumulate enough real user visits to update.

Common Mistakes to Avoid

  • Chasing a perfect 100 score. Anything in the green range, generally 90 and above, is already a strong result, and diminishing returns kick in fast past that point.
  • Only checking desktop. Mobile is what matters most for ranking, and it’s usually the weaker score.
  • Testing once and assuming that’s the final answer. Scores fluctuate, so a single run can be misleading in either direction.
  • Ignoring field data in favor of lab data. Lab data is a simulation, field data is what your actual visitors experienced, and they can tell different stories.

Quick Recap

Go to pagespeed.web.dev, enter your URL, and run the test. Check both mobile and desktop scores, focus on the Core Web Vitals metrics rather than the overall number, and work through the Opportunities list starting with the highest impact items.

Wrapping Up

You now know exactly how to check your site’s speed and, more importantly, how to actually read what the results are telling you. Run the test on your most important pages, prioritize the highest impact fixes first, and recheck in a few weeks once real user data has had time to catch up. A faster site isn’t just a ranking factor, it’s a better experience for everyone who lands on it.

Tags: