How can I use Unlighthouse to audit several templates on one site?
harlan-zw/unlighthouse
Unlighthouse runs Google Lighthouse against a set of site URLs and collects the audits in one report, so a team can compare findings across page templates.
Public GitHub facts reviewed Nov 14, 2026. Independent editorial profile; not a sponsored entry.
How is the score calculated?
Calculated on 14.11.2026. Missing public information receives no points. The index does not establish code quality, security, fitness, or future visibility.
What can unlighthouse help with?
Build a regression check for a storefront
Include a product detail, a collection page, a landing page, and a support article. Keep the same routes and device settings when comparing weekly runs.
Triage a backlog by template owner
Group recurring findings by the layout or component that owns them. Confirm a representative failure in an individual audit before assigning work.
Questions people ask before using unlighthouse
How can I use Unlighthouse to audit several templates on one site?
Give Unlighthouse a fixed list that represents the templates your team owns. Include multiple pages for important layouts and a simple control page. Use the combined report to identify repeat findings, then reproduce each issue in a single page audit.
What should a small team include in its first Unlighthouse scan?
Start with the homepage, a high-traffic landing page, a listing, and two detail pages. Check the installed release’s Node and browser requirements. The stable CLI accepts the site with --site and a short comma-separated path list with --urls. Record the exact set for the next run.
How can I measure whether a release improved page speed?
Repeat baseline and release checks with the same URL, viewport, throttling, and Chromium version. Compare metrics and the reported LCP element at the page level. Several runs help distinguish a consistent change from noise, while field metrics show what real visitors experienced.
How can I include important campaign pages the crawler never finds?
Add the campaign paths explicitly or supply the relevant sitemap. Compare the report’s discovered URLs with your launch checklist. Keep previews and expired campaign URLs in a separate group when those pages have different access or measurement needs.
How do I handle the same collection page with thousands of parameter combinations?
Choose representative canonical pages first, then add deliberately selected filtered examples to a separate run. Bound the sample and record exclusion rules. Otherwise, repeated variations can hide the templates that matter and increase run time.
Can a passing audit serve as the accessibility sign-off for a checkout?
Use the automated accessibility findings as a starting point. Check focus order, keyboard access, accessible names, input errors, and live updates while completing checkout manually. Automated checks of an individual rendered state cover only part of the experience.
How can I make a useful performance check in CI without blocking deploys on noise?
Publish the initial results as a report and use representative routes and comparable machines. Once you understand normal variation, set narrow thresholds on metrics your team can reproduce. Keep a fast path to the individual reports when a threshold fails.
What is a reasonable way to share results from an internal preview?
Keep the first report local and review what it captures. Remove sensitive URLs, content, and screenshots before sharing an artifact. Use a test environment and authorized access when checking pages behind authentication.
What does the Unlighthouse license require for redistribution?
The repository ships an MIT license in LICENSE.md. Include its copyright and permission notice when distributing the software or substantial portions. Review the separate terms for dependencies and any external content included in a report.
Where do Lighthouse and Unlighthouse fit in my debugging workflow?
Use the multi-page report to spot clusters by template. Switch to Lighthouse for a single failing page and use browser tools to isolate the asset, script, or render step involved. Use field measurement when you need population-level evidence.
What to check before adoption
- Primary language
- JavaScript
- GitHub license field
- MIT
- License according to repository file
- MIT · LICENSE ↗
- Stars / forks in this snapshot
- 4,949 / 182
- Last code push
- 27.10.2026
- Self-hostable
- Potentially, verify operating requirements
The result covers the URLs that were discovered or supplied and the conditions of the lab run. Use field data to assess the production experience and manual testing to cover the complete customer journey.
Comparison and original sources
Compared with lighthouse Use Unlighthouse to find patterns across your storefront templates, then investigate one affected page with Lighthouse. Start with Lighthouse alone if you only have a handful of URLs to diagnose.
Documentation and repository data
Compare related projects
lighthouse
GoogleChrome/lighthouse
An automated audit tool for web performance, accessibility, SEO checks, and best practices.
GitHub snapshot 11.11.2026 · Score method on profile
A visual low-code environment for event-driven automations and integrations.
GitHub snapshot 11.11.2026 · Score method on profile
wordpress-develop
WordPress/wordpress-develop
A GitHub mirror of the WordPress core development project.
GitHub snapshot 11.11.2026 · Score method on profile
Back to Open Source Radar
Explore more projects by job, technology, and license.