No website sets out to become heavy. It happens one reasonable decision at a time.
A tracking pixel for a campaign that ended last spring. A carousel someone asked for two years ago. A chat widget nobody has staffed since. Each was defensible on its own, and together they now cost you load time, clarity and maintenance hours.
Digital degrowth is the practice of removing what no longer earns its place. It is not minimalism as a visual style, and it is not a case for building less ambitiously. It is a way to define progress through usefulness, accessibility and efficiency rather than volume.
Where performance and environmental impact both apply, treat them as the same lever. Reducing unnecessary data transfer and processing can support a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.
Why more becomes worse
Growth in web projects usually means addition. More plugins, more integrations, more motion. But every addition carries a cost beyond the obvious one: data transfer, maintenance, security exposure, cognitive load. People on slower connections, older devices or assistive technology feel those costs first and hardest.
The environmental cost follows the same path. Every kilobyte transferred needs electricity, and a meaningful share of that electricity still comes from carbon-intensive sources. A leaner site can use less energy per visit. Whether it does depends on hosting, page assets and processing, so the result belongs in an assessment rather than an assumption.
Digital degrowth borrows from post-growth economics and slow technology. It asks a plain question that is harder to answer than it looks: what if building less served people better?
Refuse, reduce, rethink
The framework is three decisions, in order.
- Refuse what does not serve your users. Carousels, autoplay video, tracking-heavy plugins. Nothing enters the build without a stated user or business need.
- Reduce what you keep. Compress useful media properly, strip unused code, limit third-party scripts, and load non-critical assets only when they are needed. Lightweight frameworks often outperform heavy ones. Sometimes no framework performs best of all.
- Rethink the journey. Prioritise clarity in your content hierarchy. Remove clicks, distractions and anything that does not serve the task in front of the reader.
Three questions worth putting to your team before any feature ships:
- Do we truly need this?
- Can we meet the goal with less?
- Are we designing for clarity or for clutter?
Applying digital degrowth across a team
Designers start with content and hierarchy, not decoration. Favour space and typography over media-heavy interaction, and ask whether a design system can work harder with fewer components.
Developers audit dependencies, prefer semantic HTML and ship less JavaScript. Static output beats runtime assembly when the content allows it.
Editors archive duplication and cut wording that no longer helps anyone. Measurement tracks page weight, requests and Core Web Vitals before and after a change, under recorded conditions. Governance gives every feature an owner and a review date, which is the part most teams skip and later regret.
How to decide what goes
Build a register of features, content and third parties, each with an owner and a stated purpose. Use analytics, research and support tickets to find low-value additions, then check accessibility and record-keeping needs before you remove anything.
Removal should begin with purpose rather than file size. A rarely used accessibility option or a statutory record may be essential despite low traffic. A popular widget may duplicate a simpler journey while collecting more data than the task requires. Look for duplicated capability as well as unused capability: several analytics products, overlapping search widgets or three ways to contact the same team all create work without improving the outcome.
The W3C Web Sustainability Guidelines set out relevant practices across product, experience, development and hosting decisions.
Remove without breaking things
Prototype the simpler journey and test it with representative users before committing. Preserve useful URLs with redirects. Communicate material service changes rather than letting people discover them.
Retiring an interface does not retire what sits behind it. Stored personal data, scheduled jobs and supplier access need a controlled plan, and retention obligations should be confirmed with qualified advisers where they are unclear.
For anything uncertain, run a reversible trial. Remove or simplify one element for a suitable audience, watch task completion and read the support feedback. Restore it if the evidence shows a real loss. Degrowth should stay reversible while your confidence is low.
Prevent it from growing back
New features and tools need a purpose, an owner and a review date before approval. Set performance budgets and write maintenance into agreed requirements rather than discovering it later.
Procurement does more work here than most teams expect. Require new tools to state their integration footprint, accessibility evidence, data handling and exit plan, and include the cost of removal when comparing products.
Explore sustainable web design to apply this in a measured build or redesign.
Accessibility and restraint
Accessible design and digital degrowth are natural allies rather than competing priorities. Reduce motion, and you create a calmer experience for neurodivergent users while lowering processing load. Use semantic HTML and screen readers work better while scripts become unnecessary. Simplify navigation, and people on mobile, on slow connections and with cognitive differences all benefit at once.
That overlap is a blueprint, not a coincidence. Work towards WCAG 2.1 Level AA and test with real users. Simplicity alone does not guarantee accessibility, but unnecessary complexity reliably creates barriers.
There is a positioning argument too. In a market where people expect transparency, restraint says something. Choosing not to include something becomes a message about what you think matters.
