How this page is measured

Every figure below was measured on something that exists, by this site's own tools, and printed by the build. Nothing on this page is typed by hand.

The home page at fortoxa.com is rendered in headless Chrome at 1440×900 and 360×800 (DPR 1, loaded from file:// so that a network request cannot hide behind a local one), the pixels of the saved screenshots are counted, and the result is written to src/facts.json. The build reads that file and injects the numbers into this page: if a figure cannot be read, the build fails rather than print a placeholder. tools/verify.py then asserts that the numbers printed here are the numbers in that file, so the page and the measurement cannot drift apart.

The home page, measured

The floors the home page is held to: dominant colour at or under 55% of pixels, mean chroma at or over 6/255, zero external requests, zero console errors, and the page as one file.

The brand system, measured elsewhere

A second set of colour figures belongs to a different artefact: the FORTOXA brand system v2, measured on the brand workspace's own styleguide page from its saved PNG pixels. It is dominant colour 23.72% at 1440×900, mean chroma 35.09/255, 0 external requests, over 104 token properties in 15 groups, 7 mark lockups, a 26-symbol icon set on one 24×24 grid and 9 OFL-1.1 faces.

The two sets are not comparable and are not meant to be: the first measures the home page, the second measures the styleguide that defines the tokens the home page uses. They are printed together here only so both are inspectable in one place.

What is not measured

Nothing on this site measures a visitor. There is no analytics package, no cookie, no tracker and no third-party script: the only request the home page can make is the one you send yourself through the enquiry form, which is why the measured render still counts zero external requests.