Digital experiences consume resources across devices, networks, and infrastructure. Their exact impact depends on many factors, so broad comparisons need careful measurement.
A practical starting point is to remove work that does not contribute to the experience. Appropriately sized images, fewer unnecessary requests, and sensible retention can simplify a system as well as reduce some resource use.
Measure what you change and avoid claims the evidence does not support. Restraint is most useful when it remains connected to the service people need.
An example to consider.
A publication could prepare appropriately sized images for each placement. Sending fewer unnecessary bytes can be a practical design decision without changing the story.
Put it in perspective.
Separate the possibility from the commitment. A small trial can answer a question while leaving room to change direction after you learn more.
- Identify unnecessary transfers or repeated work.
- Make one measured improvement.
- Keep impact claims within the available evidence.
Follow a related question
Distinguish local preferences from account data.
Where a cloud application livesDescribe a scene at two scales.
Changing the scale of a questionKeep learning
Related background to continue exploring this subject.
W3C: web accessibility W3C: accessibility, usability, and inclusion