Beyond Optimization
When we talk about sustainable web design, most people think about green hosting or renewable energy. But there’s another, quieter lever with enormous impact: media optimization – especially images.
Every unnecessary megabyte we send across the internet burns energy, emits CO₂, slows down users, and consumes resources we could easily save with better defaults. So we asked ourselves: why does WordPress still upload, store, and serve such bloated image files – and can we fix that at the source?
The problem with the default WordPress way
WordPress core is designed for compatibility and editorial convenience. By default it:
- Uploads and stores the original full-resolution file.
- Generates multiple resized versions (whether they are used or not).
- Keeps legacy JPEGs and PNGs even when WebP thumbnails are available.
- Applies only light, conservative processing; it does not aggressively optimize images.
In other words, WordPress is very good at preserving pixels, but not very good at preserving the planet.
Plugins, convenience – and bloat
There are hundreds of “image optimization” plugins. Many of them sound helpful, but come with trade-offs:
- External processing: most optimization plugins rely on remote services – your images are uploaded to third-party servers for compression and then returned to your site.
- Privacy and compliance: routing media off-site can create GDPR and data-sovereignty considerations.
- Overhead: cron jobs, transients, extra metadata, and UI layers add complexity and database weight.
- Lock-in and cost: quotas, credits, and premium features for common formats like AVIF.
Some tools offer local modes, but the default path in most stacks still adds bloat and dependencies.
Our approach: local, lightweight, logical
We decided to start from first principles:
- Do it locally. Conversion happens on the site’s own server – no third-party processing.
- Keep it lean. A small, audited function replaces heavy plugins.
- Measure what matters. We calculate real bytes saved, not just abstract percentages.
- Make it visible. Editors see subtle upload toasts and a live admin-bar counter of daily data and CO₂ savings.
Technically, the process is simple: every image upload is converted to WebP directly on the server; the original file is removed once conversion succeeds; WordPress’s automatic “-scaled” duplicates are disabled; and the dashboard quietly shows a running total of megabytes saved.
Why WebP matters (and why we drop legacy formats)
WebP is supported by all modern browsers. It typically cuts file size by 60–90% compared to JPEG and PNG while preserving quality, and it supports transparency and animation. By storing only WebP, we:
- Eliminate redundant legacy formats that inflate storage and backups.
- Simplify CDN behavior and cache keys.
- Deliver smaller, faster pages – especially critical on mobile networks.
If a non-WebP fallback is ever required for a specific integration, it can be generated on demand or provided by the CDN – no need to stockpile duplicates on origin.
Privacy, security, and sovereignty
Because conversion happens entirely on the site’s own server, no media leaves your infrastructure. That means:
- No exposure of assets to external processors.
- No extra compliance burden under GDPR or regional data rules.
- No keys, quotas, or remote dependencies.
The environmental impact
It’s easy to dismiss a few megabytes, but the numbers scale quickly. An image reduced by 1 MB and viewed 10,000 times avoids roughly 0.6 g CO₂ per view-gigabyte equivalent; across busy sites, gigabytes saved per day are common. Small, systemic improvements create meaningful reductions when multiplied by real traffic.
A different kind of optimization
The new upload system built into our core theme is small, transparent, and predictable:
- No API keys.
- No hidden network calls.
- No recurring fees.
- Just local, deterministic compression and clear savings.
It’s not about squeezing every pixel; it’s about removing waste throughout the stack.
A quiet but impactful change
Sustainability in digital design isn’t a checkbox – it’s a design decision. With this update to our core theme, every Conlumina project now automatically saves data, time, and emissions with each image uploaded. It’s a quiet change with a measurable difference – the kind of detail we believe makes technology worth trusting.
