Lighthouse report customization idependent of deployment | Adobe Higher Education
Skip to main content
tb1687196
tb1687196
Level 2
June 20, 2025
Resuelto

Lighthouse report customization idependent of deployment

  • June 20, 2025
  • 1 respuesta
  • 432 visualizaciones

Hi Experts,

Could you kindly suggest if deployment independent for more number of pages ( more than 25 pages) same kind of lighthouse report can be generated? It will not be dependent upon AEMaaCS pipeline or deployment.

If yes, kindly share in little details.

Thanks in advance !!

Este tema ha sido cerrado para respuestas.
Mejor respuesta de SantoshSai

@tb1687196,

You do not need all 4 tools to implement the CLI-based, deployment-independent Lighthouse reporting.

Here’s what’s actually required and optional:

Required (Open Source)

  1. Lighthouse CLI (Node.js) – Yes, required
    This is the main tool that audits pages. It’s open source and can be installed via:

    npm install -g lighthouse
Optional Tools (depending on your needs)

  1. Puppeteer + Lighthouse – Not required for basic CLI
    Use this only if you need more control (e.g., login automation, custom headers, JS interactions). Otherwise, Lighthouse CLI with --chrome-flags="--headless" is enough.

  2. Google PageSpeed Insights API – Not required
    This is an alternative, not a dependency. It uses Lighthouse under the hood, but is rate-limited and better suited for occasional or remote audits.

  3. Lighthouse CI (LHCI) – Not required
    Optional if you want centralized tracking, history, or automated runs in CI pipelines. Adds nice dashboards, but not needed for CLI-based reporting.

1 respuesta

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
June 23, 2025

Hi @tb1687196,

Here’s how you can approach it:

Tools/Tech Stack Options

  • Lighthouse CLI (Node.js)

  • Puppeteer + Lighthouse for headless Chrome runs

  • Google PageSpeed Insights API (rate-limited)

  • Lighthouse CI (LHCI) – optional, but useful for tracking history

How to Set It Up (CLI Approach – Deployment Independent)
1. Install Node.js & Lighthouse
npm install -g lighthouse
2. Create a URL List (e.g., urls.txt)
https://your-site/page1.html
https://your-site/page2.html
...
3. Bash Script to Loop Through URLs

#!/bin/bash
mkdir -p lighthouse-reports

while read url; do
  echo "Auditing $url"
  filename=$(echo $url | sed 's|https\?://||' | tr '/:' '_')
  lighthouse "$url" --output html --output-path "./lighthouse-reports/${filename}.html" --chrome-flags="--headless"
done < urls.txt
Benefits

  • No dependency on AEM pipeline or code changes

  • You can run it locally or on any server/VM

  • Supports batch processing

  • Output can be HTML or JSON

  • Easy to customize scoring categories

Alternative: Use Lighthouse CI (Optional for Centralized Reporting)

  • Install: npm install -g @lhci/cli

  • Setup lighthouserc.js with multiple URLs

  • Can generate reports and upload to a custom dashboard or GitHub Pages

Santosh Sai
    tb1687196
    tb1687196Autor
    Level 2
    June 29, 2025

    Many thanks @santoshsai 

    for the details. So, to implement the CLI approach you described, need all 4 below? And these are open source?

    • Lighthouse CLI (Node.js)

    • Puppeteer + Lighthouse 

    • Google PageSpeed Insights API 

    • Lighthouse CI (LHCI) – 

    SantoshSai
    Community Advisor
    SantoshSaiCommunity AdvisorRespuesta
    Community Advisor
    July 4, 2025

    @tb1687196,

    You do not need all 4 tools to implement the CLI-based, deployment-independent Lighthouse reporting.

    Here’s what’s actually required and optional:

    Required (Open Source)

    1. Lighthouse CLI (Node.js) – Yes, required
      This is the main tool that audits pages. It’s open source and can be installed via:

      npm install -g lighthouse
    Optional Tools (depending on your needs)

    1. Puppeteer + Lighthouse – Not required for basic CLI
      Use this only if you need more control (e.g., login automation, custom headers, JS interactions). Otherwise, Lighthouse CLI with --chrome-flags="--headless" is enough.

    2. Google PageSpeed Insights API – Not required
      This is an alternative, not a dependency. It uses Lighthouse under the hood, but is rate-limited and better suited for occasional or remote audits.

    3. Lighthouse CI (LHCI) – Not required
      Optional if you want centralized tracking, history, or automated runs in CI pipelines. Adds nice dashboards, but not needed for CLI-based reporting.

    Santosh Sai
      Términos y condicionesAccessibility statement

      Loading footer...