How this site is built
I sell data architecture and measurement. The least I can do is make it possible to check how the thing I publish is built, without taking my word for it.
- 01
Zero third-party requests
No analytics, no pixels, no external web fonts, no heatmaps, no chat widget. Everything this page loads comes from this domain.
Check it yourself
Open developer tools, Network tab, and reload. Sort by domain: there is no domain here other than this one.
- 02
No cookies, so no banner
There is no consent banner because there is nothing to consent to. The only thing stored is your theme preference, in your browser, and it never travels anywhere.
Check it yourself
Developer tools, Application, Cookies. It is empty. In local storage you will find a single key, the theme one.
- 03
Prebuilt HTML, not an application
Every page is generated at publish time and served as a file. There is no application server, no database, no render on request, so there is nothing underneath that can fall over.
Check it yourself
View the page source. The text is in the HTML, not painted in by a script afterward.
- 04
The JavaScript that exists, and why
One file to remember light or dark theme, and one per review tool, which run entirely in your browser and send no answers anywhere. That is all of it.
Check it yourself
A check blocks publishing if any other script shows up, and the same goes for inline styles, which the security policy would reject anyway.
- 05
Contrast calculated, not eyeballed
Every color pair in the system is measured against the AA minimum, in light and dark theme. If a color drops below the threshold, it does not ship.
Check it yourself
Run any page through an accessibility tool. The diagrams also carry a full text description for screen readers.
- 06
Eleven checks before every publish
Spelling, contrast, declared figures, language pairs, heading hierarchy, pages with no inbound links, diagram labels overflowing their boxes, and several more. If one fails, nothing ships.
Check it yourself
Each one came from a real failure that reached production once. The full list is in the repository, with the error each one prevents.
None of this is a technical feat. It is what I ask of the implementations I audit, applied to my own site. A measurement consultant whose site loads three analytics tools and a chat widget is an argument against himself.
Want the same standard in your implementation?
The measurement and tracking review starts here: what gets collected, what gets sent and to whom, and what happens when the user says no.