Files
AndreaSlopFotografie/aidlc-docs/features/contact-page/construction/build-and-test/performance-test-instructions.md
T
SluijsensandClaude Opus 5.5 65c007f8c2
Continuous Integration / check (pull_request) Successful in 12m4s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 13m38s
Continuous Integration / deploy-production (pull_request) Skipped
Records Build and Test of the Contact page
Build, unit, integration and performance test instructions and the
summary, the corrected scroll rule and the review on test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 20:14:28 +01:00

1.1 KiB
Raw Blame History

Performance Test Instructions — contact-page

cd web
pnpm build
pnpm lighthouse       # mobile (lighthouserc.cjs), then desktop (lighthouserc.desktop.cjs)

Announce "claim 4173" to parallel feature sessions first and "4173 free" afterwards; avoid other heavy work on the machine while Lighthouse runs (it measures CPU).

Budgets (mobile performance)

Page Budget Measured (2026-10-25)
/ 0.8 0.78–0.80 — pre-existing (identical on the unit 2 build, 3 runs each); owner: handle separately
/contact 0.9 0.88 / 0.90 / 0.88 — owner chose to keep 0.9
/over-mij, /soorten-fotoshoots 0.85 0.85–0.88

The contact page shares the cause of the photo pages: the page text appears only after the main bundle and the route chunk have run (client rendering), so LCP lands around 3.1–3.2 s in Lighthouse's simulation. Prerendering is the structural fix (NFR-P-01). In CI, performance is report-only (D6), so these do not block a merge; locally pnpm check fails on them.

Desktop: every page ≥ 0.99; /contact 0.99 / 1 / 1 / 1. Accessibility, best practices and SEO (indexed pages) are 1.0 everywhere.