The baseline is a starting point
On August 24, 2026, the public homepage returned a 37 performance score, 83 accessibility score, 92 SEO score and 11.4-second LCP in a Lighthouse mobile-profile run. Those figures describe one controlled lab run—not every visitor and not the finished optimization work.
Prioritize the critical path
The report also showed 850 ms of total blocking time and an estimated 178 KiB of unused JavaScript. That points to a practical order: identify the LCP resource, simplify its dependency chain, cut main-thread work, then retest before polishing smaller opportunities.
- Confirm the actual LCP element
- Trace when its request begins
- Remove or defer non-critical JavaScript
- Repair named accessibility failures
- Repeat the same profile for comparison
Publish an after only when it exists
The credible case study is the one that preserves the baseline and waits for a reproducible after-audit. Until then, this remains an optimization-in-progress—not a success story with an invented ending.