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 !!
Views
Replies
Total Likes
Hi @tb1687196,
Here’s how you can approach it:
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
npm install -g lighthouse
https://your-site/page1.html
https://your-site/page2.html
...
#!/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
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
Install: npm install -g @lhci/cli
Setup lighthouserc.js
with multiple URLs
Can generate reports and upload to a custom dashboard or GitHub Pages
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) –
Views
Replies
Total Likes
You do not need all 4 tools to implement the CLI-based, deployment-independent Lighthouse reporting.
Here’s what’s actually required and optional:
Lighthouse CLI (Node.js) – Yes, required
This is the main tool that audits pages. It’s open source and can be installed via:
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.
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.
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.
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies