Full pnpm check at ae769cb passed and 24 browser checks against the
production build passed. Adds the build and test instructions and
summary, marks the feature complete and logs the session in the audit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
Performance Test Instructions — over-mij-page
A static site, so there is no load testing. Performance means page-load performance, measured with Lighthouse CI on the production build.
cd web
pnpm build
pnpm lighthouse # mobile (lighthouserc.cjs) then desktop (lighthouserc.desktop.cjs)
Budgets
- Performance: homepage on mobile ≥ 0.8 (temporary, NFR-P-01). Since this feature, that exception applies to
/only; before, it applied to every indexed page. Every other page,/over-mijincluded, needs ≥ 0.9 on mobile, and every page needs ≥ 0.9 on desktop. - Accessibility and best practices: 1.0 on every page
- SEO: the basic audits everywhere;
is-crawlableonly on indexed pages (/and/over-mij)
Measuring reliably
See homepage-sections performance-test-instructions.md: measure the production build on a quiet machine and check that environment.benchmarkIndex is around 3500–4200. On the Pi in CI, performance is reported but does not block.
Known: mobile LCP of /over-mij
The portrait is the largest contentful paint, at 3.2 s with mobile throttling. About 2.1 s of that passes before the request can start, because the page is rendered by JavaScript (the placeholder pages have the same first paint). Another 0.5 s comes from the design's fade-in (Reveal). The portrait already loads at once with fetchpriority="high". Prerendering (NFR-P-01) is the structural fix.