A visitor loads four pages looking for your opening hours, gives up, and phones you instead.
Four page loads. Four sets of images, scripts and fonts transferred. Four rounds of processing on their device. Nothing achieved except irritation, and none of it appears anywhere as a problem, because your analytics record four page views and count them as engagement.
The link between good UX and digital emissions is exactly this. Every avoided page load is transfer and processing that never happened, and the way to avoid them is to let people find things.
Good UX Digital Emissions: Why Better Journeys Help
Why journey length is the metric nobody tracks
Page weight gets measured. Journey length rarely does, and it multiplies everything.
Count the pages somebody loads between arriving and completing your primary task. If it is four and could be two, you are transferring twice the necessary data for every person who completes it, and considerably more for everyone who gives up partway.
That multiplication is why UX work belongs in this conversation at all. Halving a journey has a larger effect than shaving a hundred kilobytes off a page, and it is usually easier to justify commercially.
Where the waste sits
- Information people hunt for. Opening hours, prices, contact details, delivery terms. Each hidden fact is a page load somebody did not need.
- Navigation that does not match how people think. Labels drawn from your internal structure rather than their vocabulary, so people guess, backtrack and guess again.
- Search that does not work. A site search returning nothing useful sends people back to the navigation they had already given up on.
- Forms that fail late. Validation on submission rather than inline means a reload, a lost entry and a retry.
- Content that answers slowly. A page building to its point across four hundred words when the reader wanted the first sentence.
None of these are visual design problems. All of them cost transfer.
Finding it on your own site
Watch five people attempt a real task and say nothing while they do it. This is the whole method and it is more informative than any analytics report.
Where they pause, backtrack or reach for search, the structure is not matching their expectations. Count their page loads and compare against the minimum the task actually requires.
Then check drop-off by step in your analytics. Analytics tells you where people left; observation tells you why. You need both, and most organisations have only the first.
Fixing it
Put the frequently wanted facts where they need no hunting. Opening hours, phone number, prices where you can publish them.
Label navigation the way visitors describe things, not the way your organisation is arranged.
Validate forms inline and ask only for what routes the enquiry. Every field is answered by everyone.
Answer questions in the first two sentences of a section, then elaborate. This serves readers in a hurry and, incidentally, systems extracting an answer.
Remove steps that exist because a department wanted a field rather than because the task needs one.
What this is worth, honestly
Fewer page loads means less transfer and less processing. 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.
The commercial case is stronger and more immediate. Shorter journeys mean fewer opportunities to abandon, which usually shows up as completion rate before it shows up anywhere else.
Be careful not to overstate the environmental side. A journey shortened from four steps to two is a real reduction in transfer for that journey. It is not a claim about your organisation’s footprint, and the difference matters if you publish anything.
Accessibility improves the same numbers
Clear headings, predictable navigation and semantic structure help people using screen readers find things without loading extra pages, for the same reason they help everyone else.
Work towards WCAG 2.1 Level AA on its own merits. The overlap with journey efficiency is genuine, and neither causes the other.
Our website sustainability audits measure journey length alongside page weight, since the two multiply.
