Aligns the page edges with the design and fixes the Contact anchor offset
Continuous Integration / check (pull_request) Successful in 9m57s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 3m46s
Continuous Integration / deploy-production (pull_request) Skipped

The content column now uses the design's gutter as side padding instead
of Chakra's 16/24/32px. The Lifestyle fotografie row on phones bled out by
the gutter, so the page was 4px too wide and Chrome zoomed out slightly.
The header drops its extra padding and the to-top button follows the
gutter, so logo, hero controls and content share one edge. Anchored
sections now scroll to the height of the shrunken header, so Contact
lands right below it instead of 24px lower.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-22 01:46:08 +02:00
co-authored by Claude Opus 5.5
parent 1905295a21
commit 8d8cbdb72c
12 changed files with 191 additions and 10 deletions
@@ -0,0 +1,22 @@
# Performance Test Instructions — homepage-sections
A static site: there is no load or throughput testing. Performance means page-load performance, measured with Lighthouse CI.
```bash
cd web
pnpm build
pnpm lighthouse # mobile (lighthouserc.cjs) then desktop (lighthouserc.desktop.cjs)
```
## Budgets
- **Performance**:
- homepage on mobile ≥ 0.8. This is a temporary budget until responsive images and prerendering arrive (NFR-P-01).
- every other page on mobile ≥ 0.9.
- every page on desktop ≥ 0.9.
- **Accessibility and best practices**: 1.0 on every page
- **SEO**: the basic audits on every page; `is-crawlable` only on indexed pages
## Measuring reliably
- Measure the **production build**. The Vite dev server (`pnpm dev`) serves 137 unbundled modules and scores ~0.55 on desktop and ~0.36 on mobile, which says nothing about the site.
- Lighthouse throttles the CPU relative to the machine's own speed. A busy machine (a game, a dev server rebuilding) scatters the homepage mobile score between 0.68 and 0.84. Compare `environment.benchmarkIndex` in the report: when it is far below ~3500–4200, rerun on a quiet machine.
- In CI the Raspberry Pi scores 30–40 points lower, so performance is reported there and does not block (`LIGHTHOUSE_PERFORMANCE=warn`).