Published 21 July, 2019; last updated on 31 July, 2019.
As a web developer who knows climate change is the biggest issue facing humanity, this makes for some uncomfortable reading. So I’ve started looking into what I can do about it.
The article cited by Nature above identifies four ways a web site might use energy:
I’m planning on focusing on these four ways of using energy to guide changes to the sites I’m responsible for to reduce their carbon footprint.
Here are some of my initial thoughts on how I might do that, and how you might do the same.
This is the use of energy on the laptop, smartphone, or other device which might be accessing a web site.
Consumer device energy use can be measured with tools like Activity Monitor on Mac OS, Task Manager on Windows, or
top on Unix.
In my opinion, there’s a huge impact which could be made here. Small changes to instructions executed on devices could save a small amount of energy on hundreds, thousands, or millions of devices. A small change multiplied by all of those devices could be massive.
If you’ve ever used an ad blocker, you’ve probably observed the extra load advertising and tracking scripts add to many web sites. I encourage people to install ad-blockers to reduce the huge load imposed by those irresponsible scripts1. Anyone with any kind of influence should work to remove such scripts from their sites. Developers should ensure their code is as efficient as it can be.
In my experiments, it seems like CSS animations can be a big, somewhat hidden contributor to consumer device energy use. In the past I’ve tried adding some subtle animation to this site, but found that it caused unusually high CPU usage in Firefox, which doesn’t seem to be as optimised to offload those animations to the GPU as some other browsers.
This is the energy used delivering data to consumer devices, and is projected to increase massively over the next few years.
Network use can be observed in most browsers’ development tools.
In the same way a small change in consumer device energy use can have a massive multiplying effect, reducing the size of a web page by a small amount can also have a big impact.
Obvious ways to reduce network use is to make the files comprising a web site smaller and to eliminate unnecessary downloads.
Setting appropriate caching headers so that resources are only fetched when required can help, as can making use of a CDN to reduce the need to transport data over long distances.
This is the cost of running the site in data centres. This includes web hosting as well as other hosted services: CI/CD, logging, email, monitoring, test servers, and so on.
Energy use in the data centre is far more controllable than the other sources of energy use discussed here. It’s possible to ensure that the data centres you use are powered by renewable energy. You can check how power is generated around the world at Electricity Map, and check specific sites at The Green Web Foundation.
Even if your site is using renewable energy in the data centre, it should still be efficient. I find Django Debug Toolbar an invaluable tool to highlight any places for optimisation.
This is the energy used in manufacturing consumer devices.
Your web site mightn’t be able to talk someone out of buying a new iPad, but it should work on old devices.
Also, you should look after the devices you have and only replace them when you have to. I use an iPhone 6s which is coming up to its fourth birthday, and am still quite happy with it. I only recently replaced a 2011 MacBook Air with a 2016 MacBook Pro which I hope to get more than five years life out of.
From here, I’m going to start implementing changes to sites I’m responsible for to reduce their energy use. These sites include:
I will write further posts about this process in the hope it will inspire others to make similar changes to their sites.
I also encourage people to keep the “allow some non-intrusive ads” option enabled. Not all ads are terrible, and responsible publishers should be supported. ↩