Makes Lighthouse performance report-only in CI
Lighthouse slows the CPU 4x relative to the measuring machine, so the Raspberry Pi runner scores performance 30-40 points lower than a PC for the same build. In CI the performance assertions now only warn; accessibility, best practices and SEO still block, and performance still blocks in `pnpm check` on a PC. Mobile and desktop reports go to separate folders and are attached to every run as an artifact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
+2
-2
@@ -16,8 +16,8 @@ pnpm lighthouse # mobile (lighthouserc.cjs), then desktop (lighthouserc.deskto
|
||||
```
|
||||
- Lighthouse CI starts `pnpm preview` itself (port 4173, real security headers).
|
||||
- It measures all six routes plus `/bestaat-niet` (404) once per form factor.
|
||||
- It fails if any assertion fails.
|
||||
- Reports are written to `.lighthouseci/` (git-ignored). Open the `.html` files for details.
|
||||
- It fails if any assertion fails. Exception: in CI the workflow sets `LIGHTHOUSE_PERFORMANCE=warn`, which makes Performance report-only, because the Raspberry Pi runner gives scores 30-40 points lower than a PC for the same build. Locally, Performance blocks.
|
||||
- Reports are written to `lighthouse-reports/mobile` and `lighthouse-reports/desktop` (git-ignored). Open the `.html` files for details. In CI they are attached to the run as the `lighthouse-reports` artifact.
|
||||
- Requires a local Chrome.
|
||||
|
||||
Manual measurement in a browser: `pnpm build && pnpm preview`, then open `http://localhost:4173` in a **private window** (extensions and Brave Shields skew results) and run Lighthouse from DevTools.
|
||||
|
||||
Reference in New Issue
Block a user