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 tracking or non-essential storage
Only your chosen theme is stored, in your browser, without being sent to the server. That preference is not used for tracking or advertising. No storage requiring a consent banner is used.
Check it yourself
Developer tools, Application: there are no cookies. After choosing a theme, localStorage contains the "adria-theme" key. You can delete it there.
- 03
Prebuilt HTML, not an application
Every page is generated at publish time and served as a file. Serving it requires no application server or database. That reduces dependencies, although hosting and DNS can still fail.
Check it yourself
View the page source. The text is in the HTML, not painted in by a script afterwards.
- 04
The JavaScript that exists, and why
Scripts handle the theme, review tools and simulators. The simulators share animations and, where applicable, scenario guidance. Everything runs in your browser without sending your choices to the server.
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 colour pair in the system is measured against the AA minimum, in light and dark theme. If a colour 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
You can check languages, headings, links and contrast on the published pages. That lets you inspect the result, not the execution of the internal checks.
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.