Category: Digital sobriety

At Greenspector, our mission is to help our customers reduce the environmental impact of their digital services. We work on this every day, but is it enough to offset our own impacts?

To this fundamental question, we must admit that we do not have a simple answer at this time. We will propose to our Mission Committee to work on this subject in order to go further. In the meantime, here is what we can share with you.

To verify that we are having a positive impact, we need to know our own impacts, and estimate the impacts that our clients are avoiding thanks to us. For this exercise, we will focus on the most easily assessable impact data: greenhouse gas emissions.

Our impacts

This is the “easy” part of the calculation. We have been doing our carbon footprint every year since 2019, using the excellent software from our friends at Toovalu. So we know our greenhouse gas emissions. In 2021, they were 31 tCO2e.

Is this a lot? We can reduce this value to a monetary ratio commonly used in this type of approach: 31 tCO2e for 851 k€ of turnover in 2021, which represents 36.9 kgCO2e/k€ of turnover. By way of comparison, ADEME indicates an average value of 110 kgCO2e/k€ for the category “low material services”. We are therefore 66% below the sector average. This is good, but we can certainly do better.

Avoided impacts

This is where things get complicated. On the one hand, our activities are diverse (sales of licenses, audits of mobile applications or websites, help in choosing Android fleets, etc.). On the other hand, it is not so easy to know how much we have helped to avoid. We need to be able to measure “before” and “after” (which does not always happen) and ideally, between “before” and “after”, only our recommendations to reduce impacts should have been applied. However, if you develop applications or websites, you know that between two versions, it is rare that there are not multiple changes of all kinds.

Finally, there is a methodological question: let’s suppose an audit on a version 1.0, which leads to 30% less impact on a version 1.1. Can we consider that this 30% will be avoided ad vitam aeternam, in other words, can we consider that version 1.7, which will be released in 18 months, will have 30% less impact than 1.7 would have had if we had not intervened on version 1.0? For want of a better answer, we have chosen to consider that the avoided impacts apply for the next 12 months.

So we do not have the possibility of calculating avoided impacts on all our projects or for all our clients – which we regret. However, we can get an idea from a few cases for which this calculation was possible.

Let’s take three examples:

• The SNCF Connect mobile application (Android version): we were able to determine the impact avoided on the TER ticket reservation process: -18.9% or -10 tCO2e over one year.
• At the opposite extreme, the Orange Group’s Integrated Annual Report (IAR): the RAI 2021 website has a 55% lower impact than the RAI 2020, which for its audience – modest for this type of content – represents an avoidance of 0.024 tCO2e over one year.

Here we have 2 projects typical of our activity, extreme in their audiences, accumulating 10 tCO2e avoided, so an average of 5 tCO2e per project. However, in 2021 we worked on more than 70 application or website projects. By taking the average of these two projects, multiplied by 70 projects, we arrive at 356 tCO2e avoided. Another approach based on a categorisation of each service according to its intensity of use gives us 150 tCO2e. Let us retain this lowest value.

As a reminder, our own footprint that year was 31 tCO2e: even if our low value of 150t was still overestimated, it would be very surprising if it turned out to be less than 31t.

“And the third example?”, say those who follow

The third example is a lesser known service in our catalogue. This is our “Fleet Selection” offer, which consists, thanks to our laboratory measurements, of assisting our customers in choosing a smartphone for their business mobile fleet. The measurements and recommendations focus on autonomy criteria, of course, but also on the durability of the terminals (battery life, robustness, etc.) in order to check that they will be able to meet business needs for as long as possible.

In 2021, we helped a client choose the most sustainable device for a fleet of 35,000 smartphones and 5,000 tablets. Thanks to our measurements, he was able to ensure that he chose a model with an expected lifespan of 4 years instead of 3. The manufacturing impact of a smartphone is on average 54 kg CO2e, that of a tablet 108 kgCO2e (values extracted from the Greenspector impact model). Extending this fleet by one year before replacement therefore represents a saving of 810 tCO2e. It can be argued that we are not 100% responsible for this choice. If we attribute even 10% of these 810t to ourselves, this represents 81 tCO2e avoided – compared to the 31t we emit.

Conclusion

We don’t yet know how to quantify our positive impact precisely, and we may never know. But it is important for us to make sure that we do have a positive impact. This 2021 exercise has demonstrated that.

We will continue to work on this assessment of avoided impacts in order to arrive at more accurate results in the future. But even under conservative assumptions, we are confident that our actions are saving greenhouse gas emissions.

In addition, it should be remembered that improving the sobriety of apps has other positive impacts, particularly on the social aspect by enabling people with old and/or low-end terminals to access these digital services that are often indispensable in daily life.

All this makes us proud and strengthens us to continue our mission.

Thomas CORVAISIER

Thomas CORVAISIER is the CEO of GREENSPECTOR. After getting his degree in Engineering he worked for over 15 years in IT consulting alongside major companies, focusing on testing and software quality. He then worked on CSR topics (carbon accounting, environmental management) and eventually mixed these skills into GreenIT expertness and cofounding Greenspector.

After a first article where we based ourselves on the websites of the hosting companies to compare the hosting companies proposing “eco-responsible” offers, let’s take a closer look at the offers in question. 

The choice of a web hosting service is often complex because of the many factors to be taken into account (security, availability, storage capacity, sovereignty, etc.). If you also want to choose an offer based on its environmental impact, the choice becomes even more complex.

The main objective of this article is to present some criteria to be taken into account when choosing a web hosting offer.

We first look at the existing good practice guidelines.

Once the list of environmental criteria has been established, we will go into more detail on each of the criteria in order to better understand them but also to have the right information to understand the available criteria or even discuss them directly with the hosts.

Indirectly, this reading grid can also be useful for accommodation providers who are concerned about their environmental impact.

Our objective here is to propose a simple reading grid, allowing anyone to understand what to base their choice of an “eco-responsible” host on. However, all this information will not necessarily be on the websites of the hosting companies. The easiest way is to contact these companies directly to get the missing data.

We obviously welcome feedback and constructive comments in order to improve this reading grid and to know how it is used.

Existing benchmarks

In order to better understand how the environmental impacts of accommodation offers are translated, we started by looking at what the existing standards suggest on this subject.

In order to choose an eco-responsible host, the 115 good web design practices propose the following items (see below for details of each):

• Management of WEEE (Waste Electrical and Electronic Equipment)
• PUE (Power Usage Effectiveness)/CUE (Carbon Usage Effectiveness)/WUE (Water Usage Effectiveness)
• Responsible purchasing policy
• Respect for the social dimension
• Low carbon energy supply
• Carbon offsetting

The RGESN (Référentiel général d’écoconception de services numériques) proposes a dozen good practices relating to hosting. Among other things, it deals with :

• European Code of Conduct for Energy Efficiency in Data Centres.
• Presence of an environmental impact reduction approach (supporting indicators)
• PUE/CUE/WUE
• Equipment management
• Use of renewable energy
• Fatal heat
• Location of servers
• Good data management practices

Note: most of these criteria can be found in those selected for this comparison, with the exception of those relating to the location of servers (mentioned in the social commitments) or to data management (which depend on usage, in particular according to the criticality of the service and the data).

As usual, the GR491 (Reference Guide to Responsible Digital Service Design) offers many recommendations on the subject. If we stick to the essentials, we find :

• Waste management
• PUE
• Sizing of the physical fleet
• End of life of equipment
• Indicators on the software used

In addition, DINUM (Direction Interministérielle du Numérique) offers a practical guide to responsible digital purchasing, with in particular a sheet on IT infrastructure equipment and hosting services (and hosted solutions). The AGIT (Alliance GreenIT), for its part, updated a white paper in March 2023 on the control and optimisation of the environmental impact of a data centre.

By cross-referencing all these elements, we have drawn up a list of criteria to be checked, which is intended to be complete but not exhaustive.

Note 1: Currently, a working group within W3C is building a set of guidelines for website sustainability. One of the areas of work concerns hosting and infrastructure.

Note 2: In January 2023, the ADEME (Agence de l’Environnement et de la Maîtrise de l’Énergie) published a methodological reference framework for the environmental assessment of hosting and cloud services. This document defines the information to be gathered and displayed. At the time of publication of this article, the companies concerned have not adopted it, but it is hoped that this will be the case in the near future.

Reading grid for the environmental commitments of accommodation providers

Let us now look at what constitutes the reading grid in question.

The criteria used

On the basis of the benchmarks seen above and in order to better evaluate the accommodation offers, the choice was made to base ourselves on several criteria (which we will detail below):

• WEEE Management
• PUE
• WUE
• CUE
• Purchasing policy
• Social commitments
• Management of the heat produced
• Renewable energy supply
• Carbon offsetting
• ISO standards, labels, certificates

Description of the criteria

Management of WEEE (Waste Electrical and Electronic Equipment)

How electronic and electrical waste is dealt with. To date, most of this waste is trafficked (What is the status of recycling?).

WEEE management is about extending the life of electronic equipment through recycling or upcycling and reuse. For example, servers used for hosting can sometimes be reused in other contexts.

PUE  

The PUE (Power Usage Effectiveness) represents the proportion of energy used to power IT equipment (servers, storage and network) in relation to the total electricity consumed (for cooling, UPS, etc.). It is always greater than 1 and should be as close to 1 as possible. It is estimated that the oldest data centres have a PUE of around 2, whereas the most efficient ones are more like 1.1.

Many structures advertise very low PUE. Here again, it would be important to see how this is calculated. See the Scaleway website: https://www.scaleway.com/fr/leadership-environnemental/

WUE  

Following a similar reasoning as for the PUE, the WUE (Water Usage Effectiveness) evaluates the efficient use of water, especially for cooling equipment, by comparing it to the amount of electricity used for the equipment. Indeed, the amount of water used by hosts is very high, which increases the risk of water stress.

The aim is to get as close as possible to zero water consumption per kWh.

Few organisations today report CUE or WUE. However, this type of information is an essential complement to the PUE in order to ensure, for example, that a low PUE is not explained by higher water use.

CUE 

Carbon Usage Effectiveness (CUE) compares the amount of greenhouse gas emissions to the amount of electricity used. In order to improve it, technologies with lower CO2 emissions should be selected (which may be the case when a generator is used to produce the electricity rather than using the electricity grid directly). The objective may be to have a UEC of less than 0.1 kg of CO2.

Purchasing policy

The manufacture of equipment remains the most impactful stage in its life cycle, notably because of the many resources (including metals and rare earths) required. The purchasing policy is therefore an essential element in limiting the environmental impact of a hosting company, even if the manufacture of data centre equipment has less impact than its electricity consumption. Thus, some opt for reconditioned equipment or manufacture their own equipment and all must keep in mind the efficiency and durability of the equipment purchased.

Social commitments

It is impossible to make it an objective and directly measurable criterion. However, this category includes what some companies do to reduce the impact of their activity or to contribute to society, which is an essential component of responsible digital. Global elements such as a CSR plan or the Lucie label can testify to this. It may also be interesting to consider the location of buildings as well as local actions, choice of service providers, etc. 

Gestion de la chaleur produite  

Due to its activity and the demand on its equipment, a hosting company can produce a lot of heat. In order to keep the equipment in working order, it is necessary to cool it down, most often by using electricity via air conditioning for example (hence the notion of PUE seen above) or water. When released directly, this heat can have a negative impact on the environment (sometimes referred to as waste heat or energy). Some accommodation providers therefore use it to heat neighbouring buildings. This can be measured by the Energy Reuse Factor (ERF).

Renewable energy supply

Data centres are often criticised for their electricity consumption. While the priority is to ensure that as little electricity as possible is used, it is important to rely on renewable energy as much as possible to limit the environmental impact. This can be measured by the Renewable Energy Factor (REF).

Most hosting companies are focusing on renewable energy. We have based our analysis on the companies’ statements on the proportion of renewable energy used. By way of comparison, the Green Software Foundation’s approach to this (for their Green Hosting Directory which is mentioned by several of the organisations compared here) is rather simple. They distinguish between but take into account organisations that :

• Use only renewable energy
• Invest in renewable energy to offset their own use of non-renewable energy
• Use carbon offsetting

This choice may be debatable (particularly with regard to the inclusion of carbon offsetting). It is up to each individual to see what he or she deems necessary (in terms of procedures and evidence).

It is also important to distinguish between decarbonised energy (e.g. nuclear) and renewable energy.

Finally, claims of “100% renewable energy” can be misleading. It is therefore up to each individual to find out more directly from the companies.

Carbon offsetting

Carbon offsetting is the final step in the process of reducing environmental impacts. It should only be used when emissions have first been reduced as much as possible through sobriety and efficiency. Moreover, the effectiveness of some carbon offsetting solutions is regularly questioned. As there are several ways of offsetting, it is advisable to approach companies to find out more about the precise nature of their approach. In accordance with the recommendations of ADEME and EcoInfo, the notion of carbon neutrality should be approached with caution and avoided as much as possible.

ISO standards, labels, certificates

We look at a number of elements as a matter of priority. These include ISO50001 (energy management), ISO27001 (information security) and ISO14001 (environmental management). In addition to this, we sometimes find the HDS (Health Data Hosting, which includes ISO27001 and ISO50001 among other standards). Finally, the Code of Conduct on Data Centre Energy Efficiency includes many good practices. Greenethiquette is sometimes mentioned, but has disappeared in favour of more detailed standards (such as the European Code of Conduct).

Conclusion 

The notion of an eco-responsible host has been around for several years (notably via the Greenethiquette), but the precise criteria are still under consideration (not to mention what one is entitled to expect from it). Even if some companies are very transparent on their websites (notably via dedicated pages), this cannot replace a more in-depth discussion, both to find out about missing criteria and to better understand the actions already taken. It is therefore to be hoped that hosting companies will move towards concrete criteria to demonstrate their environmental impacts and communicate them in a transparent manner.

For the time being, it is to be hoped that this reading grid will be useful for those who wish to move towards more environmentally friendly accommodation offers, but also so that everyone can be in a position to push companies towards more virtuous actions.

Laurent DEVERNAY

Laurent Devernay Satyagraha has been an expert consultant at Greenspector since 2021. He is also a trainer, speaker and contributor to the W3C’s Web Sustainability Guidelines, INR’s GR491, greenit.fr’s 115 best practices and various working groups, notably around the RGESN.

ldevernay.github.io/

When we are interested in digital sobriety, the question of the host comes up very often. Indeed, this is a very interesting and cross-cutting lever for reducing the environmental impact of digital services. Things get more complicated when you try to sort out the real from the fake in order to choose the best possible host according to the project’s business constraints. Some providers go so far as to talk about carbon neutrality or even carbon negativity.

Claims of carbon neutrality are most often based on the source of the electricity used according to a market-based (supplier’s claims) or location-based (geographical energy mix) approach. Given that some of the scopes 1, 2 and 3 are often neglected, all of this makes these claims invalid. The purpose of this article is not necessarily to go into this point in detail, but you will find some initial answers here:

• [Youtube, 24min 16s] Carbon footprinting tools for public clouds, a presentation by Pierre Rust from Orange Innovation
• Carbon neutrality’ for digital companies, by EcoInfo

Today, in all cases, the claims of eco-responsibility of hosting providers are mostly based on PUE (Power Usage Effectiveness) and the source of the electricity used. This does not seem to be enough. At Greenspector, we decided to look into the subject, to see what was being offered today and to base ourselves on the existing literature in order to determine what criteria to use to choose a hosting company. We were then able to classify several French (or nearby) hosts.

In this first article, we decided to evaluate the homepage of their sites from the point of view of digital sobriety, in order to check whether they reflect their environmental claims. This approach is of course biased and unrepresentative, but it already gives an idea of where each of them stands from this point of view.

It is only with the second article that we will really be able to decide between the hosts, by sifting through the criteria we have chosen.

Comparison of home pages

Based on their intentions regarding environmental impacts, 21 accommodation providers were selected. We have selected as a priority those that show efforts to reduce the environmental impacts of the services they offer. We may have missed some. If so, please let us know!

Based on this list, we measured the homepage of each with the Greenspector tool in order to compare them.

Résultats des mesures sur les pages d’accueil

Now let’s look in more detail

In terms of the Ecoscore (whose calculation methodology can be found on the Greenspector blog), the Webaxys home page does best and Infomaniak does worst. For Infomaniak, this can be explained by the fact that the energy impact of the site is very high. It is even the highest in the sample. On the other hand, from this point of view, it is once again Webaxys that comes out on top. Empreinte Digitale presents the lowest volume of transferred data while Sostradata transfers the most (more than 17 MB!). Concerning HTTP requests, the home page of Empreinte Digitale uses the least while the one of OVEA has the most (at first sight, some optimizations would be quite easy to implement by avoiding duplicates and by delaying the loading of the chat or even by questioning its relevance).

The home pages of the Webaxys and Empreinte Digitale sites clearly stand out and we will now analyze them in more detail. We will then complete our analysis with a quick look at the elements of the Infomaniak site that make it more impactful. We’ll finish with a brief overview of the other sites.

Empreinte Digitale

This homepage is particularly light, which is an opportunity to note the application of several good practices:

• Optimised and lazy-loaded images
• Third-party services mastered and, in principle, all self-hosted
• Very little JS and CSS
• Use of system fonts only

The site is pleasant and attractive. The score could be even better without the animation but this is absent on mobile. The choice of dithering for some images highlights the desire to produce a site as light as possible but is not necessarily necessary.

Webaxys

We find here light and lazy-loaded images, with a simple and attractive service.

On this type of very optimized and light site, some flaws stand out even more, especially the use of Google fonts.

Here we see 7 requests only for these fonts whereas a system font would probably have been suitable. It should also be remembered that their use from Google servers may pose a problem with respect to the RGPD. A variable font could limit the number of files and a subset (limit to useful characters) could reduce the size. But the priority would be to use a system font.

Finally, the last request of the list is probably FontAwesome. So here we get an icon font while only a few icons are useful (and could be integrated in optimized SVG, maybe even directly in the HTML).

Infomaniak

The Infomaniak site stands out for its low Ecoscore and high energy impact.

If you take a closer look, you’ll notice that most of the weight of the page is due to numerous JS files (about forty in all!).

In addition, the animation at the top of the page (for the search of a domain name) seems to be one of the causes of the overconsumption of energy, highlighted in the Greenspector tool:

Other possible explanations for this over-consumption may be found in JS processing. In any case, it should be analysed and limited.

Other websites

Greenshift’s homepage shows a low energy impact, despite the inclusion of animations when the page is loaded. However, in terms of usability, the presence of horizontal scrolling on mobile phones is not ideal.

For the Sostradata site, which has the highest volume of data transferred in the sample, a quick glance reveals the first areas of improvement:

• Avoid including a Google Maps component directly on the homepage
• Optimise images (size, format, quality, lazy-loading)

Good practice in digital sobriety

In terms of good practice, it is worth noting that the Neutral IT homepage meets the most criteria.

From this point of view, we found that some good practices are almost never implemented on the pages in our sample. To improve impact, one should systematically consider :

• Do not let the browser resize images, this limits the consumption of terminal resources
• Only download the necessary images and do lazy loading
• As far as possible, do not integrate css and js code into HTML files; this will avoid systematically reloading the whole file if necessary
• And of course, once the css and js files are independent, they should be minified to save space

Best practices for accessibility

In addition to measurements and verification of good practices (two complementary approaches that are difficult to separate), we were curious to briefly evaluate the selected sites from the perspective of accessibility. While it is important to reduce the environmental impact of digital services, this cannot be done without ensuring that the site adapts to all contexts of use so as not to exclude anyone. What is the point of having the least impactful site possible if it is unusable for a part of the population?

As we do not wish to be exhaustive, we have relied on the aXe tool (it should be remembered that this type of tool is not intended to cover all the WCAG or RGAA criteria) and on the manual verification of certain criteria (200% zoom, content linearisation, textual alternatives, etc.) In accessibility as in digital sobriety, there is no magic wand!

In the end, our findings are as follows:

• The Eolas and Empreinte Digitale websites have the fewest accessibility errors
• Despite its reduced environmental impact, the Webaxys site has several errors that are fairly easy to fix.
• The Infomaniak site is among the sites with the most errors
• Among the most frequent errors, we find mainly those highlighted by the WebAIM Million study (which is consistent):

So here we see (once again) that accessibility and digital sobriety are linked. It would be difficult to say that those who do not take care of the sobriety of their websites do not care about accessibility (and vice versa). On the other hand, it is important to remember that it will be all the easier to apply accessibility criteria to a sober site, and even more so when the two approaches are carried out jointly throughout the project’s life cycle.

Conclusion

A first quick analysis of the websites of the selected hosting providers allows us to distinguish those who make the effort to create a sober (and accessible) site. While this does not indicate that they are paying attention to reducing the environmental impact of their hosting offers, it will be interesting to see if the trends noted here are confirmed later.

In the next article in this series, we will look at the criteria needed to assess the environmental responsibility of a web host. We will return to the websites of the selected hosts to see how each one measures up against the criteria in question.

Laurent DEVERNAY

Laurent Devernay Satyagraha has been an expert consultant at Greenspector since 2021. He is also a trainer, speaker and contributor to the W3C’s Web Sustainability Guidelines, INR’s GR491, greenit.fr’s 115 best practices and various working groups, notably around the RGESN.

ldevernay.github.io/

When we browse the web, autocompletion is almost everywhere. In particular, this functionality is implemented on search engines, whether they are website-specific or not. So, when the user types in the words they are looking for, suggestions are made dynamically, whether to complete the words or phrases they type in or to display the search results as characters are added. 

In the case of Google, these suggestions are often derided as incongruous.  Not to mention the SEO chestnut about the death of the search engine.

Take the example of the Google search engine: 

Here, the blue arrows represent character inputs and the black rectangles represent autocomplete queries.  

We arrive at a total of 16 XHR type queries for 5.1 kb transferred.  

The number of queries remains the same whether the input is fast (input in 2 seconds for the whole search) or longer (7 seconds in total for the input). 

Autocompletion can also be found in some input forms, to ensure that the text entered corresponds to what is expected (city, country, etc).   

While this mechanism can be an aid to the user, the environmental impact of the queries generated should not be overlooked. Let’s see how to limit them.

First recommendations 

If sobriety is a priority, the best thing to do is not to integrate an autocomplete mechanism. However, input help is a definite advantage for users in most cases. 

In the case of forms, the GreenIT.fr collective’s collection of 115 good practices in web ecodesign recommends input assistance. In this way, less strain is placed on the server while ensuring that the text entered remains consistent with what is expected. 

On the GR491 side, there are two recommendations:   

• Limit unnecessary searches by local search engines: this is based on the number of letters entered in order to space out the queries  
• Limit the number of requests between the client and the server: this more general good practice applies perfectly here  

Rather than systematically implementing autocompletion and search, it is sometimes possible to make filters (and sorting mechanisms) available to the user.   

With these initial elements in mind, let’s look at how we can go even further.

Recommendations  

Ensure that requests are as light as possible   

When the client sends a request to the server, ensure that it contains only the elements necessary to provide a relevant response.   

When the server sends a response, again ensure that :   

• Only relevant fields are returned. For example, it is not always necessary to display an image for each result  
• Only the necessary elements are returned (relevance of responses and pagination of results)

Do not offer autocompletion before a few characters  

Before launching the first query, it is preferable to wait until 5 characters have been entered or at least 2 seconds have elapsed since the last entry by the user.   

This avoids returning results for a request that is too vague (when the number of characters entered is insufficient), while taking into account the case where the term searched for is deliberately short (“summer”, etc).

Spacing out the queries in time  

After the initial query, wait until 3 new characters have been entered or at least 2 seconds have elapsed since the last query. 

Limit the number of queries for fast entries  

In addition to the previous rule, in the case of fast input, wait at least one second between each request. Indeed, some particularly fast users can enter a character every 200 ms. 

Measuring local relevance  

When a user adds characters to his search, the results become more precise and their number decreases. It is possible to perform this filtering directly locally, without additional requests to the server. For example, if results were obtained for “housing assistance”, it is possible to filter on the client side if the user continues by typing “housing assistance”.   

This good practice is particularly relevant in the case of an input field in a form. For example, when entering a city or country, the elements of an initial query can be refined locally as the user continues to type.  

Be aware that if a space is entered and new terms are added, the logic chosen for the search results must be taken into account. In particular, should a result contain all the terms entered or only some of them?  

Be careful also to take into account the case where the user deletes some of the characters entered. You may also want to temporarily store the queries you have already made so that you can use them again if necessary.

Back to the example of the Google search engine  

Taking the case of the Google search engine mentioned at the beginning of the article (16 queries, 5.1 KB transferred), we arrive at 3 queries in total for 1 KB transferred.

• A first query only performed when at least 5 characters have been entered.   

• A second query when 3 more characters have been entered.   
• A third query when 3 more characters have been entered.   
• The local evaluation of the results to be returned at the end of the input, since it is only a question of filtering the results obtained following the third query.

Conclusion  

If autocompletion is a necessity and assisted input is not possible, the following good practices should be implemented:   

• Ensure that queries are as light as possible  
• Do not offer autocompletion before a few characters  
• Spacing out queries over time  
• Limit the number of queries for quick entries
• Measure relevance locally

Finally, although this input help may be beneficial to many users, do not neglect its accessibility. 

Laurent DEVERNAY

Laurent Devernay Satyagraha has been an expert consultant at Greenspector since 2021. He is also a trainer, speaker and contributor to the W3C’s Web Sustainability Guidelines, INR’s GR491, greenit.fr’s 115 best practices and various working groups, notably around the RGESN.

ldevernay.github.io/

The discovery that digital technology was not so virtual and that it could have an impact on the environment brought a multitude of injunctions followed by a multitude of criticisms and counter-injunctions. “You have to delete your e-mails”, “No, it’s like peeing in the shower, it’s useless”… The criticism of these actions by the digital actors is quite strong relative to the large part of the “non-technical” population that took this to heart (and increased its eco-anxiety!). 

These discussions have also led to a decision on which is the most polluting between use and manufacture. Use of the mail versus manufacture of the terminal on which the mail was read. The latter being announced as more impacting, this was in the sense of uselessness to optimize the mail part!  

Yes, the impact is concentrated on the manufacturing of the terminals. Yes, the unit impact of an email is low, especially compared to a raclette (this is a private joke, a joke that circulates among the detractors of digital sobriety). These are quite reassuring messages in a binary world. Reassuring to limit eco-anxiety. But mostly reassuring for the digital actors to not deal with the problem and continue business-as-usual.

Because yes, there is a potential problem. Because of the scale effect, a low unit impact can lead to a high global impact with a large number of users and more and more uses. The 4% impact of digital technology does not just happen. Especially when you list and observe what happens on the internet every minute https://www.allaccess.com/merge/archive/32972/infographic-what-happens-in-an-internet-minute. A diversity and a frequency much more important than raclette (for information, we should eat raclette 12 times a year https://journal-des-etudes.com/selon-la-science-il-faudrait-manger-de-la-raclette-12-fois-par-an/ ) 

The plastic packaging of our food, taken individually, does not have a huge impact. A few milligrams of plastic. But plastic is indeed a global environmental problem. As Gerry McGovern would say, plastic is an environmental plague but if you have a plastic bag, use it! https://gerrymcgovern.com/books/world-wide-waste/exploding-plastic-inevitable/ 

“Avoid plastic packaging. Bring your own bag and avoid the barcodes. Whenever you can replace plastic with another material, do, but don’t replace it simply for the sake of it. If you have a plastic bag, use the hell out of it.” 

As a digital player, we need to work on impacts because the effect of scale means that our solutions have a significant global impact. Using the “order of magnitude” argument by taking only the unit impact is not valid.  

Behind an email, there is a solution provider. Behind a social network, too. Each digital actor contributes to a brick that is ultimately used by a user.  

It is therefore necessary to optimize our solutions, to offer better management of solutions. What about smart email deletion options that would be proposed in email solutions? What about providing solutions to help writing sober emails (attachments, signatures…)? It is possible, editors have done it for spam management, why not go further? 

As for user awareness, it is necessary but it must be less anxiety-provoking, without becoming whataboutism (https://fr.wikipedia.org/wiki/Whataboutism).  

Olivier PHILIPPOT

Digital Sobriety Expert
Books author «Green Patterns», «Green IT – Gérer la consommation d’énergie de vos systèmes informatiques», …
Speaker (VOXXED Luxembourg, EGG Berlin, ICT4S Stockholm, …)
Green Code Lab Founder, ecodesign software national association

In 2020, we published a study on digital sobriety requirements in public procurement. With the publication this summer of the decree n° 2022-1084 of July 29, 2022, we thought it would be a good idea to take stock of the sites of cities and communities.  
This decree concerns municipalities and communities of more than 50,000 inhabitants, requiring them to develop a responsible digital strategy focusing in particular on reducing the environmental footprint of digital.  
We therefore remeasured the sites of the 29 cities and 17 metropolises already discussed in order to compare the results obtained.
The measurements here only concern the first page of each site. Ideally, a larger sample of pages should be taken into account, or even compared on the basis of a user path common to all these sites. However, this approach already allows us to establish points of comparison and to identify some good practices. 

Metropolitan sites

The Ecoscore as defined by Greenspector allows a good overview of each site. We will therefore start by looking at its evolution between the initial measurements and the re-measurements.

In most cases, there is an improvement (even slight) in the EcoScore. The cities of Brest, Grenoble, Nice, Orleans and Strasbourg stand out with a very strong increase. For some cities, the trend is downward.  

While Nancy had the best EcoScore (74), Rennes takes the lead with an EcoScore of 80. 
However, it can be estimated that it would be important for each city to obtain an EcoScore of at least 50/100, which is still not the case for some.  

Estimating the environmental impacts of different sites is another good basis for comparison.

We note here that the trend is globally upward for the measured sites with sometimes a strong difference between the initial measurement and the remeasurement. The case of the Saint-Etienne metropolis illustrates this very well.

Further analysis of selected sites

This site appears very light.  The images, even if they are rather numerous, are light but should be lazy-loaded (load them only when they are displayed).  The use of a variable font would limit the requests. The carousel on the home page does not bring much. The fact that it is in autoplay may lead to overconsumption in addition to potentially causing accessibility problems.  The Accessibility page would be more relevant if it stated the compliance with the RGAA (Référentiel Général d’Amélioration de l’Accessibilité) and presented the multi-year accessibility plan for the site.  The few animations, even if they are not intrusive, seem superfluous and can lead to overconsumption.

Following the remeasurement, the site of the metropolis of Montpellier is the least well placed. Leaving the site open, we quickly observe more than 300 HTTP requests for more than 30 MB of transferred data. Even after the site is loaded, the requests continue to accumulate.  

The homepage is particularly heavy, especially in terms of content: lots of images, autoplay carousels, lots of third-party services.  

If quick gains are possible through technical optimization, in-depth work is required, particularly through a more sober approach to design.

Summary of measures for metropolitan websites

We have calculated the average of these data. On the general level we notice that the average ecoscore is 50, the energy consumed is 5,65 mAh, the percentage of CPU used is 2,16, the data exchanged is 6,25 MB, the RAM used is 704 MB, the number of requests is 103. Concerning the environmental impact we can observe that the carbon impact is 0,51 gEqCO2, the water footprint is 0,070 Liters and the soil footprint is 0,68 m2.

By distinguishing the measurements from the remeasurements here are the averages that we obtain:

City websites

Here again, we start by looking at the EcoScore of the sites of the cities in the sample.

Even more than for the metropolises, the trend for the EcoScore is clearly upward.  

In addition to the site of the city of Rennes (already discussed in the context of metropolises), the sites of the cities of Le Havre, Lille and especially Strasbourg have improved significantly. It is also the site of the city of Rennes that presents the best EcoScore. We note in passing the interesting choice of having the same site for the city and the metropolis. As for the lowest EcoScore, it goes to the site of the city of Tours.   
Now let’s look at the environmental footprint of these sites.

The overall trend is downward, which is a very good thing.

Further analysis of selected sites

Even if this site has evolved well since the first measurements, there are still areas of improvement to explore.  

Many HTTP requests, several MB of data exchanged and some 404 errors among the resources to recover.

We note here in passing the interest of having an HTML 404 page as light as possible because this is often what the server will return if it does not find what is requested. Note that it is possible to modify this via the server configuration in order to send a simple message instead. The best thing is of course to make sure that you don’t go looking for elements that cannot be found. 

The homepage is very busy, with an auto-scrolling carousel and many images and content.  Il serait avantageux d’utiliser une font variable et d’éviter de charger toutes les icônes de FontAwesome.  Some images, weighing several hundred kb, should be optimized.

In a rather classical way, there are many images here, some of which should be optimized.  

However, at first glance, the home page does not seem so busy. It is therefore necessary to dig a little to better understand what makes the site so heavy.  
We find about ten queries for fonts and we note in passing Google fonts (which can, let’s remember, cause concern with respect to the RGPD).

Several requests also seem to correspond to video. But most of the requests come from JS and CSS files. A closer look at the domains of origin of the requests reveals one of the explanations for the weight of the site. A closer look at the domains of origin of the requests reveals one of the explanations for the weight of the site.

This firework is provided by the RequestMap tool developed by Simon Hearne (already mentioned during the analysis of requests from an Android application). If we don’t have the details, we can see that there are many requests and that most of them come from other domains.  
The Domains tab of Webpagetest allows us to learn a little more:

This is only an excerpt but it shows several interesting elements:  

Most of the requests (in terms of numbers but also in terms of weight) come from other domains 
Most requests came from mobiledition.com 
Mobiledition.com proposes to those whose site is not responsive to generate a version of their site specially thought for a display on mobile. The intention is not bad but the approach is rather aberrant from the point of view of ecodesign. Indeed, this overlay will exist on top of the original site and will be automatically refreshed at each update of the site. Nearly 10 years after the appearance of the notion of responsive design, it would be important that all sites can adapt to different devices or even that they are thought mobile-first (first for mobile and then extend to other media). Or even offline-first in order to be able to cope more easily with degraded connections.  
In summary, it would be important to rethink the site in order to limit as much as possible the use of third party services to make it less impactful.

Measurement results for the cities’ websites

We have calculated the average of these data. On the general level we notice that the average ecoscore is 49, the energy consumed is 5,57 mAh, the percentage of CPU used is 2,22, the data exchanged is 6,36 MB, the RAM used is 689 MB, the number of requests is 99. Concerning the environmental impact we can observe that the carbon impact is 0,50 gEqCO2, the water footprint is 0,069 Liters and the soil footprint is 0,668 m2.
By dissociating the measurements from the remeasurements here are the averages that we obtain:

The initial measurements were conducted on a Samsung Galaxy S7 smartphone running Android 8.

The remeasurements were performed on a Samsung Galaxy S9 smartphone running Android 10. The measurements were performed through our Greenspector Benchmark Runner tool, which allows automated tests.

Detail of the scenarios :

• Loading the application
• Reading the website in foreground
• Reading the page with scroll
• Inactivity of the website in background

Each measurement is the average of 3 homogeneous measurements (with a low standard deviation). The consumptions measured on the smartphone connected to a wifi network can be different when the smartphone is connected to a wired network. For each iteration, the cache is cleared beforehand.

Discover how Greenspector evaluates the environmental impact of digital services.

Valentine Candela

Valentine CANDELA is in charge of communication at Greenspector since October 2022. Graduated with a Bachelor’s degree in Marketing and Communication, she specializes with us in communication

Today, we are studying the impact of solutions allowing the implementation of websites without knowledge of coding. Among these solutions, we can include CMS (Content Management System) but also No Code solutions.

This article is the first in a series where we analyze the measurements of 1500 sites through our tools.
In these articles, we will deal with the impact of technologies, and parameters…

How are CMS and No Code solutions positioned?

Ranking of CMS according to the median value of energy.

We find the most widespread technologies (according to Web Core Vitals), apart from Shopify (these sites must be classified in the “No CMS” category).

We observe a 20% difference between the most efficient solution (Ametys) and the least efficient (Webflow).

Three CMS are positioned ahead of sites without CMS. Popular CMS like Drupal and WordPress are lagging behind. The last four solutions are No Code solutions.

There are many outliers in some categories (WordPress, sites without CMS). It is explained by a large data set (several hundred sites). An exploratory analysis of these sites generally shows that they are sites with fairly heavy streaming processing (such as video). Here is an example of a site positioned in “outlier“ the loading and idle stage (inactive site) consume a lot given an animation that runs continuously.

Quelques pistes d’explications à l’analyse des CMS :

Ametys: a domain-specific CMS

Ametys is a specific CMS which is used for institutional sites. Our ranking of school websites, in which many schools use this technology, explains its presence in this ranking. Its good positioning would have to be analyzed from a technical point of view. However, we can deduce that a solution that targets a type of need will be more optimizable than a generic solution. The integration of multiple functionalities in a CMS will indeed lead to overconsumption. We also observe that these institutional sites include fewer modules than the other sites. It is ultimately about functional sobriety.

Squarespace: an all-in-one solution

Squarespace is a publisher-hosted CMS. On the sites analyzed, we can identify there are few requests (<30), so there are potentially integrated optimization solutions. In other tracks, all the resources are hosted on Squarespace, and the assets (or assets) are on dedicated servers. The hosting of the CMS by the publisher is indeed a good thing because it will allow systematic and shared optimizations. However, this is not necessarily native. The editor must apply it.

Typo 3: native optimization options

Typo 3 which is an open source solution is in 3rd position. An HTTP Archive ranking is confirming this positioning. Fine cache management and native optimization options explain this performance.

Drupal: a professional CMS

Drupal is positioned just after sites without a CMS. The good positioning of this CMS is explained by its less accessible setup and start-up process than WordPress.

Contentful: a headless CMS

Contentful is a “no interface” CMS. It allows you to publish content from other tools. The efficiency gain is present for the publication (because we do not use our usual tools). However, we observe that this CMS is just as efficient as a classic CMS.

WordPress : un CMS simple et très répandu

The WordPress platform is very popular and offers many plugins and themes. But genericity and modularity come at a price. Non-technical users can use this CMS. A potential explosion of plugins and non-configuration of the CMS in terms of performance and efficiency are the counterparts. We see in relation to the low moustache that the CMS can be efficient. However, this requires a lot of work.

Wix, Webflow, SiteCore, Adobe: No Code or equivalent solutions

These solutions offer the user the possibility of creating a website without coding knowledge. The median is high. The low whiskers are also higher than other solutions. It shows that they are heavier solutions.

Conclusion 

From a statistical point of view, CMS solutions do not all have the same efficiency. The initial design, taking into account optimizations, will be essential to achieve good performance (case of Typo 3). We observe that end-to-end control, combined with good practices implementations (Squarespace), also makes it possible to achieve a good efficiency level. In the same way, specializing in a CMS (Ametys) and therefore the options that go with it will allow you to obtain good results.

However, on the other hand, making a very generic and modular CMS (WordPress), even if potentially efficient initially, will bring bloatware. In the same way, the No Code will add a heaviness. It remains to identify the causes of this heaviness. Indeed, it can come from levels of abstraction but also from rendering possibilities (interactivity, animations, etc.) which are easily possible and which lead the user to add more than is necessary. In addition, the use of a “generalist” CMS is also potentially representative of a lack of precision in the need.

For a CMS solution (and more generally any solution), sobriety will not be innate. It will be necessary to apply a set of good practices:

Do you want to include a CMS in this ranking? Contact us and send us at least 20 links to sites using technology, we will integrate them into the measures and within our ranking!

For our next article, we will go into the finer analysis of WordPress data to observe which parameters and configurations influence environmental performance.

Olivier PHILIPPOT

Digital Sobriety Expert
Books author «Green Patterns», «Green IT – Gérer la consommation d’énergie de vos systèmes informatiques», …
Speaker (VOXXED Luxembourg, EGG Berlin, ICT4S Stockholm, …)
Green Code Lab Founder, ecodesign software national association