Delivery via Cloudflare
bytebrise.com is hosted by mittwald in Germany and delivered through the Cloudflare network, which caches pages in the nearest edge data centre. Shorter routes mean less energy per request.
Sustainability · Low-carbon websites
How we build websites that use little electricity.
The internet uses a lot of electricity, and every page view causes CO₂ emissions. We cannot solve that on our own, but we can make sure our websites do not add to the problem. Here is how we do it technically, what it achieves and where we still want to improve.
Measure this page's CO₂ footprint
What we measure
Four figures that show where we stand.
We measure every live page with websitecarbon.com and enter the values here. The values refer to the bytebrise.com home page (as of August 2026).
Footprint per visit
0.11 g
CO₂ per average visit. The global web average is around 1.3 g per visit (websitecarbon.com).
Delivery
100%
Cloudflare has run its edge infrastructure on renewable energy since 2024. bytebrise.com is delivered through this network; the origin server is hosted by mittwald in Germany.
Bytes delivered
~65 KB
HTML of the home page, without video. With the hero video on desktop it comes to around 15 MB, but the video only loads if the browser does not signal Save-Data.
Rendering energy
B
Websitecarbon's cleaner-than-74% rating. The top grade A+ is only reached below 0.1 g per visit.
bytebrise.com is delivered via Cloudflare, and Cloudflare confirms its green hosting status with The Green Web Foundation. We do not claim a separate green electricity certificate for the origin server at mittwald. The Website Carbon live test measures 0.11 g CO₂ per page view (measured on 19 August 2026). You can check both values yourself at any time in the Website Carbon report.
How we solve it technically
How we apply the six levers.
Avoiding greenwashing: we only list what we have actually implemented. If it is not on this list, we do not do it. Want to check your own CO₂ footprint? The audit tool from bytebrise green measures any website and shows concrete levers for improvement.
On-the-fly image resizing
Instead of storing several image sizes, a worker transforms images on first request to fit the viewport. It delivers WebP and AVIF dynamically. In our case: a 1.4 MP hero image reduced from 190 KB to 9 KB for the 400-pixel version.
Effect: more than 90% fewer bytes per image on mobile visits.
Local fonts, no CDN pings
Fonts are subsetted and hosted on our own server. No round trip to Google Fonts, no tracking cookies, fewer DNS lookups. Manrope Regular: 14 KB.
Saves around 50 KB of third-party bytes and 1-2 extra connections per visit.
Carbon-aware loading
For browsers with the Save-Data flag or a slow connection, the hero video does not load at all. A static poster image stays visible. Saves up to 15 MB per visit for these users.
Detects: prefers-reduced-data, navigator.connection.saveData, 2G/3G connections.
Aggressive caching
Static assets get an `immutable` cache with a long lifetime, and HTML is served with stale-while-revalidate. Returning visitors reload almost nothing.
Effect: a second visit typically causes less than 5 KB of traffic.
Lean code, no frameworks
Vanilla HTML, CSS and JavaScript without React, Vue or a Tailwind build. The site CSS is 32 KB, the site JS 8 KB. No megabyte bundles for a marketing site.
Effect: no JS parsing, no hydration overhead, less CPU load on the device.
Your website can be low-carbon too.
When you hire bytebrise for a project, you get this set-up as standard. No extra charge, no extra explanation. It is simply how we work.
Book an initial consultation