Makes Lighthouse performance report-only in CI
Continuous Integration / check (pull_request) Successful in 5m56s
Continuous Integration / lighthouse (pull_request) Successful in 12m13s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / deploy-production (pull_request) Skipped

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:
2026-10-19 01:23:06 +02:00
co-authored by Claude Opus 5.5
parent 295adc2a9c
commit 23f7020ff5
11 changed files with 77 additions and 9 deletions
@@ -140,11 +140,23 @@ jobs:
# --no-sandbox: als root weigert Chrome anders te starten
# --disable-dev-shm-usage: /dev/shm is in een container maar 64 MB; met
# de grote hero-foto's crasht het tabblad anders (TARGET_CRASHED)
# Performance op de Pi is niet representatief (CPU-vertraging bovenop een
# trage machine): hier alleen melden, blokkerend in `pnpm check` op een pc.
# Toegankelijkheid, Best Practices en SEO blokkeren wel.
- name: Lighthouse
env:
LIGHTHOUSE_CHROME_FLAGS: '--no-sandbox --headless=new --disable-dev-shm-usage'
LIGHTHOUSE_PERFORMANCE: warn
run: pnpm lighthouse
- name: Upload Lighthouse-rapporten
if: always()
uses: actions/upload-artifact@v3
with:
name: lighthouse-reports
path: web/lighthouse-reports/
retention-days: 14
deploy-test:
needs: [check, lighthouse]
if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master')