Google Lighthouse Checker

What is Google Lighthouse Checker?

Google Lighthouse Checker is a powerful SEO and performance analysis tool that runs Google Lighthouse audits on any number of web pages. It automatically extracts critical metrics like Performance, Accessibility, Best Practices, SEO, and PWA scores, providing you with actionable insights to improve your website's ranking and user experience.

Unlike manual audits in DevTools, this Actor allows you to bulk audit hundreds of URLs effectively, emulate different devices (mobile vs. desktop), and integrate the results directly into your CI/CD pipelines or reporting dashboards.

What can this Google Lighthouse Checker do?

• Bulk Lighthouse Audits: Check multiple URLs in a single run.
• Device Emulation: Switch seamlessly between Mobile and Desktop form factors to see how your site performs for different users.
• Comprehensive Metrics: Extract detailed scores for:
  • ⚡ Performance (Core Web Vitals)
  • ♿ Accessibility
  • ✅ Best Practices
  • 🔍 SEO
  • 📱 PWA (Progressive Web App)
• Granular Control: Choose exactly which audit categories to run to save resources.
• Structured JSON Output: Get results in clean JSON format, perfect for automated reporting or data storage.

Why use Google Lighthouse Checker?

Improving your website's Lighthouse scores is crucial for SEO rankings and user retention.

• SEO Agencies: Generate bulk audit reports for clients instantly.
• Developers: Monitor performance regression by integrating audits into your build pipeline.
• E-commerce: Ensure product pages load fast to maximize conversion rates.

"You can't manage what you don't measure. Google Lighthouse Checker makes measurement scalable."

How to use Google Lighthouse Checker

This Actor is designed for simplicity. You don't need to configure complex Puppeteer scripts—just provide the URLs.

Step-by-Step Guide

1. Enter Start URLs: Add the list of web pages you want to audit (e.g., https://apify.com, https://example.com).
2. Select Categories: Choose which audits to perform (Default includes Performance, Accessibility, Best Practices, and SEO).
3. Choose Form Factor: Select mobile (default) or desktop emulation.
4. Run: Click run and wait for the audits to complete.
5. Download: Export your results in JSON, CSV, or Excel formats from the Output tab.

Input Configuration

The input is simple and flexible. All fields are technically optional as they have sensible defaults (or simply do nothing if empty), but you usually want to provide at least one URL.

Field	Type	Description	Default
startUrls	Array	The list of URLs to audit.	[]
onlyCategories	Array	Specific categories to check.	['performance', 'accessibility', 'best-practices', 'seo']
formFactor	String	Device emulation mode.	mobile

Example Input

{
  "startUrls": [
    { "url": "https://apify.com" },
    { "url": "https://www.google.com" }
  ],
  "onlyCategories": ["performance", "seo"],
  "formFactor": "desktop"
}

Output Data

The results are stored in the Apify Dataset. Each item represents one audited URL.

Example Output

{
  "url": "https://apify.com",
  "finalUrl": "https://apify.com/",
  "performance": 0.92,
  "accessibility": 1,
  "bestPractices": 0.95,
  "seo": 1,
  "formFactor": "desktop",
  "fullReport": { ... }
}

FAQ

Is everything optional in the input?

Yes, from a schema perspective, all fields (startUrls, onlyCategories, formFactor) are optional.

• If you don't provide startUrls, the actor will simply finish without auditing anything.
• If you don't provide others, they will use their default values (e.g., mobile for form factor and all major categories for auditing).

How much memory does it need?

Lighthouse is resource-intensive. This Actor uses a headless Chrome instance, so we recommend allocating at least 1024 MB (1 GB) of memory for reliable performance, especially for complex websites.

Can I integrate this with GitHub Actions?

Absolutely. You can use the Apify API to trigger this actor from your CI/CD pipeline and fail the build if scores drop below a certain threshold.

Support

If you find any bugs or have feature requests, please check the Issues tab or create a new issue.