perf(site): defer below-fold homepage demos

[tin-computer]

What changed

• keeps the inline analytics queue available immediately while loading the external analytics library after the initial interactive phase
• loads the 11-family live preview wall only when a visitor nears it instead of putting it on the hero critical path
• gives the homepage a focused 11-demo registry while leaving all 58 catalog demos and documentation links intact
• updates the affected end-to-end checks to scroll the deferred wall into range before testing it

Why

Three fresh production Lighthouse mobile runs measured 3.417s, 3.273s, and 2.952s LCP, for a 3.273s median against the 3.0s target. The family wall sits 7,174px below the initial mobile viewport and does not need to load before the hero.

Measured result

The structural behavior is verified: the family wall is absent at first paint, loads all 11 families when scrolled into range, and /components still exposes all 58 components. The shared test host was saturated during the exact-build Lighthouse sample, producing 5.128s, 5.494s, and 4.246s LCP with 2.6-4.6s total blocking time, so that run cannot support a production target claim. The 3.0s result remains unverified until production deployment can be measured on the same external path.

Checks

• focused ESLint and TypeScript
• production build (275/275 static pages)
• focused production-mode Playwright coverage for the deferred wall and its copy control
• browser verification: deferred wall absent initially, 11 families load on scroll, all 58 /components entries remain linked
• release gate, quick checks, Node 20, four fresh Payload smokes, PR gate, and both Vercel deployments

All automated checks pass. Required non-author maintainer review is the only remaining merge gate.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
payload-components	Ready	Preview, Comment	Jul 16, 2026 2:02pm
payload-components-97bf	Ready	Preview, Comment	Jul 16, 2026 2:02pm