Statement
Sustainability Statement
This statement records what sustainability means for our own website: the decisions we make, the things we measure, the limits of those measurements and the improvements still to be made. It is a working record, not a badge.
Last updated:
Scope
This statement covers the public Hummingbird website: its content, design and technology, the hosting and third-party services it uses, the measurement of representative pages and how the site is maintained. It does not automatically cover client websites or external platforms reached through links.
Our priorities
- Make the site useful. Content or functionality that does not help people understand, examine or contact us should be questioned.
- Make it accessible. We design toward WCAG 2.2 AA and never remove essential access to reduce a carbon estimate.
- Keep it light. Limited page weight, media, fonts, scripts and requests – while retaining the communication value of the design.
- Protect privacy. Minimal data collection. Analytics (Google Analytics) runs only with visitor consent and is configured for data minimisation.
- Use responsible infrastructure. Energy claims, location, performance, security and transparency weighed together.
- Maintain what we build. Content, dependencies, accessibility and performance reviewed as the site changes.
Design and development commitments
Every public page has a defined purpose. No filler. Genuine imagery in responsive formats. No autoplaying background video. Sparing animation with reduced-motion respect. Limited font families and weights. Semantic HTML, native browser capabilities, proportionate JavaScript, optimised assets, lazy-loaded below-the-fold media, security updates and backups.
Hosting
Provider: Raidboxes GmbH, hosted in Germany (EU). Raidboxes states its infrastructure runs on 100% green electricity. We will not describe the hosting as renewable, green or carbon neutral without a current source that explains the boundary of the claim.
Performance budget
Budgets for transferred page weight, image transfer, JavaScript, CSS, fonts, requests and Core Web Vitals – stated as project controls, with exceptions recorded and justified.
How we estimate carbon
Website carbon estimates are calculated from data transfer and assumptions about energy across data centres, networks and user devices. For each published estimate we record the tool and version, model and version, page tested, date and location, visit assumption, hosting classification and limitations. We use CO2.js with the Sustainable Web Design Model. The estimate is described as an estimate.
Baseline results
Baseline results for the live site will be published here. For each representative page: page name and URL, transferred weight, requests, vitals evidence and estimated grams CO2 per view, with method and date.
Improvements still to make
A live list of known heavier pages, planned optimisations and review dates – maintained as the site changes, not written once.