Setting Up PageSpeed Insights and Reading Your First Report

Your site is live. Traffic trickles in. But you're stuck below page two on Google. You've shipped the product. You haven't shipped the visibility.

One of the fastest ways to move rankings is to fix the technical foundation your content sits on. PageSpeed Insights is the tool Google uses to measure it. It's free, it's official, and it's the first audit every founder should run before hiring an agency or obsessing over backlinks.

This guide walks you through setting it up, running your first report, and—most importantly—identifying the three issues that actually move rankings. Everything else is noise.

Prerequisites: What You Need Before You Start

Before you run your first PageSpeed Insights audit, make sure you have these in place:

A live website. Your site needs to be publicly accessible at a real domain. Localhost doesn't work. Staging servers with password protection won't show results.

Admin access to your site. You'll need to make changes based on what PageSpeed tells you. If you're on a platform like Shopify, understand the default SEO settings that are costing you sales, or if you're on WordPress, you'll need plugin access or theme editing capability.

A Google account. PageSpeed Insights is free and requires no login, but if you want to track results over time and connect to Google Search Console, a Google account helps.

10 minutes. You don't need a full day to run your first audit. You need 10 minutes to set it up and another 20 to understand what the report is telling you.

Realistic expectations. PageSpeed Insights measures one thing: how fast your pages load. It doesn't measure whether your content ranks or whether people want to read it. It measures the technical floor. Fix the floor first, then build the house.

If you're shipping your first SEO push, consider pairing this with the 30-day SEO sprint every busy founder should run. Page speed is one pillar. Keywords, content, and crawlability matter equally. But speed is the fastest to audit and often the fastest to fix.

Understanding What PageSpeed Insights Actually Measures

PageSpeed Insights is Google's official performance auditing tool. It's built on Lighthouse, an open-source tool that crawls your page and measures how fast it loads, how interactive it is, and how stable it is visually.

The tool doesn't measure your gut feeling about speed. It measures real user data from the Chrome User Experience Report (CrUX), which aggregates performance metrics from millions of real Chrome users. If your site isn't in CrUX yet (usually takes 28+ days of traffic), PageSpeed will use Lighthouse lab data instead—simulated data on a standard test device with standard network conditions.

This distinction matters. Lab data is predictable but artificial. Real user data is messier but true. Both inform your ranking potential.

PageSpeed measures three core metrics:

Largest Contentful Paint (LCP). How long it takes for the main content to appear on screen. This is the metric most correlated with perceived speed. If your hero image takes 5 seconds to load, users see a blank page for 5 seconds. That kills both UX and rankings.

First Input Delay (FID) / Interaction to Next Paint (INP). How responsive your page is when users click, tap, or type. A slow response makes the page feel broken even if it looks fast. Google is shifting from FID to INP, which measures all interactions, not just the first.

Cumulative Layout Shift (CLS). How much your page jumps around while loading. If your layout shifts after the user starts reading, that's frustrating and it signals poor engineering. Good CLS is invisible.

PageSpeed also measures secondary metrics like First Contentful Paint (FCP), Time to First Byte (TTFB), and Total Blocking Time (TBT). These matter for the full picture, but the three above are what Google weights most heavily in rankings.

Understanding the difference between lab and field data is critical. Google's official PageSpeed Insights documentation explains that field data comes from real users, while lab data simulates a specific device and network. If you have field data, trust it more. If you don't, lab data is your starting point.

Step 1: Navigate to PageSpeed Insights and Enter Your URL

Go to https://pagespeed.web.dev. This is the official Google tool. No account required. No setup needed.

You'll see a simple interface: a search box at the top with the text "Enter a URL to analyze."

Type your domain. Use your homepage first. For example, if your site is example.com, enter https://example.com (not http://, always use https://). If you want to test a specific page, enter the full URL: https://example.com/pricing or https://example.com/blog/my-post.

PageSpeed Insights tests both mobile and desktop versions. Mobile is weighted more heavily in Google's ranking algorithm, so if your mobile score is low, that's your priority.

Hit Enter or click "Analyze."

PageSpeed will now crawl your page. This takes 30-90 seconds depending on your site's complexity and current server load. You'll see a loading bar. Wait for it to finish. Don't close the tab.

If you get an error like "We couldn't access this URL," check:

Is your site publicly accessible? (Not behind a login or firewall)
Did you use the correct domain? (Typos happen)
Is your site up? (Check if you can load it in another browser tab)
Are you blocking Google's crawlers? (Check your robots.txt)

Once the analysis completes, you'll see your report.

Step 2: Read Your Score and Understand What It Means

PageSpeed Insights shows you a score from 0-100 for mobile and desktop separately. The score is color-coded:

90-100 (green). Fast. Your site loads quickly. Continue optimizing but you're in good shape.

50-89 (yellow/orange). Moderate. Your site has performance issues that are likely affecting rankings and user experience. Fix these.

0-49 (red). Slow. Your site is losing rankings and users to speed. This is your top priority.

Your score is not a number pulled from thin air. It's a weighted average of:

Largest Contentful Paint (25% weight)
Interaction to Next Paint (35% weight)
Cumulative Layout Shift (10% weight)
First Contentful Paint (10% weight)
Time to First Byte (10% weight)
Several other minor factors (10% combined)

If your mobile score is 65 and your desktop score is 85, Google treats your mobile score as the truth. Mobile-first indexing means Google crawls and ranks your mobile version. If mobile is slow, you're slow in Google's eyes.

Don't obsess over the exact number. A score of 68 vs. 72 doesn't matter. What matters is the category: are you green, yellow, or red? And what specific metrics are dragging you down?

Scroll down past the score. You'll see your metrics broken down:

Metrics section. Shows your LCP, INP, CLS, FCP, TTFB, and TBT. Each has a threshold: green (good), orange (needs improvement), red (poor).

If your LCP is 4.2 seconds, that's red. Good LCP is under 2.5 seconds. If your INP is 250ms, that's orange. Good INP is under 100ms. These numbers tell you exactly where your performance problems are.

This is where most founders stop reading. They see a red number and panic. Don't. Keep scrolling.

Step 3: Identify the Three Issues That Actually Move Rankings

PageSpeed Insights shows you dozens of optimization opportunities. "Eliminate render-blocking resources." "Defer offscreen images." "Minify CSS." "Remove unused JavaScript."

Most of these are noise. They're technically correct but they won't move your rankings 10 positions in 30 days. Some will. Three, specifically, move the needle fast enough that a busy founder should care.

Issue #1: Largest Contentful Paint (LCP) over 2.5 seconds.

This is the metric most correlated with user bounce rate and Google rankings. If your hero image takes 4 seconds to load, users leave before they see your value prop. Google sees that bounce and ranks you lower.

In the PageSpeed report, scroll to the "Opportunities" section. Look for suggestions like:

"Reduce the impact of third-party code" (especially fonts, analytics, ads)
"Defer offscreen images"
"Serve images in next-gen formats" (WebP instead of PNG/JPG)
"Properly size images"
"Reduce CSS" (if your stylesheet is huge)

The most common LCP culprit? A large hero image that loads slowly or a render-blocking font. If your site has a big banner image, that's likely your problem.

Fix: Optimize your largest image. Compress it. Serve it in WebP format. Make sure it's lazy-loaded if it's below the fold. If your LCP is slow because of a third-party font, switch to system fonts or use a faster font service like Google Fonts with font-display: swap.

This single fix often drops LCP from 4+ seconds to 2 seconds. That moves rankings.

Issue #2: Cumulative Layout Shift (CLS) over 0.1.

CLS measures how much your page jumps around while loading. Common culprits:

Ads that load after content and push everything down
Images without defined dimensions
Embeds (YouTube, Twitter) that load late
Fonts that swap sizes between load states

PageSpeed will show you "Avoid large layout shifts" in the opportunities section. It'll even highlight the elements that are shifting.

Fix: Define width and height on all images. Set dimensions on ad containers before they load. Use font-display: swap for fonts so text appears immediately even if the font is still loading.

This is often a 30-minute fix that has zero impact on functionality but huge impact on rankings. Google explicitly weights CLS in its ranking algorithm.

Issue #3: Time to First Byte (TTFB) over 600ms.

TTFB is how long your server takes to respond to a request. If your TTFB is 2 seconds, everything downstream (images, JavaScript, CSS) starts loading 2 seconds late.

PageSpeed will suggest "Reduce server response time" if this is your problem.

Fix: This one is harder because it usually requires server-side changes. Common solutions:

Switch to a faster hosting provider (Vercel, Netlify, or a CDN if you're on shared hosting)
Enable caching (browser cache, server cache, Redis)
Optimize your database queries if you're generating pages dynamically
Use a CDN to serve static assets from servers closer to your users

If you're on Shopify, Vercel, or Netlify, TTFB is usually not your problem. If you're on shared hosting or a slow VPS, it probably is.

Ignore everything else in the PageSpeed report for now. The report will list 20+ opportunities. Most are 1-2% improvements. These three are 10-20% improvements. Ship the big wins first.

Step 4: Understand the Opportunities Section (and What to Ignore)

PageSpeed lists optimization opportunities in order of estimated impact. You'll see things like:

"Eliminate render-blocking resources"
"Reduce CSS"
"Remove unused CSS"
"Minify JavaScript"
"Defer offscreen images"
"Properly size images"
"Use modern image formats"
"Reduce unused JavaScript"

Each has an estimated savings in milliseconds. For example: "Reduce unused CSS: Potential savings of 45ms."

Here's the brutal truth: a 45ms improvement to your Largest Contentful Paint doesn't move rankings if your LCP is already 3 seconds. You need to cut it in half. You need 1000ms+ improvements, not 45ms improvements.

Look at the opportunities and find the ones with the biggest estimated impact. Usually the top 3-5 opportunities account for 70%+ of the potential gains. Those are the ones to ship.

Ignore the rest. Minifying CSS is good practice but it's not why you're invisible on Google. Deferring offscreen images helps but it's not the bottleneck. Focus on the three issues above and the top opportunities in the report.

One more thing: understanding the difference between indexing and ranking is critical here. PageSpeed measures ranking factors, not indexing factors. Your page can be indexed but slow. Slow pages rank lower. Fix speed, then worry about content and links.

Step 5: Connect to Google Search Console (Optional but Recommended)

PageSpeed Insights shows you lab data and field data. If you have traffic, field data is more accurate. To see field data in PageSpeed, your site needs to be in Google's Chrome User Experience Report (CrUX).

CrUX data appears automatically once your site gets enough Chrome traffic (usually 28+ days). Until then, you see lab data only.

To verify your site is in CrUX and see field data, connect PageSpeed to Google Search Console:

Go to Google Search Console
Verify ownership of your domain (if you haven't already)
Go to "Experience" > "Page Experience"
You'll see a list of pages with field data (if available)

This shows you real user metrics, not simulated ones. If your site has traffic, this is the truth.

If you don't have field data yet, don't worry. Lab data is your starting point. Once you get traffic, field data will appear and you can compare.

Step 6: Run Audits on Your Key Pages

Your homepage is a good start, but it's not the whole story. Run PageSpeed Insights on:

Your top landing pages (pricing, product demo, signup)
Your top blog posts (if you have organic traffic)
Any page you want to rank for a specific keyword

Different pages have different performance profiles. Your homepage might be fast but your blog might be slow because of comment widgets or ad networks. Your product page might have a slow third-party payment processor.

Run audits on 5-10 of your most important pages. Find the patterns. Are all pages slow or just some? Is it a global issue (server, hosting) or page-specific (heavy images, third-party scripts)?

If you're running a content-heavy strategy as part of your first 100 days of SEO, make sure your blog posts are fast. A slow blog post doesn't rank, even if the content is great.

Step 7: Prioritize and Ship Your Fixes

You now have a list of issues. Here's how to prioritize:

Tier 1: The three issues above (LCP, CLS, TTFB).

If your LCP is over 2.5 seconds, optimize your largest image. If your CLS is over 0.1, define image dimensions and ad container sizes. If your TTFB is over 600ms, consider a CDN or faster hosting.

These three fixes often take 30 minutes to 2 hours. They move rankings.

Tier 2: The top 3-5 opportunities in the report.

Once you've fixed the core metrics, tackle the biggest opportunities. If the report says "Reduce render-blocking resources: 200ms savings," that's worth doing.

Tier 3: Everything else.

Minifying CSS, deferring images, removing unused JavaScript—these are good hygiene. But they're not why you're ranking low. Do them if you have time. Don't do them if you have a choice between this and shipping content.

Remember: SEO triage for busy founders is about the 80/20. Page speed is one pillar. Keywords, content, crawlability, and links matter equally. Don't spend 40 hours optimizing PageSpeed if you haven't shipped your keyword roadmap.

Ship the big wins. Move on. Measure results in 30 days.

Step 8: Measure Progress and Re-Test

After you ship your fixes, re-run PageSpeed Insights on the same pages. You should see improvements in your metrics and score.

But here's the important part: don't obsess over the score improving from 72 to 78. That's noise. What matters is:

Did your LCP drop below 2.5 seconds?
Did your CLS drop below 0.1?
Did your TTFB drop below 600ms?

If yes to all three, you've fixed the technical foundation. Now focus on keywords, content, and links.

If no, dig deeper. Maybe your server is still slow. Maybe you have another image problem. Re-run the audit and look for new bottlenecks.

Set a cadence: audit your site every 30 days. As you add features, new performance issues emerge. New tracking scripts, new ads, new embeds—all of these can slow your site. The 10-minute SEO review every founder should run monthly includes a PageSpeed check. Make it a habit.

Common Mistakes Founders Make When Reading PageSpeed Reports

Mistake #1: Obsessing over the score instead of the metrics.

A score of 62 feels bad. A score of 78 feels good. But the score is a composite. What matters is whether your LCP, INP, and CLS are in the green. You can have a 65 score with one green metric and two orange metrics. Fix the orange ones. The score will improve.

Mistake #2: Trying to fix everything at once.

PageSpeed shows 20+ opportunities. You can't ship all of them in a week. Pick three. Ship them. Measure. Repeat.

Mistake #3: Ignoring field data in favor of lab data.

If you have traffic, your field data is the truth. Lab data is a simulation. If your lab data says you're fast but your field data says you're slow, trust field data. Your real users are experiencing slowness.

Mistake #4: Assuming PageSpeed is the only ranking factor.

It's not. Content, links, crawlability, and intent matter equally. A fast page with no keywords and no links ranks nowhere. A slow page with great content and strong links can still rank. Speed is the foundation, not the whole house.

Mistake #5: Shipping page speed fixes and expecting rankings to move immediately.

Google re-crawls your site every few weeks. It takes 2-4 weeks for a page speed improvement to show up in rankings. Ship the fix, then move on to content and links. Check back in a month.

Why Page Speed Matters for Founders Specifically

If you're a founder without an agency budget, page speed is your competitive advantage. Agencies optimize for links and content. Those take months. Page speed can be fixed in weeks.

A 1-second improvement to your page load time can move you 5-10 positions on Google for competitive keywords. That's free traffic. That's traction.

Moreover, fast pages convert better. A 1-second delay in page load time reduces conversions by 7%. If you're running a SaaS, e-commerce, or any product with a signup flow, page speed directly impacts your bottom line.

PageSpeed Insights is free. It takes 10 minutes. The fixes are usually free (optimize images, remove unused code, enable caching). This is one of the highest-ROI SEO moves you can make as a founder.

Connecting Page Speed to Your Broader SEO Strategy

Page speed is one of the 5 pillars of modern SEO every founder should master. The others are crawlability, content, links, and intent (or AEO, which is AI Engine Optimization).

Here's how they fit together:

Crawlability. Google needs to find and crawl your pages. If your pages aren't crawlable, nothing else matters. Crawlability for founders is a plain-English primer you should read after this.

Content. Your pages need to match what people are searching for. Keywords, intent, and quality content matter. If you're shipping fast, consider the 30-day SEO sprint with a focus on keyword roadmap and AI content.

Page Speed. Your pages need to load fast. This guide covers it.

Links. Other sites need to link to you. This is the slowest pillar but the most powerful. Start with content and speed first.

Intent and AEO. Your content needs to be cited by AI (ChatGPT, Claude, Perplexity). AEO foundations cover the 4 signals that matter.

If you're starting from scratch, audit your site with PageSpeed Insights. Fix the three issues above. Then move to keywords and content. Don't obsess over page speed at the expense of everything else.

The Fastest Way to Get a Complete Audit

PageSpeed Insights is one piece of the puzzle. A complete SEO audit includes:

Domain audit (crawl errors, indexation, redirect chains)
Keyword roadmap (what to rank for, search volume, difficulty)
Content audit (what exists, what's missing, what's underperforming)
Technical SEO audit (speed, crawlability, mobile-friendliness, schema)
Backlink audit (who links to you, who links to competitors)
Competitive analysis (what's working for them, what you can steal)

PageSpeed Insights covers one piece: page speed. If you want a complete audit in under 60 seconds, Seoable delivers a domain audit, brand positioning, keyword roadmap, and 100 AI-generated blog posts for a one-time $99 fee. It's built for founders who ship.

But for page speed specifically, PageSpeed Insights is the official Google tool and it's free. Use it.

Key Takeaways: What Every Founder Should Remember

PageSpeed Insights is your free, official window into how Google sees your site's performance. Here's what you need to do:

Go to pagespeed.web.dev and enter your domain. Takes 30 seconds.
Look for the three metrics that matter: LCP, CLS, and TTFB. Ignore everything else.
If LCP is over 2.5 seconds, optimize your largest image. Compress it, serve it in WebP, lazy-load it.
If CLS is over 0.1, define dimensions on images and ad containers. Prevent layout shifts.
If TTFB is over 600ms, consider a CDN or faster hosting. Your server is the bottleneck.
Run audits on your top 5-10 pages. Different pages have different issues.
Re-test after you ship fixes. Measure progress every 30 days.
Remember: page speed is one pillar. Keywords, content, crawlability, and links matter equally. Don't spend 40 hours on speed if you haven't shipped your content strategy.

PageSpeed Insights is the fastest way to find and fix your technical foundation. It's free, it's official, and it moves rankings. Use it before you hire an agency or obsess over backlinks.

Ship the fix. Measure results. Move on.

What to Do Next

You've run your first PageSpeed audit. You know your three issues. Here's your next move:

If you're shipping SEO from scratch, read week 1 of SEO: what a busy founder should actually ship. Five concrete deliverables: domain audit, keyword roadmap, content strategy, technical fixes, and launch prep.

If you want a day-by-day playbook, your first 100 days of SEO is a founder playbook with 100 shippable actions. Page speed is week one. Keywords and content are week two. Links are week three.

If you want to skip the manual work and get a complete audit with 100 AI-generated blog posts in 60 seconds, Seoable is built for founders like you. One-time $99 fee. Domain audit, brand positioning, keyword roadmap, and content. No monthly fees. No agency markup.

But whatever you do next, you've already taken the most important step: you've measured your technical foundation. That's where all SEO starts.