Blog › Tools & measurement

PageWeight vs Lighthouse CI: which should you use?

Lighthouse CI is Google’s open-source tool for running performance audits automatically on every code change, built for developers wiring it into a CI/CD pipeline. PageWeight is a hosted, no-setup scanner for anyone who wants a report and a tracked score over time without touching a config file. They solve overlapping problems for different audiences.

What is Lighthouse CI?

Lighthouse CI (@lhci/cli) is an open-source npm package that runs Lighthouse audits — the same audit engine behind PageSpeed Insights and Chrome DevTools — as part of a CI pipeline like GitHub Actions or GitLab CI, typically on every commit or pull request. It can fail a build automatically when an assertion fails, such as a score dropping below a budget you set. To keep results over time and compare runs, you point it at an LHCI server, an open-source Node server you deploy and run yourself.

What is PageWeight?

PageWeight is a hosted scanner powered by the Google PageSpeed Insights API — no install, no config file, no CI pipeline. Enter a URL and get a lab report plus real-user field data when it’s available. With a free account you can track up to 3 pages, keep their score history, and get an email alert if a tracked page’s score drops. Reports can be shared via a link without the recipient needing an account.

Who is each one actually for?

  • Lighthouse CI — developers who want automated regression detection wired directly into a deploy pipeline, catching a performance-hurting change before it ships. Requires engineering setup and CI access.
  • PageWeight — anyone checking a live site’s performance, tracking it over time, or sharing a report with a client or stakeholder, with no engineering setup required. Works on sites you don’t have code or CI access to at all — useful for agencies auditing client sites, marketers, and freelancers.

Can they be used together?

Yes — they aren’t really solving the same job. Lighthouse CI catches a regression before it reaches production, as part of your engineering workflow. PageWeight monitors what’s actually live right now and reports on it in plain language, for you and for non-technical stakeholders, with no pipeline to build or maintain. It also catches changes that never go through your pipeline at all, like a script added by a tag manager or a marketing plugin.

How do they show what changed between runs?

An LHCI server can show a detailed diff between any two runs. PageWeight does a similar comparison on the live page: its Recent changes panel lists files that were added, removed, or changed size, and requests that started failing. It only lists a change once it has held for three checks in a row, so rotating images and ads don’t flood the list.

What does it take to run a Lighthouse CI server?

The LHCI server stores historical run data and powers those comparisons — powerful, but it’s infrastructure you deploy and maintain yourself, on a cloud host or your own machine. Without it, Lighthouse CI’s free temporary public storage keeps individual reports, but no history or comparisons. PageWeight’s monitoring — score-drop alerts, saved history, Recent changes — needs no server of your own.

Which should you set up first?

If you already have a dev team shipping through CI, adding Lighthouse CI is a small addition. If you want visibility into your live site’s real-world performance today, without filing an engineering ticket, start with a PageWeight scan — and see how PageWeight stacks up against other hosted tools in our PageWeight vs GTmetrix vs DebugBear comparison.