Colophon

This build

Reading the build report...

Demo sites

Asking the demos how they are...

Real visitors, last 28 days

Asking for the field data...

Good means LCP under 2.5 s, INP under 200 ms, CLS under 0.1, TTFB under 0.8 s. A figure appears once a page has ten or more samples.

Your visit

LCP

waiting (INP needs you to click something, CLS and LCP settle when you leave)

INP

waiting (INP needs you to click something, CLS and LCP settle when you leave)

CLS

waiting (INP needs you to click something, CLS and LCP settle when you leave)

TTFB

waiting (INP needs you to click something, CLS and LCP settle when you leave)

What is collected: for about one visit in four, each of those four numbers is sent once, with the page you landed on and how you arrived (a normal visit, a reload, and so on). That is all. No cookie, no identifier, no browser details, and your IP address is not stored. If your browser sends Do Not Track or Global Privacy Control, nothing is sent at all.

How it is built

• Pages. React and Vite, with every page rendered to plain HTML at build time, so it shows before any script runs. The pages then come alive in place.
• Look. One stylesheet with a small set of shared controls, Tailwind for layout, self-hosted Space Grotesk, Inter and Space Mono, and one accent colour used only for live data and go states.
• Motion. GSAP is the only animation library. Everything that moves stops under the reduced-motion setting, apart from things you drag yourself.
• 3D. three.js draws the hero and the globe. It is loaded after the page has painted, and only where it is used.
• Hosting. Netlify serves static files. Its functions do only three jobs: Formula 1 session data (cached for good once a session is over), these vitals, and the contact forms.
• Data. The Pit Wall's latest session and the calendar are fetched at build time and refreshed by a nightly rebuild. If the fetch fails, the last good copy stays live.

Data refreshed: Formula 1 calendar 0 min ago.