Requirements, execution plan, functional design, code summaries, build and test results and the audit log; the reverse-engineering notes and the feature registry are updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Performance Test Instructions
Purpose
NFR-TR-02: the Lighthouse targets in web/lighthouserc.cjs (mobile) and lighthouserc.desktop.cjs do not go down because of this feature. The carousel stays lazy-loaded away from the hero, and the photos are the same files.
Run
cd web
pnpm build
pnpm lighthouse # lhci autorun for mobile, then for desktop (&&)
- Needs port 4173 free and no heavy work in parallel: it skews the score. In the parallel-sessions agreement, ask the other sessions first.
- Locally the performance assertion blocks; in CI it only warns (
LIGHTHOUSE_PERFORMANCE=warn), because the Raspberry Pi runner scores 30 to 40 points lower.numberOfRunsis 1 on purpose, so a page that sits exactly on its floor can fail by chance. - Accessibility, best practices and SEO must be 1 on every page; those block everywhere.
A/B check against master (when one page sits on its floor)
cd web
pnpm exec lhci collect --collect.url=http://localhost:4173/ --collect.numberOfRuns=5
Run it once with the branch's dist and once with master's dist (build master in the main checkout), then compare the scores in .lighthouseci/lhr-*.json. Do not run the two at the same time.
Result of 2026-11-06
See build-and-test-summary.md: the homepage is on its floor of 0.85 and scores 0.84 on both the branch and master on this machine.