Add Lighthouse CI workflow to audit the page (closes #8) - #11
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a GitHub Actions workflow that audits the page with Lighthouse CI on every push to
masterand on PRs targeting it (closes #8). The page is static and dependency-free, so scores should stay near-perfect — any drop is a clear regression signal.What it does
.github/workflows/lighthouse.yml): runstreosh/lighthouse-ci-action@v12against the repo root served as a static site (no deploy wait). Least-privilegepermissions: contents: read,concurrencycancels superseded runs, reports uploaded as workflow artifacts.lighthouserc.json): hybrid gate — accessibility / SEO / best-practices hard-fail below1.0; performance is warn-only (timing on shared CI runners fluctuates and would otherwise cause false failures).Notes
lighthouserc.jsonforcesprefers-reduced-motionviachromeFlags. The page's entrance animation starts content atopacity: 0, which never advances in headless Lighthouse and yieldsNO_FCP; reduced motion makes content statically visible so the audit is deterministic. The gated categories are motion-independent.assertpasses (exit 0).🤖 Generated with Claude Code