Skip to content

Lighthouse scores on the PR, not buried in the logs

A Lighthouse score in CI logs tells you it dropped. The HTML report tells you why — filmstrip, opportunities, diagnostics. That report is a single self-contained file, and it deserves a URL on every PR.

Drop your Lighthouse report here — get a live link

free, no account, live for 7 days.

The artifact dead-end

Most setups print the scores to the job log and call it a day. When performance regresses, someone has to re-run Lighthouse locally to see the actual audit — the context that explains the number never leaves the runner.

The alternative is uploading the report as an artifact, which puts the full breakdown behind the usual download-and-extract ritual. Reviewers check the number, shrug, and move on.

Two lines to a live link

Build your output like you already do, then hand the folder to the action:

Audit the deployed preview

npx lighthouse <url> --output=html --output-path=./lighthouse.html --chrome-flags="--headless --no-sandbox"

.github/workflows/ci.yml

- uses: bitgate/ship-page-action@v1
  if: always()
  with:
    path: lighthouse.html

path: lighthouse.html deploys exactly what the tool wrote — no detection to configure. The link goes in the job summary — add comment: true and it lands on the pull request too.

What you get

  • The full interactive report renders — scores, filmstrip, every audit — because the self-contained HTML is served untouched
  • Audit the actual deployed preview: deploy your build, run Lighthouse against that URL, publish the report — all in one job
  • name: pr-${{ github.event.number }}-lighthouse keeps a stable per-PR report URL that every push redeploys in place

Questions

What should I point Lighthouse at?

The preview you just deployed — the action's url output. That way the report measures exactly what reviewers will click, not localhost. Full walkthrough in /docs/ci-reports.

Does this work with Lighthouse CI (lhci)?

Yes — lhci's GitHub App posts checks, but its HTML reports still need somewhere to live. Deploy the .lighthouseci output directory the same way and link it from your workflow summary.

How long do report links live?

Anonymous drops expire after 7 days — fine for PR review. On a paid plan you control ttl, or keep a permanent named drop for your main-branch scores.

Try it on your next run

Anonymous deploys need no account and no key — paste the step, get a link. When you want stable URLs that redeploy in place, an API key and a name are all it takes.

Get the GitHub ActionAll CI recipes

Need to share the report with someone outside GitHub? How to share a GitHub Actions artifact without a login.