What we measure
We treat measurement as a way to answer a defined product or service question: can visitors find a product, does a page load reliably, or is a workflow confusing? We do not treat a dashboard score as a complete description of every visitor’s experience.
This public site is designed to work without a mandatory analytics account or a tracking cookie banner pretending that tracking is present when it is not.
- We start with the question before choosing a measurement tool.
- We separate observed results from assumptions and estimates.
Our privacy position
We prefer the smallest amount of data that answers the question. Where a future product or campaign adds analytics, we document the tool, purpose, data collected, access, and retention in the relevant notice.
We do not add a tracking script solely because it is easy to install. A measurement needs a clear purpose and a proportionate design.
- We review whether an event can be counted without identifying a person.
- We avoid putting personal data, messages, tokens, or secrets into analytics fields.
How we interpret results
Performance and search reports change with network quality, device capability, location, sample size, browser cache, and the time of the test. We use repeatable conditions when comparing an improvement.
We do not publish speed, audience, conversion, or availability claims without evidence and a method that explains what was measured.
- We compare like-for-like runs and record major test conditions.
- We use findings to investigate a specific problem rather than to justify a predetermined decision.
Review and limits
A tool can miss users or distort behaviour. We combine measurements with direct functional checks and feedback, and we remove measurement that no longer supports a valid decision.
Our current contact form prepares an email in the visitor’s email application; it is not a server-side analytics or ticket endpoint.
- We review privacy notices whenever a data flow changes.
- We label estimates and unverified results honestly.
Our measurement decision
We prefer measurements that answer a real product question with minimal collection. We document the purpose and retention before adding any new measurement tool.