Last updated: September 2026.
Sustainable and traditional web design use the same platforms and skills. The difference is a set of defaults: lighter images and video, fewer third-party scripts, chosen hosting and caching, and a page weight budget the team defends through every revision. Timelines stay close to the same; what changes is what the site measures after launch.
| Build area | Traditional web design | Sustainable web design |
|---|---|---|
| Images and video | Sized for the design file, compressed if someone remembers to | Sized for the display, compressed and served in modern formats by default, video gated behind a click |
| Fonts | Two to four families pulled from a font service as needed | One or two families, self-hosted, subset to the characters the site actually uses |
| Third-party scripts and tag managers | Added as marketing and analytics tools come up, rarely removed | Audited before launch and on a schedule, anything unused gets removed |
| Hosting | Chosen for price, support and server location | Chosen for price, support and server location, plus verified renewable power |
| Caching | Left on the default plugin or server setting | Configured and tested on purpose, since it protects repeat visitors |
| Page weight budget | Not usually set as a number the team is held to | Set at the start of the project and checked at every revision |
| Accessibility | Often a separate line item or an afterthought | Built in from the wireframe, since clean markup serves both goals |
| Ongoing maintenance | Updates and backups, performance revisited if something breaks | Updates and backups, plus a periodic recheck of weight and scripts |
| Cost and timeline | Priced and scheduled by scope | Priced and scheduled by the same scope, the difference is where the hours go |
None of this makes traditional web design bad design. Plenty of traditional builds are well designed, accessible and well maintained after launch. And sustainable web design is not a stripped-down, plain text site with no personality: some of the lightest sites on record are also some of the most visually considered, because a sustainable build spends its weight budget on purpose instead of by accident, the same way our own web design team builds every project. Call the list above the Default Stack: eight build decisions where the two approaches actually diverge. The rest of this guide walks through each one, plus what it does to your cost, your timeline and what you can measure once the site is live.
What actually changes in images and video?
Images and video are the heaviest part of almost every page, in sustainable and traditional web design alike. The HTTP Archive’s 2025 Web Almanac put the median page at 2.86 MB on desktop and 2.56 MB on mobile, with images alone accounting for roughly 37 percent of that weight and video pushing individual pages far higher when it autoplays in a hero section.
A traditional build usually compresses images if someone remembers to, often late in the project, and treats video as a design decision rather than a weight decision. A sustainable build sets a target file size for every image before it is placed, serves modern formats like WebP, and gates video behind a click instead of an autoplay, so the visitor decides whether to spend that bandwidth. Same photography, same production value, different discipline about when the pixels get sent.
What is different about fonts?
Sustainable and traditional web design can use the exact same typefaces. The difference is delivery. A traditional build often pulls two to four font families from a third-party font service, loading weights nobody uses because the theme shipped with them enabled. A sustainable build narrows that to one or two families, hosts the font files on the same server as the rest of the site instead of calling out to a third party, and subsets each file to the characters the brand actually needs. Fonts also block rendering while they load, so trimming them speeds up the page twice: once in bytes, once in the time before text appears on screen.
Do sustainable builds really cut third-party scripts and tag managers?
Yes, and this is usually where the biggest single difference in the build lives. A tag manager is rarely one script. It is a container that loads other people’s scripts, some of which load more scripts behind it, and most of those get added over time and never removed.
Sites built with traditional web design tend to accumulate these: a chat widget here, a retargeting pixel there, a plugin that quietly loads a script library the page never calls. A sustainable build audits what actually fires on a live page, keeps what earns its place, and removes what nobody has looked at in months. The visible result is a lighter page. The less visible result is fewer scripts running code on every visitor’s device on every page load, which is where a large share of a page’s actual energy use happens.
Does hosting make a measurable difference?
Some, though less than its reputation. Hosting decisions in traditional web design are made on price, support and server location. Sustainable web design adds one more requirement: the host’s electricity has to be verified as renewable, not just claimed, which is what a directory like the Green Web Foundation exists to check. That said, hosting is one input among several, not the whole answer. A verified green host running a bloated, script-heavy site will still lose to a lean site on ordinary power. The two decisions work together, they do not substitute for each other.
How do caching and page weight budgets change the build?
Caching is often left on a default setting and forgotten, which is exactly what a traditional build usually does: whatever the plugin or the server ships with, left alone unless something breaks. A sustainable build configures and tests caching on purpose, because it does not shrink what a first-time visitor downloads, but it removes that download entirely for everyone who comes back, which matters most on a site people revisit.
A page weight budget is the more unusual habit. Instead of finding out how heavy a page turned out to be after it is built, the team sets a number before the first wireframe, for example under 1.5 MB for a landing page, and treats every added image, script or embed as spending from that budget. Going over is a conversation, not a surprise at launch. Traditional web design projects rarely set this number at all, which is the real reason page weight tends to creep up over a project’s life regardless of anyone’s intentions.
If you are looking at two proposals right now and cannot tell from the language alone which one actually builds this way, ask us for a third: we reply with a plan and a price within 24 hours, no call required. Get a quote.
Is accessibility included, or a separate line item?
In traditional web design, accessibility often shows up late: a plugin added before launch, or a fix list after a complaint. It gets treated as compliance, separate from the design work. In a sustainable build, accessibility tends to arrive built in, because the same habits that reduce page weight, clean semantic markup, fewer intrusive scripts, deliberate color and contrast choices, also make a site easier for assistive technology to read. The two are not the same discipline, but they share a foundation. Neither approach guarantees accessibility conformance on its own; ask any vendor directly which standard they build to and how they test it, sustainable or not.
What changes in ongoing maintenance after launch?
Traditional web design and a sustainable build need the same baseline: core and plugin updates, backups, and someone checking that forms and payment flows still work after an update. A sustainable maintenance plan adds one habit on top of that baseline: a periodic recheck of page weight and active scripts, on a schedule such as quarterly, rather than only when something visibly slows down. New plugins, embeds and tracking pixels get added after launch on almost every site; without a recheck, a lean launch quietly turns heavy again within a year.
Does it cost more than traditional web design, take longer, or neither?
For the same scope, the estimate range and the timeline are close to the same. What changes is where the hours go: less time picking stock plugins and default settings, more time on image and video preparation, script audits, and testing the page weight budget at each revision. Ongoing sustainable maintenance can carry a small premium over bare-minimum upkeep, for the same reason a quarterly check costs more than no check at all. Be cautious of a proposal, on either side, that promises a full custom build for noticeably less than a comparable traditional project: the difference in this list is where the care goes, not a discount.
What do you get at the end that you can actually measure?
Traditional web design gets you a working site, judged mostly by whether it looks right and functions. A sustainable build gets you the same working site, plus numbers you can put in a report: a page weight figure at launch, a carbon grade from a tool like our own Website Carbon Checker, and a baseline to compare against a year later. None of those numbers are a certification, since no governing body certifies an individual website, but they are real, repeatable measurements a marketing lead can hand to a board or a sustainability report without hedging.
If your team already knows it wants this approach, our sustainable web design agency page has the published process and starting prices. If you are still deciding what the term even covers before you compare vendors, start with our plain-English guide to sustainable web design.
Frequently asked questions
Is a sustainable website more expensive to build than a traditional one?
Not for the same scope. The estimate range and the timeline stay close to those of traditional web design; what changes is where the hours go, more into image and script preparation and weight testing, less into default settings left as they came. Ongoing sustainable maintenance can carry a small premium over bare-minimum upkeep, since it includes a periodic recheck the minimum plan does not.
Will a sustainable site look plainer or less creative than a traditional one?
No. Sustainable web design is a set of engineering defaults, not a design style. Photography, animation, custom layouts and brand personality are all still on the table; the difference is that every asset earns its place in the page weight budget instead of arriving by default.
Can an existing WordPress site be rebuilt as a sustainable site without starting over?
Often, yes. Many of the changes, compressing and resizing images, subsetting fonts, removing unused scripts, configuring caching, can be applied to an existing theme and structure. A full rebuild becomes worth it when the underlying theme itself is heavy or poorly coded, which an audit will show.
Does choosing sustainable web design help or hurt SEO?
It tends to help. Google’s own documentation lists Core Web Vitals, the metrics that track loading speed, responsiveness and visual stability, as part of what its ranking systems evaluate. Removing an oversized image or an unused script is a page weight fix, a speed fix and an SEO input on the same line of code.
How do I verify that a proposal calling itself “sustainable” actually is?
Ask for specifics against the Default Stack above: a stated page weight budget, the image and font approach, a list of what scripts will run, and how hosting was verified rather than just claimed. A vendor who builds this way can answer each one in a sentence. A vendor using the word as a label usually cannot.
Do I need green hosting for a site to count as sustainable?
It helps, but it is one input among several, not the whole answer. In the Sustainable Web Design Model’s own breakdown, the data center segment that a green host changes is a minority of a page’s total energy intensity; the network and the visitor’s device account for more. A verified green host paired with a heavy, script-loaded site will still lose to a lean site on ordinary power.
Kurt Whitt
Planet Media
Founder and CEO of Planet Media, a sustainability focused marketing agency. 25+ years helping purpose driven brands grow through strategy, storytelling and design.
More about the team