We covered the infrastructure side of sustainable computing - right-sized cloud resources, efficient backend architecture - in a separate piece. This one is specifically about the frontend and design decisions that affect a website’s carbon footprint, which get less attention but are genuinely within a design and content team’s direct control, not just engineering’s.
Where a website’s frontend actually drives energy consumption
Every byte transferred to a visitor’s device costs real energy - network infrastructure, data centers, and the device itself all draw power proportional to the data moved and processed. A bloated page with unoptimized images, unnecessary third-party scripts, and excessive animation isn’t just slower for the user; it’s measurably higher energy consumption multiplied across every visitor, every page view. At real traffic volume, this adds up to a genuine, calculable environmental cost, not an abstract one.
What actually moves this number, concretely
- Image weight, by far the largest lever on most sites. Properly compressed, correctly sized, modern-format (WebP/AVIF) images routinely cut page weight dramatically compared to unoptimized originals - this is usually the single highest-impact change available on a typical content-heavy site.
- Video and autoplay content used deliberately, not by default. Autoplaying background video is one of the heaviest, least necessary additions to a typical page’s weight - genuinely reconsidering whether it’s adding real value versus just following a design trend is worth doing on its own merits, separate from the sustainability angle.
- Third-party script audit. Every analytics tool, chat widget, and marketing pixel adds real weight and often runs continuously in the background - a periodic audit of what’s actually still needed versus what’s been added over time and never removed catches real, easy wins.
- Dark mode as a genuine, if modest, energy consideration on OLED and similar displays, where darker pixels draw meaningfully less power - a smaller lever than image optimization, but a real one worth offering as an option, particularly for content-heavy or long-session applications.
Where this overlaps directly with performance and SEO work you’d want anyway
Nearly every change that reduces a page’s carbon footprint is identical to the change that improves Core Web Vitals and page speed - smaller images, fewer unnecessary scripts, less bloat. This means sustainable design work isn’t a separate initiative competing with performance and SEO priorities for engineering time; it’s largely the same work, viewed through an additional lens. We don’t run separate “green audits” for this reason - a performance audit already surfaces nearly everything relevant.
Where we’d draw a line on this
Removing genuinely valuable content or functionality purely to reduce page weight is the wrong trade - the goal is eliminating waste (bloated, unoptimized, unnecessary weight), not eliminating value. A well-optimized page with genuinely useful video content is a better outcome than a stripped-down page that no longer serves the user’s actual need, even if the stripped version scores marginally better on a carbon calculator.
What we’d actually recommend
Start with an image and asset audit - it’s almost always the highest-impact, lowest-risk change available, and it improves load speed and user experience at the same time it reduces environmental impact, with no real trade-off to weigh.
We build efficient, well-optimized sites as standard practice in our web development work - sustainability is a natural byproduct of the performance discipline we already apply. Get in touch for an audit of where your site’s weight is actually coming from.