Lighthouse for Founders: Running Your First Audit in Chrome

The Free Audit Every Founder Owns

You shipped. Your product works. But nobody knows it exists.

You're not alone. Most founders skip the technical SEO groundwork because it feels abstract, expensive, or both. Agencies want retainers. Tools cost monthly. The setup looks endless.

There's a faster path: Lighthouse, built into Chrome DevTools, gives you a free domain audit in under five minutes. No signup. No credit card. No waiting.

Lighthouse audits your site for SEO, performance, accessibility, and best practices. The scores are brutal—they'll show you exactly what's broken. The fixes are concrete—they point to specific problems, not vague recommendations.

This guide walks you through running your first Lighthouse audit, reading the results, and shipping the fixes that matter most. By the end, you'll have a technical foundation that compounds. You'll know your crawl health, your page speed, your schema gaps, and your ranking ceiling before you write a single blog post.

Let's go.

Prerequisites: What You Need Before You Start

Before running your first Lighthouse audit, make sure you have the basics in place.

You need:

A live website (even a simple landing page counts)
Chrome browser (any recent version)
5 minutes of uninterrupted time
A quiet internet connection (ideally wired, not WiFi)

You should have:

Your domain registered and pointing to your server
At least one page indexed in Google (check: site:yourdomain.com in Google Search)
Basic understanding of what SEO is (this guide assumes zero technical depth)

You don't need:

An SEO agency
A paid tool subscription
A custom domain (subdomains work for audits)
Perfect code or design

If your site is still in development or behind authentication, you can still run Lighthouse, but the audit won't be public-facing. We'll cover that in the pro tips section.

One more thing: Lighthouse audits are most useful when you run them regularly. This first audit is your baseline. You'll compare future audits to this one to measure progress. Write down your scores today.

Step 1: Open Chrome DevTools

Chrome DevTools is the developer console built into every Chrome browser. It's where Lighthouse lives.

On Windows or Linux:

Open Chrome
Press Ctrl + Shift + I (that's Control, Shift, and the letter I)
Or right-click anywhere on your page and select "Inspect"

On Mac:

Open Chrome
Press Cmd + Option + I (Command, Option, and the letter I)
Or right-click anywhere on your page and select "Inspect"

A panel will open at the bottom or side of your screen. This is DevTools. It shows the HTML structure, CSS, JavaScript, network requests, and more.

You'll see tabs along the top: Elements, Console, Sources, Network, Performance, Application, Security, and more. Don't worry about those yet.

Next step: Find the Lighthouse tab.

Look for a tab labeled "Lighthouse" in the DevTools panel. If you don't see it, click the >> icon (double arrow) on the right side of the tab bar. This reveals hidden tabs. Lighthouse should be in that dropdown.

If Lighthouse still isn't visible, you might be using an older version of Chrome. Update Chrome to the latest version and try again. Lighthouse has been built into Chrome since version 60 (released in 2017), so any recent Chrome will have it.

Click the Lighthouse tab. You're now in the Lighthouse panel.

Step 2: Configure Your Audit Settings

Before you run the audit, you need to tell Lighthouse what to check and how to check it.

In the Lighthouse panel, you'll see several options:

Device type:

Mobile
Desktop

Choose based on your audience. Most founders should start with Mobile because Google prioritizes mobile-first indexing. If you're building B2B software or a desktop-only tool, Desktop is fine. You can run both audits to compare.

Categories:

Performance
Accessibility
Best Practices
SEO
PWA (Progressive Web App)

For your first audit, select at least Performance, SEO, and Best Practices. Accessibility and PWA are useful but secondary. Uncheck PWA unless you're building an app-like experience.

Throttling:

Simulated fast 3G (default)
Simulated 4G
No throttling

Leave this on "Simulated fast 3G." This mimics real-world conditions for users on slower connections. It's more realistic than testing on your office WiFi.

Clear storage:

Check this box

This clears your browser cache before the audit, simulating a first-time visitor. This is what you want.

Screenshot:

Check this box

Lighthouse will capture a screenshot of your page during the audit. Useful for debugging.

Once you've selected your settings, you're ready to run the audit.

Step 3: Run the Audit

Click the blue "Analyze page load" button at the bottom of the Lighthouse panel.

Lighthouse will now reload your page and run a series of automated checks. This takes 30 seconds to 2 minutes, depending on your page size and server response time.

You'll see a progress bar. Don't close the DevTools panel or navigate away during the audit. Let it finish.

While Lighthouse runs, it's checking:

Page load speed (time to interactive, largest contentful paint, cumulative layout shift)
SEO basics (meta tags, mobile friendliness, structured data)
Accessibility (color contrast, alt text, heading hierarchy)
Best practices (HTTPS, no console errors, modern JavaScript)
Performance (unused CSS, unminified code, render-blocking resources)

Once the audit completes, you'll see your scores.

Step 4: Read Your SEO Score

Your SEO score is the first number you should care about. It's out of 100.

90-100: Good. Your site has the basics. You can focus on content and links.

70-89: Needs work. You have fixable SEO gaps. Address these before investing in content.

Below 70: Critical issues. Your site won't rank until you fix these. This is common for new sites.

Scroll down to the "SEO" section in your Lighthouse report. You'll see a list of checks, each marked as:

✓ Passed (green)
✗ Failed (red)
⚠ Warnings (yellow)

Common SEO failures:

Mobile-friendly: Lighthouse checks if your site is responsive. If it fails, your site doesn't adapt to small screens. Google will deprioritize it. Fix this first.

Meta descriptions: If missing, Lighthouse flags it. Meta descriptions don't directly impact rankings, but they improve click-through rates. Write one for every page.

Structured data: Lighthouse checks for schema markup (JSON-LD). This tells search engines what your page is about. If you're missing it, you're leaving ranking potential on the table. We'll cover schema in a later section.

Crawlability: Lighthouse checks if your robots.txt and sitemap are valid. If they're missing or broken, search engines waste crawl budget. Fix these.

Page title: Lighthouse verifies you have a unique page title. If it's missing or duplicate, your page won't rank. Every page needs a unique, descriptive title under 60 characters.

Write down which checks failed. These are your SEO priorities for the next week.

Step 5: Read Your Performance Score

Performance is the second critical score. It's also out of 100.

Page speed is a ranking factor. Slow sites rank lower. Slow sites also convert worse. A one-second delay can cost you 7% of conversions.

90-100: Fast. Your site loads quickly. Users won't bounce due to slowness.

50-89: Moderate. Your site is usable but has room to improve. Users on slow connections will wait longer than they should.

Below 50: Slow. Your site is frustrating to use. You're losing users and rankings.

Lighthouse measures several metrics:

Largest Contentful Paint (LCP): How long until the main content loads. Target: under 2.5 seconds.

First Input Delay (FID): How long until the page responds to user input. Target: under 100 milliseconds.

Cumulative Layout Shift (CLS): How much the page jumps around as it loads. Target: under 0.1.

If any of these are red, you have a problem. Scroll down to see the specific issues.

Common performance problems:

Unminified CSS/JavaScript: Your code is larger than it needs to be. Minification removes unnecessary characters. Most frameworks do this automatically in production.

Unused CSS: You're loading styles for code that doesn't exist on the page. Remove it.

Large images: Images are often the biggest performance culprit. Compress them or use modern formats like WebP.

Render-blocking resources: JavaScript or CSS is blocking the page from rendering. Move non-critical scripts to the end of the page.

No caching: Your server isn't telling browsers to cache assets. This forces repeat downloads on every visit.

Performance issues are usually fixable in a day or two. Prioritize LCP if you only have time for one fix.

Step 6: Review Best Practices

Best Practices is a catch-all category for web standards and security.

Common failures:

HTTPS: Your site should use HTTPS (secure protocol). If it's HTTP, you're vulnerable and Google will deprioritize you. Get an SSL certificate (free from Let's Encrypt).

Console errors: JavaScript errors in the browser console indicate broken functionality. Fix the highest-impact errors first.

Outdated libraries: You're using old versions of third-party code. Update them.

Permissions policy: You haven't declared what features your site uses (camera, microphone, location). Add a permissions policy.

Most of these are one-time fixes. Address the red items and move on.

Step 7: Export and Save Your Report

Lighthouse generates a detailed report. Save it.

At the top of your Lighthouse results, you'll see a menu icon (three dots). Click it and select "Save as JSON" or "Generate report."

This creates a file you can download and store. Run this audit monthly. Compare your scores to last month. Track progress.

You can also take a screenshot of your scores and paste them into a Google Doc or Notion. The goal is to have a baseline.

Understanding Lighthouse Limitations

Lighthouse is powerful, but it's not perfect. Understand what it can and can't tell you.

What Lighthouse does well:

Identifies technical SEO gaps (schema, mobile friendliness, crawlability)
Flags performance bottlenecks
Catches accessibility issues
Provides actionable recommendations

What Lighthouse misses:

Keyword relevance (it doesn't know if your content matches search intent)
Backlink quality or quantity (Lighthouse can't see your link profile)
Competitor positioning (it only audits your site)
Content depth or uniqueness
User engagement metrics (bounce rate, time on page)
Ranking potential (Lighthouse doesn't predict where you'll rank)

Lighthouse is a technical foundation. It's not a complete SEO strategy. You still need keyword research, content strategy, and link building. But you can't skip the technical foundation and expect to rank.

Think of Lighthouse as a prerequisite, not a destination.

Pro Tips: Advanced Lighthouse Usage

Run audits on multiple pages:

Don't just audit your homepage. Run Lighthouse on your most important pages: product pages, pricing, blog posts, contact page. Each page gets its own score. Fix the pages with the lowest scores first.

Audit on different devices:

Run the audit on both Mobile and Desktop. Mobile is more important for most sites, but Desktop matters if you have a desktop-heavy audience. Compare the scores.

Use throttling to simulate real users:

Leave "Simulated fast 3G" enabled. This mimics users on slower connections. If your site fails on 3G, it will fail in the real world. Most users aren't on fiber.

Run audits in incognito mode:

Open an incognito window (Ctrl+Shift+N on Windows, Cmd+Shift+N on Mac). Run Lighthouse there. This prevents browser extensions from interfering with results.

Test pages behind authentication:

If your site requires login, you can still audit pages. Log in normally, then open DevTools and run Lighthouse. The audit will use your authenticated session.

Use Chrome Extensions for continuous monitoring:

Google offers a Lighthouse Chrome Extension that runs audits without opening DevTools. Install it for quick checks.

Compare against competitors:

Run Lighthouse on your competitor's site. Open their homepage, run an audit, and compare scores. This gives you a competitive benchmark.

Automate audits with the CLI:

Once you're comfortable with Lighthouse, you can run audits from the command line using the Lighthouse CLI tool. This lets you schedule audits and track changes over time.

Common SEO Fixes You Can Ship This Week

Lighthouse will flag issues. Here's how to fix the most common ones quickly.

Missing meta descriptions:

Every page needs a unique meta description (150-160 characters). This is the text that appears under your title in Google search results. Write one for each page. It doesn't directly impact rankings, but it improves click-through rates.

Mobile-friendliness:

If Lighthouse flags this, your site isn't responsive. Check your CSS. Make sure your viewport meta tag is set: <meta name="viewport" content="width=device-width, initial-scale=1">. Test on a real phone.

Missing structured data:

Add JSON-LD schema markup to your pages. For a homepage, use Organization schema. For blog posts, use Article schema. For products, use Product schema. Google's Schema Markup Helper can generate the code.

Large images:

Compress images using tools like TinyPNG or ImageOptim. Use modern formats like WebP. Lazy-load images that aren't above the fold.

Render-blocking CSS:

Minify your CSS. Inline critical styles above the fold. Defer non-critical styles.

No HTTPS:

Get an SSL certificate. Most hosting providers offer free certificates through Let's Encrypt. Update your site URL to HTTPS.

These fixes usually take a day or two. Do them before writing content. Content won't rank if the technical foundation is broken.

Connecting Lighthouse Audits to Your Broader SEO Strategy

Lighthouse gives you a technical baseline. But it's one piece of a larger SEO strategy.

After you run your first Lighthouse audit and fix the critical issues, you need to move to the next phase: keyword research, content strategy, and ongoing optimization.

If you're a founder who shipped but lacks organic visibility, start here. Run Lighthouse. Fix the red items. Then move to domain audits and keyword roadmaps to identify what to write about.

If you're preparing for a product launch, use Lighthouse as part of your pre-launch SEO checklist. Technical SEO on day one compounds. You'll rank faster if you fix crawlability and speed before launch.

If you're in your first 100 days of building organic visibility, integrate Lighthouse audits into your weekly routine. Run audits every two weeks. Track improvements. This keeps you accountable.

For a compressed timeline, run a 30-day SEO sprint where week one is Lighthouse fixes, week two is keyword research, week three is content, and week four is optimization.

If you're unsure what to prioritize, focus on the 80/20. Lighthouse audits, keyword roadmaps, and AI-generated content are the three moves that move the needle. Everything else is noise.

The key insight: don't hire an agency until you've done this work yourself. You'll understand your site better, you'll know what's actually broken, and you'll save money. Most founders don't need an agency in their first 100 days. They need a process.

Running Lighthouse on Different Platforms

Lighthouse lives in Chrome DevTools, but there are other ways to run it.

web.dev:

Visit web.dev and enter your domain. Lighthouse will run in the cloud and show you results. No DevTools required. This is useful if you want to share results with your team.

PageSpeed Insights:

Google's PageSpeed Insights runs Lighthouse under the hood. It's a simplified interface, good for non-technical founders.

Lighthouse Chrome Extension:

Install the Lighthouse Chrome Extension for one-click audits without opening DevTools. Faster for repeated checks.

Lighthouse CLI:

For advanced users, install Lighthouse via npm and run audits from the command line. This lets you automate and schedule audits.

Third-party tools:

Tools like Semrush, Ahrefs, and others include Lighthouse audits alongside other SEO data. These are useful if you already use these platforms, but they're not necessary for your first audit.

For your first audit, stick with Chrome DevTools. It's free, it's built-in, and it's all you need.

Troubleshooting: What If Lighthouse Won't Run?

"Lighthouse failed to load the page."

Your page isn't loading. Check:

Is your domain live and accessible?
Are you connected to the internet?
Is there a firewall blocking the request?
Is your site requiring authentication?

Try running the audit in an incognito window. Try a different page. Try reloading the page and running again.

"Performance score is unusually low."

Lighthouse might be running on a slow connection or slow server. Run the audit again. If it's consistently low, you have a real performance problem. Check your server response time in the Network tab of DevTools.

"SEO score seems wrong."

Lighthouse only checks technical SEO. It doesn't check content quality, keyword relevance, or backlinks. A high SEO score doesn't mean you'll rank. It means your technical foundation is solid.

"I can't find the Lighthouse tab."

You're using an old version of Chrome. Update to the latest version. Lighthouse has been built-in since Chrome 60.

"My site is behind a login."

Log in first, then open DevTools and run Lighthouse. The audit will use your authenticated session. Or audit a public page instead.

Taking Action: Your Next Steps

You've run your first Lighthouse audit. You know your scores. Now ship.

This week:

Fix the red SEO items (mobile friendliness, meta descriptions, structured data)
Fix the red performance items (image compression, render-blocking resources)
Run the audit again and compare scores

Next week:

Research keywords using a keyword roadmap
Identify your ranking ceiling (what's the maximum traffic you can get if you rank for your target keywords?)
Prioritize content topics

Week 3:

Write or generate content for your top 5 keywords
Optimize pages for those keywords
Build internal links

Week 4 and beyond:

Monitor your rankings
Fix crawl issues as they appear
Run Lighthouse monthly to track progress
Measure what matters and adjust

The brutal truth: Lighthouse is a prerequisite, not a strategy. A perfect Lighthouse score with no content and no links won't rank you. But a broken technical foundation will prevent you from ranking no matter how good your content is.

Fix the foundation first. Then build on it.

Key Takeaways

Lighthouse is a free, built-in audit tool. It lives in Chrome DevTools. No signup. No cost. No excuses.

SEO score matters most. Fix mobile friendliness, meta descriptions, and structured data. These are table stakes.

Performance score is a ranking factor. Compress images, minify code, and optimize server response time. Speed converts.

Best Practices catches security and standards issues. Get HTTPS, fix console errors, update libraries.

Lighthouse is not a complete SEO strategy. It audits technical SEO only. You still need keyword research, content, and links.

Run audits monthly. Track progress. Compare to your baseline. This keeps you accountable.

Fix critical issues before you write content. A broken site with great content won't rank. A fast, crawlable site with mediocre content will.

You don't need an agency. You can run this audit yourself in five minutes. You can fix most issues yourself in a day. You can build organic visibility without a retainer.

Ship your Lighthouse audit today. Fix the red items this week. Measure again next month. This is how founders build organic visibility that compounds.

You shipped. Now make sure people can find you.