Eco-design
Verifiable digital sobriety: carbon budget per page, measured payload, right-sized infrastructure - not a claim, a practice.
Eco-design is not a badge: it is a set of technical decisions made from day one - asset weight, HTTP requests, caching, infrastructure sized to actual need. Every gain is measured, every regression detectable in CI.
Measure before and after
EcoIndex and RGESN provide a quantified reference: score per page, estimated carbon footprint, request count, transferred payload. We establish a baseline, set thresholds, and measure the impact of every release.
Asset and cache optimisation
Images converted to WebP/AVIF and resized on demand, fonts self-hosted with font-display: swap, third-party scripts deferred or removed. Cloudflare cache cuts origin load by more than 85% on high-traffic sites.
Right-sized infrastructure
BSO Kubernetes with horizontal autoscaling: pods scale up under load and shrink after the peak. No paying - and no consuming - for idle compute. Media is on S3/MinIO, served via CDN.
Why measure eco-design
Digital technology accounts for roughly 4% of global CO2 emissions, a share that continues to grow. Web eco-design acts on factors directly within our scope: page weight, request count, asset cache lifetime, infrastructure sizing.
The RGESN (French General Reference for Digital Service Eco-design, published by DINUM) covers 79 criteria across 8 themes: strategy, specifications, architecture, UX/UI, content, front end, back end, and hosting. It complements EcoIndex (an A-to-G score based on page weight, request count and DOM complexity).
Technical levers applied
Asset weight:
- Images converted to WebP or AVIF, resized to the correct resolution via the Next.js
<Image>component or a Cloudflare Images worker. - Fonts self-hosted (no external Google Fonts) with preload and
font-display: swapto avoid FOIT. - CSS and JS bundle-split, tree-shaken and Brotli-compressed. No unnecessary dependencies in the client bundle.
HTTP request count:
- Third-party scripts (analytics, ads, widgets) loaded in deferred mode or not loaded at all if consent has not been given.
- SVG sprites or icon fonts for repeated pictograms.
- API calls aggregated through the MUH middleware: a single round-trip between front end and backend, no client-side request waterfall.
Cache and infrastructure:
- Cloudflare full-page cache on static routes, targeted invalidation on every publish (no global wipe).
- BSO Kubernetes: horizontal autoscaling based on actual CPU/RAM load. Replicas shrink after traffic peaks - no sustained overconsumption.
- Media on S3/MinIO, served via CDN with long TTL. No local filesystem on pods (stateless).
What this means for your CIO
- EcoIndex report per URL: letter grade (A to G) plus estimated carbon footprint (gCO2e per visit), available as an audit or integrated into CI.
- CI/CD thresholds: a build can be blocked if page weight exceeds a set threshold, exactly like a performance test.
- Documented RGESN compliance: an audit grid filled criterion by criterion, applicable for public procurement or a corporate CSR policy.
- Lower hosting costs: a correctly cached and right-sized site consumes less compute. Eco-design and cost control point in the same direction.