Proof of Work
Performance Log
We don't just claim the scores — we log them. Every entry below is a real Lighthouse run, what changed, and why. Keeping a 100 score takes ongoing upkeep — for most sites, a score in the 90s is more than enough.
July 1, 2026
The Problem: Low-Contrast Text on the Blog Index
Adding a read-time label to each blog post row dropped Accessibility to 94 on both mobile and desktop. The muted gray used for that text (#8a8880) scored roughly 3.1:1 against the paper background — below the 4.5:1 minimum WCAG requires for small text. Lighthouse flagged the same span six times, once per post row.
(Mobile)
(Desktop)
The Solution
One value needed to change:
- Darkened the read-time text from #8a8880 to #6b6a63.
Still visually secondary to the date and category, but now clears 4.5:1 against the background. One color value changed, no layout impact.
June 31, 2026
The Problem: Google Analytics (GA4) Flagged as Unused JavaScript
Google Analytics (GA4) loads a script that Lighthouse flags as 67 KiB of unused JavaScript. Most of that code doesn't run during a page's first few seconds — it's there for later tracking events, not initial render. That's a common tradeoff: real analytics data costs you page-speed points.
(Mobile)
(Desktop)
The Solution
Three options were on the table:
- Leave it alone and accept the flag.
- Drop GA4 for a lighter analytics tool.
- Delay GA4 until the visitor actually interacts with the page.
We went with option 3 — GA4 now loads only after a scroll, click, or mouse move, with a timeout fallback so visitors who bounce without interacting still get counted. Analytics stays accurate, but the script no longer competes with the content for load time.