Sustainable UX design for higher performance

Flourish Marketing - Kabaddi World Cup render on iPhone, Sustainable UX design

Every pixel has a price.

It is paid in energy, in the visitor’s time and in their attention, and the bill lands whether or not the pixel was doing anything useful.

Sustainable UX design is the practice of designing journeys that spend less of all three. Fewer steps to the outcome, fewer page loads along the way, fewer elements competing for a decision the visitor has already made.

This is not a trade-off against a good experience. Most of the time it is the same thing described from a different angle, because the shortest useful path is usually also the clearest one.

Sustainable UX design for higher performance

Count the page loads

Start here, because it is the measurement teams rarely take.

How many pages does someone load between arriving and completing your primary task? Every one is a full round trip: a request, a render, a wait, and a fresh opportunity to abandon.

A four-step enquiry process that could be two is not merely twice the friction. It is twice the data, twice the processing, and two more moments where someone decides they will do this later and then does not.

Map the journey honestly. The step that exists because a department wanted a field is the one to challenge first.

Design for the decision, not the page

Each screen should ask for one thing. When a page presents four equally weighted actions, the visitor has to do work that the design should have done.

Put the action where the decision gets made. Someone persuaded by the second paragraph should not have to scroll past four more to act on it.

Remove what does not serve the task in front of them. Related articles, newsletter prompts and social widgets all compete with the thing you actually want to happen, and each carries weight.

hand drawn website wireframe

Forms are where journeys die

Ask for what you need to complete the transaction and nothing you would merely like to have. Every optional field is a small tax paid by every applicant so that somebody can occasionally run a report.

Validate inline rather than on submission, so people correct one thing at a time instead of meeting a wall of errors after committing.

Accept information in the shapes people actually provide it. Names with apostrophes, addresses that do not fit a template, phone numbers with spaces. Rejecting valid input is a failure of the form, not the person.

Accessibility and efficiency travel together

Clear headings and predictable navigation reduce how many pages someone loads to find what they need, which helps people using screen readers and people on slow connections for the same reason.

Semantic HTML reduces reliance on scripts. Reduced motion lowers processing and helps people with vestibular conditions. Sufficient contrast helps everyone reading outdoors.

Work towards WCAG 2.1 Level AA and test with keyboard navigation and zoom. Simplicity alone does not guarantee accessibility, but unnecessary complexity reliably creates barriers.

Where performance and environmental impact both apply, treat them as the same lever. Reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.

WCAG 2.1 AA infographic of each level.

What to measure, and what not to claim

Track the things you can attribute: steps to completion, drop-off by step, page weight and Core Web Vitals on the pages in the journey, recorded under stated conditions.

Watch five people attempt the task. This finds problems analytics only hints at, because analytics tells you where people left and not why.

Be careful with outcome claims. Simplifying a journey can improve completion, and often does, but the size of the effect depends on your audience and starting point. Measure your own before and after rather than repeating a figure from a case study about a different business.

Our sustainable web design work treats journey design, accessibility and page weight as one brief.

Hills Quarry Google Core Web Vitals report mockup on Macbook - Decarbonisation campaign, Agnikii Driftguard

For businesses across the South West

If your customers are frequently on phones on uneven connections, journey length costs you more than it costs a competitor selling into a city centre. Each additional step is another chance for the connection, or the patience, to give out.

Smaller teams have the advantage of being able to remove a step without convening a committee. That is worth using.

Most common questions

01

What is sustainable UX design?

It is designing user journeys that reach the outcome with fewer steps, fewer page loads and less unnecessary weight. It overlaps heavily with plain good UX, with an explicit eye on what each step costs in data, processing and attention.

02

How is it different from ordinary UX work?

Mainly in what gets measured. Conventional UX optimises for task completion and satisfaction; sustainable UX adds page loads, weight and processing to the same review. Since shorter journeys are usually both faster and clearer, the two rarely conflict.

03

Will simplifying our journey increase conversions?

It often helps, because fewer steps mean fewer opportunities to abandon. The size of the effect varies with audience and starting point, so treat it as a hypothesis to test on your own site rather than a guaranteed result.

04

Which form fields should we remove?

Anything not required to complete the transaction. Fields collected for reporting or future marketing are paid for by every applicant, and they are a common cause of abandonment. If a field is genuinely needed later, ask for it later.

05

How do I find the friction in an existing journey?

Watch five people attempt the real task on the real site and say nothing while they do it. Combine that with drop-off data by step. Analytics shows you where people leave; observation shows you why, and you need both.

06

Does this mean removing features?

Sometimes, though more often it means reordering and deferring them. The test is whether an element helps the visitor complete what they came to do. Anything that does not is competing with the thing that does.