U6: Lighthouse performance in CI alleen waarschuwen (Pi te traag), eigenaarsbesluit vastgelegd

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-14 14:24:26 +01:00
co-authored by Claude Sonnet 5.5
parent 9ac852f2a2
commit 1a02824338
4 changed files with 14 additions and 5 deletions
@@ -46,7 +46,7 @@
- **NFR-7 Maintainability**: theme tokens as CSS variables per variant × mode; Tailwind semantic color names remain; content stays in `content.ts`/API.
- **NFR-8 Compatibility**: hash routing and static hosting remain; the existing Sentry/Umami integration and the CI/CD pipeline keep working.
- **NFR-9 SEO and performance (U6)**: static text is prerendered into the HTML at build; dynamic parts (packages, later gallery) are injected by the CMS host from current data, fresh within minutes; canonical, Open Graph/Twitter, favicon set, JSON-LD (organisation and offers), `robots.txt` and `sitemap.xml`; test hosts serve `Disallow: /` and `X-Robots-Tag: noindex` from the host, not the bundle; Lighthouse in the pipeline on mobile and desktop is a hard gate of at least 0.9 per category (exceptions only with a recorded owner decision); no new third-party scripts.
- **NFR-9 SEO and performance (U6)**: static text is prerendered into the HTML at build; dynamic parts (packages, later gallery) are injected by the CMS host from current data, fresh within minutes; canonical, Open Graph/Twitter, favicon set, JSON-LD (organisation and offers), `robots.txt` and `sitemap.xml`; test hosts serve `Disallow: /` and `X-Robots-Tag: noindex` from the host, not the bundle; Lighthouse in the pipeline on mobile and desktop is a hard gate of at least 0.9 per category (exceptions only with a recorded owner decision; **owner decision 2026-11-14**: on the Pi CI runner the performance category is report-only, because the measurement is too slow there (0.54 vs 0.90 locally); accessibility, best-practices and SEO stay hard gates, and performance stays a hard gate when run locally); no new third-party scripts.
- **NFR-10 CMS content is live (owner principle, 2026-11-12)**: everything that comes from the CMS (packages, banner, later the gallery) is visible on the website immediately after a change in the CMS; a rebuild exists only for SEO (HTML and structured data that crawlers read). Pattern for all sites: baked-in or host-injected HTML for crawlers plus a client-side refresh from the API on load; on failure the baked version stays (no empty prices). Applies to SLP Software, Andrea Slop Fotografie and future sites.