Foglift vs Lighthouse: Technical Audit Comparison

Lighthouse diagnoses page performance in depth. Foglift adds a broader Technical Audit for AI Readiness, SEO, security, and accessibility. Here is when to use each.

Short Answer

Use Foglift for a broad Technical Audit. Use Lighthouse for deeper performance diagnosis. A Foglift audit can tell you that a large HTML document is weakening performance and show the issue beside AI Readiness, SEO, security, and accessibility. Lighthouse can then help a developer investigate lab metrics, main-thread work, resource cost, and specific opportunities.

Foglift dogfood result, July 14, 2026

The live Technical Audit returned 97/100 overall, with performance at 90 and one warning for a 247KB HTML document. That result is a readiness baseline. It does not substitute for Lighthouse's lab trace or field performance data.

What Google Lighthouse Measures

Google describes Lighthouse as an open-source automated tool for improving web-page quality. Its established categories cover performance, accessibility, best practices, and SEO. It can run in Chrome DevTools, from the command line, as a Node module, through PageSpeed Insights, or in continuous integration.

Lighthouse's performance score is a weighted lab score. The documented Lighthouse 10 weights use First Contentful Paint, Speed Index, Largest Contentful Paint (LCP), Total Blocking Time (TBT), and Cumulative Layout Shift (CLS). Google also warns that scores can vary with test conditions, device choice, routing, extensions, and page experiments.

Lighthouse's Experimental Agentic Browsing Category

Google added an experimental Agentic Browsing category for Chrome 150 and later. It evaluates whether a site is constructed for machine interaction through deterministic audits. The current checks cover registered WebMCP tools and schema, forms that could expose declarative WebMCP, agent-focused accessibility, layout stability, and llms.txt retrieval.

The category does not return a weighted 0 to 100 score. It reports a pass ratio, audit-level pass or fail states, warnings, and informational counts while the standards are still emerging. WebMCP audits also require the WebMCP origin trial. These constraints make it a useful developer diagnostic, but they keep it distinct from prompt-level AI search measurement.

What Foglift Measures

Foglift's Free Technical Audit gives a cross-discipline baseline for AI Readiness, SEO, performance, security, and accessibility. It also reports page issues and recommended fixes in one crawlable result. Foglift's separate monitoring product measures brand mentions, sentiment, citations, and competitors across AI engines.

The distinction matters. A technically ready page can still be absent from an AI answer. A cited brand can also have a page-level warning. Technical Audit data and AI Visibility monitoring answer different questions.

Foglift vs Lighthouse: Feature Comparison

Capability	Foglift	Lighthouse
Primary job	Broad website Technical Audit	Deep page-quality, lab-performance, and experimental machine-interaction audits
AI search readiness	8-dimension AI Readiness analysis	Experimental Agentic Browsing checks in Chrome 150+
Performance	Performance score and issue summary	Weighted lab metrics, diagnostics, and opportunities
Accessibility	Accessibility score and issue checks	Automated accessibility audits
Security	Security headers and HTTPS checks	HTTPS and browser best-practice checks
AI crawler access	Search, training, and user-fetch crawler policy checks	llms.txt retrieval and agent-interaction checks; no dedicated crawler-policy audit
Developer workflow	Web app, API, CLI, and MCP	DevTools, CLI, Node module, and Lighthouse CI
Free utility surface	43+ free tools	One open-source audit system

Where the AI Readiness Boundary Sits

Lighthouse's experimental Agentic Browsing category tests whether agents can discover and interact with a page through deterministic technical signals. It does not ask ChatGPT, Perplexity, Gemini, Claude, or Google AI Overview about a brand. It therefore cannot measure mentions, citations, sentiment, competitor presence, or share of voice.

Foglift's Technical Audit adds eight dimensions that help a publisher inspect whether a page gives retrieval systems clear, verifiable material:

Structured data richness: whether machine-readable markup adds useful entity detail.
Heading clarity: whether the page hierarchy exposes its main questions and answers.
FAQ quality: whether common questions receive direct, visible answers.
Entity identity: whether the organization, product, and category are stated consistently.
Content depth: whether the page has enough evidence to answer its target query.
Citation formatting: whether claims include named, dated, reachable sources.
Topical authority: whether supporting content covers the surrounding subject.
AI crawler access: whether relevant search and user-fetch agents can retrieve the page.

These checks measure technical and content readiness. They do not establish a ranking formula or guarantee selection in an AI answer.

Where Lighthouse Goes Deeper

Lighthouse gives developers more detail when the problem is page performance. Its report connects weighted lab metrics to diagnostics and opportunities such as main-thread work, render-blocking resources, image delivery, request cost, and document size. Its CLI, Node module, and Lighthouse CI also fit automated engineering workflows.

Treat a Lighthouse score as one controlled run. Google's own documentation explains why performance scores fluctuate and recommends interpreting performance as a distribution rather than relying on one perfect number.

Recommended Workflow

Run Foglift's Free Technical Audit to establish the broad baseline.
Prioritize severe issues across AI Readiness, SEO, performance, security, and accessibility.
Open Lighthouse when performance needs metric-level diagnosis.
Fix the issue, rerun both tools under comparable conditions, and record the change.
Use AI Visibility monitoring for mention, citation, sentiment, and competitor outcomes.

Frequently Asked Questions

What does Google Lighthouse audit?

Google documents Lighthouse as an open-source automated tool for performance, accessibility, best practices, and SEO audits. It also has an experimental Agentic Browsing category in Chrome 150 or later. That category runs deterministic checks for WebMCP integration, agent-focused accessibility, layout stability, and llms.txt discoverability.

Does Foglift replace Google Lighthouse?

The tools are complementary. Foglift gives a broad Technical Audit across AI Readiness, SEO, performance, security, and accessibility. Lighthouse provides deeper lab-performance diagnostics and developer workflows. Use Foglift to find cross-discipline gaps, then use Lighthouse when a performance issue needs trace-level investigation.

What does Foglift's AI Readiness analysis measure?

Foglift's Technical Audit evaluates eight answer-readiness dimensions: structured data richness, heading clarity, FAQ quality, entity identity, content depth, citation formatting, topical authority, and AI crawler access. These page signals describe technical readiness. They do not prove that an AI engine mentions or cites a brand, which requires prompt-level monitoring.

Does Lighthouse measure AI search visibility?

No. Lighthouse's experimental Agentic Browsing category evaluates technical readiness for machine interaction. It does not query AI engines or measure brand mentions, citations, sentiment, competitors, or prompt-level visibility. Foglift's AI Visibility monitoring measures those outcomes separately from its Technical Audit.

Which audit should I run first?

Start with Foglift when you need a broad, no-install baseline. Follow with Lighthouse when performance needs deeper diagnosis. Foglift's July 14 audit of foglift.io returned 97/100 overall and flagged a 247KB HTML document while its performance subscore was 90, which is a practical example of the handoff between a broad audit and focused performance tooling.

Sources

Google Chrome for Developers, Introduction to Lighthouse. Current overview of audit categories and execution methods; last updated June 2, 2025.
Google Chrome for Developers, Lighthouse performance scoring. Documents metric weights, scoring distributions, and run variability.
Google Chrome for Developers, Lighthouse agentic browsing scoring. Documents the experimental Chrome 150+ category, deterministic audit set, score format, and WebMCP origin-trial requirement; last updated May 5, 2026.
Google Chrome for Developers, Registered WebMCP tools. Documents the informational registered-tools audit; last updated July 1, 2026.
Foglift, Technical Audit of foglift.io, July 14, 2026. Overall 97/100, performance 90, and one large-HTML warning.

Start with the broad baseline

Audit any public URL for AI Readiness, SEO, performance, security, and accessibility.

Run Free Technical Audit

Fundamentals: Learn about GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) (the two frameworks for optimizing your content for AI search engines).