Category: Applications sobriety

The Impact of playing a Canal + video study

Reading Time: 16 minutes



This study was carried out by Greenspector, a company specializing in the impact of digital technology, and EVEA, specializing in analyzes of the environmental impact of products. This study is based on:

  • a calculation methodology initiated as part of the CONVINcE project on the energy consumption of video. A project involving several players such as Orange, Sony …
  • energy and resource consumption measurements carried out on the myCANAL application to support hypotheses
  • collection of data on the use and infrastructure of Canal +
  • a bibliographic study to identify and correlate emission factors and energy consumption

Study summary :
Results : consumption, overall impact and projection
Areas for improvement
Conclusion – points to remember
Chief Digital Officer – Canal+ testimony


The functional unit of this study is defined as follows: “Watch 1 hour of video, live or in a replay, on the Canal + interfaces”.

Disclaimer: The purpose of this study is to estimate, by orders of magnitude, the carbon impact of playing a video on Canal + interfaces. To date, it is based on reliable and robust sources and is intended to be representative of the reality of the Canal + infrastructure. However, this is not a complete Life Cycle Assessment (LCA). We rely on LCA methodologies but, for example, we have not performed a sensitivity analysis that would allow min-max deviations on the values. However, this study made it possible to formalize an analysis benchmark for the carbon footprint of a video service, and it could be used to monitor the evolution of the carbon footprint over time. And all this in no way detracts from the consistency of the data for its primary use.

Means of access to services

We have listed different ways to access myCANAL video services. Depending on this type of access, it is necessary to have more or less material (s). This inventory is needed to assess the impact of accessing video services. We have classified the means by category:

  • Canal + decoder
  • FAI TV Box
  • TNT Box
  • Game console
  • IP TV (Android TV, Samsung TV)
  • PC / Mac Multimedia Gateway with ISP Internet Box
  • Smartphone / Tablet with ISP Internet Box or GSM access

For Decoder, TV / TNT Box, Console, and Multimedia Gateway access, it is necessary to add a TV. We have ruled out all special cases of viewing considered as anecdotal compared to other accesses such as:

  • Display of the PC stream on a TV,
  • Multiroom viewing

Regarding the link between the terminals and the Boxes, we will consider that the Wi-Fi connection and the wired connection (Ethernet) have no impact on the consumption of the terminals (PC and TV).

Definition of visualization

Visualization quality influences end-to-end power consumption. We have taken the following 3 main definitions:

  • SD (Simple Definition)
  • HD (High Definition)
  • UHD / 4K (Ultra High Definition)

The definition depends on 3 factors:

  • compatible program availability
  • material compatibility in terms of quality
  • the quality of the connection (the quality of myCANAL videos is adapted according to the connection speed).

Greenspector’s exploratory measurements on myCanal show the impact of SD, HD, or UHD video consumption on smartphones, and then on laptops:

Impact of consuming SD, HD or UHD video on smartphones and laptops

Bibliographic sources were used for the consumption of other platforms such as Consoles (Source 1), TV (Sources 1 and 2), Set-Top-Box (Sources 1 and 2). The consumption of Canal + decoders supplied by Canal + was also used.

Depending on the different equipment configurations, we obtain energy consumption which varies from 1.3 to 108 Wh / h, i.e. a ratio of 1 to 80:

Consommations d'énergie selon les configurations d'équipements


Several parameters were taken into account in the calculations because they influence the consumption:

  • Streaming technology: IPTV (Technology among ISPs), OTT (Over the Top), and Peer To Peer
  • Linear (Live) or Non-linear (Replay / VOD) signal
  • Broadcasting (Hertzian, Satellite, IP)

Means of connection to the network

To access the services, the infrastructure considered takes into account: the user’s equipment (Box among others), access to networks (GSM, Fiber, etc.), and the heart of the IP network.

We used calculation methods that are widespread in the scientific literature and standardized by ETSI. The principle is to take an “energy / typical use” ratio in Wh/Go. Although the network infrastructure has a fairly fixed consumption and does not depend on the use, this calculation method makes it possible to assign a global impact to a use (here one hour of video). In addition, it allows to study the improvement of networks in terms of efficiency. Beyond the search for improved energy efficiency, it also makes it possible to assess pressure on the network and to take into account the improvement in the capacity of the infrastructure.

As explained in the CONVINcE report:

“As we are looking for an order of magnitude in energy saving, we suppose that decreasing by 30% the traffic volume in the core network induces a decrease of same ratio in network dimensioning and consequently a decrease of 30% in energy consumption in the core IP network.”

We have studied the literature and listed metrics ranging from 1.3Wh / Go (figure for FTTH fiber) to 600Wh/Go. These factors fluctuate depending on the infrastructure assessment date, method (Top Down or Bottom Up) and technology. It is clear, however, that the efficiency improves over the years.

We have taken:

  • 13 Wh / Go for the core network (source CONVINcE)
  • 30 to 40 Wh / Go for the fixed network
  • 150 Wh / Go for the GSM network (source CONVINcE)

For TNT and satellite, there are few data. However, we based ourselves on a BBC study for TNT.

Content Delivery Network

Content Delivery Networks (CDNs) are servers used to limit the load on “Top of Head” servers (serving videos) and to provide a flow as close as possible to the user. Canal+ uses CDN providers on the market but also uses its own infrastructures.

The methodology for estimating the energy intensity per GB is to bring the estimated consumption of the data center down to throughput during peak periods. Canal+ indeed knows the number of physical servers, their types as well as their speeds. As the servers are hosted by a host, certain assumptions have been made to estimate the actual consumption: among other things, an assumption of PUE (Power Usage Effectiveness) of 2, consumption per server of 250W, and a server load of 50%. The consumption of routers and storage is considered negligible compared to the consumption of servers. (Sources 1, 2 , and 3)

The energy intensity obtained is 0.13 Wh / Go, with a different value between VOD and Live. Note that this value is calculated in the event of a peak (football match for example). It can be lower (use of the total capacity of the data center) or higher (during periods of low traffic).

For lack of data, the hypothesis of the same energy intensity (Wh / Go) was taken for CDNs outside Canal + (50%). For comparison and verification, the studies listed display values from 0.04 to 1 Wh / GB. These differences can be explained by various factors:

– Improving the efficiency of data centers, old studies, therefore, lead to higher figures,

– Top-Down approaches that have a higher estimate than Bottom-Up studies (like this estimate on CDNs).

AWS application servers Excluding video: using Mycanal (catalog presentation, authentication, etc.) and watching videos involve requesting services hosted on servers (rights management, etc.). The APIs used are hosted on AWS instances.

Canal+ rents AWS instances and knows the number of VMs. A part of these VMs is purely dedicated to providing ancillary services to video.

It is difficult to know the power consumption of AWS instances because no communication or information is provided by Amazon. According to an expert, we took a value of 20W (taking into account a PUE of 2) (Source: Interview of experts on virtualization from the company Easyvirt).

We have assumed a uniform distribution of consumption concerning the number of hours visualized and we obtain a value of 0.14 Wh / h.

Video encoding servers

The “Headend” servers allow you to format videos, “package” them to the user’s format … For the OTT, up to 150 packages may be available for a single video. Here is the workflow for the OTT.

The most consuming parts are video encoding and decoding. The workflow is distributed over specific servers (for encoding) and classic servers (for formatting and packaging).

We took the figures from the CONVINcE project (considering Harmony servers identical to those used by Canal +) to estimate the energy, as well as the Canal + server data:

  • For IPTV: 0.09 Wh for one hour of video
  • For the OTT: 0.30 Wh for one hour of video

This difference is explained by the fact that OTT is encoded in several formats, unlike IPTV which is encoded in a high definition format.

CO² emission factors

For energy, we used the values provided by the Open Data Networks Energies database (Work of distributors such as RTE and ADEME). We used intermittent usage which corresponds more to video usage in terms of the period (evening), ie 60g CO2eq / kWh. Part of the broadcasts for the rest of the world has been added taking into account the fact that some users are outside France.

For terminal and server manufacturing emission factors, we used factors provided by Shift Project / IEA.

These factors were brought to the time of viewing by taking into account the lifespans associated with each material.

Note: Regarding the impacts of DTT and satellite, there is a lack of data on infrastructure and emission factors. However, we have integrated this part to understand the orders of magnitude of the impacts. Certain analyzes were carried out only on the IP part in certain cases (for comparison with other studies for example).

Likewise, the impact of the data center manufacturing phase outside of the servers and the network infrastructure was not taken into account as it was considered to be shared and low given the lifespan of the buildings.

Results – global projection

The supply of renewable energy to AWS infrastructures and Canal + CDNs hosted by Interxion has not been taken into account.

In one hour, on average, here are the flows that pass through the network:

500 000 hours of video
900 TB of data
3.6 GB / hr average throughput

The number of viewing hours for Canal+ subscribers has been broken down according to the parameters listed above.

The unit data obtained previously are then projected on these uses to obtain the overall consumption. By taking these results, we can obtain the usage intensities of each part (Terminal, Network, Server) to check the consistency of the overall consumption.

Intensity analysis

The usage intensities obtained can be compared to the Shift Project and IEA studies. This intensity is calculated by taking the distribution of devices, the use of Canal +, and keeping only the IP transfer part (without Satellite or TNT).

It is clear (and shared by the IEA) that the Shift Project study overestimates grid consumption. For servers, we have a fairly low value but are quite confident considering that it is based on data from a known infrastructure (with the uncertainty from Amazon servers and third-party CDNs). The estimate of the terminal part of the Shift Project seems to us to have been underestimated (shared by IEA). It seems that the IEA also underestimated many parameters and seems not to have taken into account the influence of the definition on the consumption of the terminal, certain elements such as boxes, and the consumption of new TVs that consume more. The CONVINcE study and the Sauber/Koomey analysis also validate the consistency of our study.

Impact of playing an hour of video

Across the Canal+ fleet, the average end-to-end consumption is 214 Wh per hour of video. For comparison, the IEA study announces consumption between 120 and 240Wh per hour. The breakdown is as follows:

The impact in average CO2 equivalent by type of access is as follows (with the assumptions specified in the paragraph CO2 emission factors where the manufacture of Satellite, DTT, network and server hosting infrastructures has not been taken. into account)

By taking the type of connection:

The impact ranges from 20 to 66 g CO2 eq, it depends on several parameters:

  • the more or less energy consumption of the device (for example Smartphone vs TV),
  • embodied energy and material life,
  • the means of access to the network (for example GSM access has a greater impact than wired access),
  • the viewing quality which will influence above all the share of the network (depending on a cost per Wh / Go),
  • the number of materials to access the service.

By taking real uses (see the end of the document), the average is 28g CO2eq. If we take only the IP part, the average value is 37g CO2eq.

For comparison, the IEA study (2020) announces 8g CO2eq for France (for the use phase only). Another study for the US (2014) announces 360g CO2eq on the use phase (and 420g CO2eq with manufacturing). If we take a US energy mix, we get 202g which brings us closer to this study. The lower value can be explained by the differences in assumptions, in particular on the energy intensity of the network. For example, if we take for our study a TV with 4K reception, IEA announces 20g CO2eq while we rather estimate 14g (37g with the manufacturing phase).

If we look at the usage / manufacture ratio, in some cases the use has more impact (UHD in particular), while in others it is the manufacturing (IP TV or PC in HD for example).

In this same study, the estimate of the purchase of a DVD is 400g EqCO2, which therefore leads to the impact of watching a 2-hour video. 5 times less than that of buying a DVD in France and equivalent in the US.

Consumption and overall impact

The result of the total energy consumption of viewing Canal+ videos over IP is 900 GWh per year with a greenhouse gas impact of 159,000 tonnes CO2eq.

For comparison, annual French consumption is 473 TWh per year (Source RTE) and France’s 2017 carbon footprint (national emissions + imports) is 749 Mt CO2 eq (source: Haut Conseil pour le Climat – 2019 report). The consumption of the Canal + fleet by IP is therefore 0.18% of energy consumption and 0.016% of the French carbon footprint.

The end-to-end distribution is as follows:

Most of the consumption is on the user’s premises (terminal and part of the network access). Indeed, it is necessary to have the equipment (TV, Box, Smartphone …) which is not shared like the servers.

To validate the consistency of this projection, we took the consumption of CDNs specific to CANAL as well as to suppliers. We have a consumption of Canal + CDNs of 2.6 GWh (and estimated at 7 GWh for suppliers) excluding video head-ends which are not at Interxion. We get 12 GWh with the projection, which validates the model.

If we look at the distribution of the impact in greenhouse gases, we have the following distribution:

répartition de l’impact en gaz à effet de serre

A large part of the impact comes from the manufacture of user terminals. On the network part, the manufacture of Boxes (FAI, Satellite …) also has a significant impact.

Areas for improvement to limit the impact of services

General strategy

As we have seen in the network part, efficiency improves. The same is true for terminals. But on the other hand, 4K will become widespread, networks will continue to increase their capacity and therefore increase the overall impact of consumption. By taking one of the hypotheses of a 30% improvement in network efficiency (according to the trends set out in the studies listed in the Networks section of this report) and an increase in average throughput of 20% over 3 years as well as of 20% of the hours viewed, as well as a transfer of 75% of the hours viewed from all interfaces to that of the OTT, we estimate an increase in the energy consumed by 39% and the impact of greenhouse gases greenhouse by 23%. This simplistic projection allows us to approach a more realistic consumption in 3 years.

To offset this increase, and optimize the impact of video playback, we examined the impact of the following projects carried out by Canal+:

  1. Switching from H264 encoding to HEVC
  2. Switching to multicast for live
  3. Switch audio encoding from AAC to AC4
  4. Strengthen bitrate downsizing
  5. Improve the interface and the software layer
  6. Help the user on their digital impact

These projects are not exhaustive. Other possible areas for improvement have been identified which could be launched subsequently by Canal+.

The measurements, estimates, and models that allowed us to obtain the overall impact were used to quantify the estimated gains.

Note on optimizing video servers:

The energy consumption of video servers is very low, as is their impact, as the hardware has a high lifespan (10 years). Several optimizations are under study (video passage Just-in-Time among others). However, these optimizations provide very little end-to-end gain. They are however necessary to optimize management and reduce storage size (impact not taken into account in this study because it is low). Optimizations such as switching to HEVC have a stronger impact (this is confirmed by the CONVINcE study).

“The “Just In Time Transcoding” approach will allow to reduce the number of video representations stored in the CDN and thus its power consumption. This is an end-to-end approach to be compared to the global abovementioned one consisting of reducing the bandwidth of the network by using the most efficient encoding technology (HEVC/AVC).

On CDNs in the same way, even if the impact is low, certain actions such as increasing the rate of use of Canal + infrastructures (using a transfer of flows from supplier CDNs to own CDNs) will improve the efficiency.

Switching from H264 encoding to HEVC

The HEVC video codec is about 20% more efficient than the H264, and a large number of devices are now compatible. For a 3-year projection of consumption, we have taken an increase in the market share of HEVC compatible devices (Box, Smartphone, etc.).

For users who are on 1080p 5Mbits to date (34% of users currently) as for users restricted to 720p for technical reasons (for example a limitation of the network), a 20% drop in consumption is expected. For other 1080p compatible users, there is no decrease in consumption, but an increase in quality with superior grip.

A new even more efficient format begins to appear (AV1), saving an additional 20%. However, very rare equipment is compatible: the transition is largely premature, we would hardly gain anything to date because the fleet is almost zero.

Switching to multicast for live

Broadcasting in hybrid multicast / unicast adaptive streaming for the OTT will greatly reduce the use of bandwidth, and therefore power consumption.

Usable only for live stream, it ensures that a single stream is sent for all customers to the final delivery point. This project will be accompanied by other ancillary projects such as the switch to CMAF packaging. The CMAF audio/video packaging format allows you to have exactly the same video files for all platforms.

Switch audio encoding from AAC to AC4

Currently we mainly use AAC audio, from 96kbits to 128kbits.

The EAC3 + is widely compatible to date and improves audio quality at equivalent bitrate while allowing 5.1. Switching to EAC3+ would be at a fixed rate, without hoping to save bandwidth (while 20% more efficient than EAC3 +).

On the other hand, the new AC4 format is 50% more efficient than the EAC3 + and would allow the audio bit rate to be divided by 2. Even if the share of the video is greater, the gains at the global level are not negligible.

Strengthen bitrate downsizing

To date, except in Africa, or on a cellular network (so as not to empty the customer’s subscription), the quality of the video is adequate . On PC, quality adaptation is possible but access is not necessarily easy.

Making the possibility of reducing the size more accessible by different means (improvement of the interface, communication, etc.) would make it possible to redirect some of the users to a lower but sufficient quality.

Taking into account the increase in video quality and that of network performance, quality caping by users of Canal + services should represent in 3 years a gain of 20% in average speed compared to that generated by uncapped use.

In this axis, several elements have not been included in the gain projection but are possible to help the user in his impact. For example, the Greenspector mobile measurements show that it is better (under favorable conditions such as wifi) to use downloading rather than streaming. Indeed, here is the comparison for a 45mn video (with 5mn download):

Consommation d'énergie d'un streaming vidéo vs d'un téléchargement et lecture vidéo

This is partly explained by the fact that when viewing the downloaded video, the radio cell is not used while it is much more during streaming.

Improve the interface and the software layer

Part of the impact of viewing an hour of a video comes from the interface. Indeed, viewing the catalog, managing subscriptions (via APIs), processing playlists … are necessary functions. Greenspector measurements showed that this could represent 10% of terminal consumption:

Improving the interface on all platforms (smartphone, PC, etc.) would therefore make it possible to obtain significant gains. It would also allow, beyond reducing the impact, to limit the exclusion of certain people as well as the obsolescence of platforms.

Among the actions identified:

  • Switch to the dark mode
  • Reduce the overall impact of the software layer
  • Improve UX
  • Limit the integration of third-party libraries

Help the user on his digital impact

Much of the impact of video playback is not directly related to video playback. Canal +, through its large audience, can act by making users aware of the impact of digital technology. If some of the users take these actions into account, the impact can be reduced. Among these actions:

  • Extending the life of the user’s equipment,
  • Use Ethernet rather than Wifi, rather than 4G,
  • Extinction of equipment out of use.


Here is the projection of the various energy gains:

The improvements compensate for the increase in energy consumption and even allow a gain of 14% compared to the current situation. For the greenhouse gas impact, we obtain a gain of 8%.

There are many ways to reduce the carbon impact of streaming activities for Canal + by 30%, and the actions put in place will make it possible to make a gain of 26% on the environmental footprint of services and in particular -31% for the consumption in OTT only.

Conclusion – to remember

This study has uncertainties on future use, on the emission factors of each element as well as on the potential gains. However, the objective is to challenge the choices or even to rule them out (some actions not listed in this document have, for example, already been discarded), if they had no gain. One of the first actions is to be able to measure yourself in order to improve. This is the goal of this phase. Now comes that of improvement.

The environmental interest of the sites identified by Canal+ has been confirmed. Their implementation will make it possible to offset the effects of the growth in uses, or even more, in the years to come.

The conclusions of this evaluation evolve with many technological parameters but in summary:

  • Work on video and audio compression formats while taking into account new formats optimized by manufacturers.
  • Optimize the consumption of user functions to access the content.
  • Involve/guide users in the choices according to the context of use (streaming, type of network, device screen format, etc.) and lead them to extend the life of the equipment to reduce the impact.
  • Implement hybrid multicast / unicast adaptive streaming for OTT to dramatically reduce bandwidth usage and power consumption.
  • Pursue end-to-end measures to avoid future decisions that shift the impact without reducing it

Pierre-Emmanuel Ferrand, Chief Digital Officer at CANAL+


– How does this assessment and improvement process fit into the Group’s strategy?

CANAL+ is anchored in its time. We have decided to become more involved in a major issue of our time, dear to our subscribers and users of myCANAL: the protection of our environment. CANAL+ was very early on as a pioneer in eco-responsible approaches. first. In addition to the rental model of decoders, which is very virtuous from the point of view of the circular economy, Canal+ organized in 1988 the recovery of old decoders to ensure their return to service or their recycling. Moreover, as a publisher, We have produced eco-responsible productions including series that have been exemplary on this subject, Baron Noir, L’Effondrement, and more recently OVNI (S).

-What main lessons/contributions do we draw from this work (on the design of services)?

This work allows us first of all to identify the technical projects to prioritize to minimize the carbon footprint of myCANAL video consumption as much as possible. At the same time, the lessons guide us on the awareness messages to relay to our users, throughout our future developments. This commitment to cooperation between our technical developments and our users is the key to consumption that has less impact on the environment. 

– What role do users play?

Protecting the environment is a priority for them. Their role is central to our approach. Our challenge is to offer them a platform offering the best content and the best video quality adapted to their equipment and their reception capacities to reduce the effects on the environment. By raising their awareness and supporting them in responsible actions, they too will be able to get involved, as they do in other areas for a more eco-responsible society.

Digital sobriety comparison of 3 direct messaging apps for business.

Reading Time: 6 minutes


Today and more than ever, communication is essential in business. Since the start of the Covid-19 crisis, many companies and employees have discovered remote work. This exceptional situation has led to a change in our interaction habits: making teams communicate effectively with each other, remotely, instantly. We decided to compare the 3 most popular direct messaging apps for business: Skype, Slack and Teams.

6 scenarios were carried out on the basis of an average user journey:

– Launch of the application
– Opening of a blank one-to-one conversation
– Sending a text message
– Send an image (.jpg)
– Sending an attachment (.pdf)
– Send an animated image or GIF (.gif)

Consult the methodology and the details of the scenarios.

Carbon impact projection

Carbon impact (graph) of apps: Skype, Slack and Teams

During the application launching stage, the carbon impact of Skype (0.038 gEqCO2) and Slack (0.039 gEqCO2) are pretty similar. Teams exchanges 77% more data compared to Skype, therefore increasing its carbon impact where in terms of energy, the Teams application has a consumption similar to the other two apps.

On the part of sending a text message and sending an image, Slack is the most efficient application oscillating between -30% (message) and -60% (image) less than Skype, less good application on these two scenarios.

Generally speaking, Teams consumes a lot more data. Indeed, on average it is nearly 196 KB where Skype is at 134 KB and Slack is at 113 KB.

The application with the best carbon impact average is Slack (0.035 gEqCO2) followed closely by Skype (0.043 gEqCO2) then Teams (0.055 gEqCO2), a difference of 36% between the best and the worst.

Focus on background consumption

On the background idle side of the application, we notice several things:

Slack consumption in IDLE Background

Slack consumption in the background is higher than the other two apps. Especially in terms of data exchanged where Skype and Teams do not exchange any data in this user step. Slack also consumes in terms of CPU (1.16%) where Skype consumes 10x less and Teams is once again at zero. This consumption is not linked to the background setting (state change processing) but lasts over time both on background inactivity states and in foreground inactivity.

AppsEnergy consumption par second (µAh/s)Exchanged Data (KB)CPU (%)

The Slack app performs processing in the background, impacting battery, power and resource consumption throughout the day. If we project this impact for a user who puts his Slack application in the background on his phone for a whole working day (7 hours), we obtain an impact of 26 gEqCO2, or approximately the Carbon impact of an average light vehicle driven in 230 meters! At the scale of the year (220 days): this behavior for a person is equivalent to 50 km of the same vehicle. Probably a mess that could be taken care of and avoided.

Average carbon impact projection of the scenarios

Carbon impact of direct messaging apps user journeys

The scenario with the lowest carbon impact on average of the 3 applications measured is that of opening a conversation (0.018 gEqCO2) consuming 69% less than sending an attachment (0.061 gEqCO2). The step of sending an image is the second least impactful step with + 10% more than opening a conversation. Finally, sending a text message and loading the app are similar in their impact (less than 1% difference).

Disclaimer : Note that these scenarios do not have the same duration.

Scenarios and their duration (in seconds)SkypeSlackTeams
Launch of the application4,524,135,88
Opening a conversation1,761,828,95
Sending a text message33,331,7832,19
Sending an image15,169,0714,46
Sending an attachment10,1312,1310,99

Below, the ranking of applications according to their carbon impact per second.

Carbon impact per second of direct messaging apps

Projected energy consumption of scenarios over 60 seconds

Energy consumption of direct messaging apps

When it comes to the launch of the application, Skype is in the lead with energy consumption of 31 mAh followed closely by Teams (32.8 mAh) then Slack (35.5 mAh). A difference of 12% between the first and the last application for this step.

For the opening a conversation step, Teams (11.3 mAh) is doing well with a lower consumption of 61% compared to Skype and Slack side by side (29 mAh).

For the 3 scenarios of sending a text message, image or attachment, the ranking does not change: Slack remains in the lead followed by Skype and Teams.

In the end, by adding all the steps, the Teams application is the most efficient (71.3 mAh) followed by Slack in second position (85.6 mAh) then Skype, the last one (86.2 mAh).

Remember that this classification is projected over one minute of use. In real time, Slack is the fastest application (11.7 seconds on average scenario completion time), Teams the slowest (14.49 seconds), however Teams is the most sober in terms of downloading speed on the smartphone (237, 7 on average compared to 285.6 for Slack or 287.2 for Skype).

On average, a minute of writing and sending a text message consumes 3.33 mAh, which is 2x less consumption than a minute spent in videoconferencing (audio only: 6.60 mAh).

Slack vs Teams: send a GIF



For the same functionality of finding and sending a GIF via Giphy third-party, the two applications Slack and Teams have a different user journey.

In fact, Slack allows, with a simple command, the search and display of a SINGLE GIF via the keywords typed then offers the possibility of loading a new one if the first one is not suitable. The command used is as follows:

/giphy simpson

Teams meanwhile, displays a search bar that displays new GIFs with each new letter typed. So unnecessarily. loading dozens and dozens of GIFs. After typing the entire keyword “simpson”, the results window will always display a number. For this scenario, we have chosen to select the first gif from the results.

We therefore observe a difference between the two applications:

ApplicationsDuration of the scenario
(in second)
Energy consumption
Exchanged data
Carbon impact projection

We can see that the Slack user journey is much more energy and resource efficient than that of Teams. Especially for the part of the data exchanged (a difference of more than 22 MB!), Which can be explained by the quantity of GIFs unnecessarily loaded by Teams.

The difference in power consumption between these two apps is 40% for a similar scenario duration. The carbon impact is multiplied by 36 for the Teams application compared to Slack.

For each of its applications, measured on an S7 smartphone (Android 8), the user scenarios were carried out through our GREENSPECTOR Test Runner, allowing the performance of automated tests.

Details of the scenarios:

  • Launch the application
  • Opening a one-to-one conversation
  • Sending a 28 character text message “Hello this is a test message”
  • Sending an image (.jpg): 32 KB (350×350)
  • Sending an attachment (.pdf): 188Kb – generated from a Word text file (A4 format)
  • Sending an animated image or GIF (.gif): GIF used for Slack – 225Ko – 500×375; GIF used for Teams – 600Kb – 500×352

Each measurement is the average of 3 homogeneous measurements (with a low standard deviation). The consumption measured on the given smartphone according to a wifi type network can be different on a laptop PC with a wired network for example. For each of the iterations, the cache is first emptied.

To assess the impacts of infrastructure (datacenter, network) in the carbon projection calculations, we relied on the OneByte methodology based on real data measured on the volume of data exchanged. This assessment methodology takes into account the consumption of resources and energy in use for the requested equipment. As this is a very macroscopic approach, it is subject to uncertainty and could be fine-tuned to adapt to a context, to a given tool. For the Carbon projection, we assumed a 50% projection via a Wi-Fi network and 50% via a mobile network.

To assess the impacts of the mobile in the carbon projection calculations, we measure the energy consumption of the user scenario on a real device and in order to integrate the material impact share, we rely on the theoretical wear rate generated by the user scenario on the battery, the first wearing part of a smartphone. 500 full charge and discharge cycles therefore cause a change of smartphone in our model. This methodology and method of calculation have been validated by the consulting firm specializing in eco-design : Evea.

Integrate a third-party service: is it dangerous for your visitors privacy, which impact on the environment? The Youtube case.

Reading Time: 4 minutes

Third-party service integration makes it easy to quickly add functionality to a site such as a video or social network integration (see the case of Twitter integration). The providers of these tools have worked to make technology integration quick and easy. And the technique is there. But at what cost?

Energy consumption of the third-party service Youtube

We observe an increase in this type of third-party service on our measurements and abnormal overconsumption. This is the case with many sites and even government websites. 

The YouTube integration is a good case study to explain this effect. In just a few lines, it is possible to display a video on any site:

<iframe width=”560″ height=”315″ src=”″ frameborder=”0″ allow=”autoplay; encrypted-media” allowfullscreen></iframe>

But what is the result in terms of user impact? Here is the result we get in terms of power consumption on a Nexus 6 smartphone:

Consommation d'énergie du services tiers Youtube

Reference: Phone discharge speed in uAh / s (OS, Browser …)
Loading: Speed of the first 20 seconds of loading
Idle Foreground: Inactive site speed in the foreground
Scroll: Speed when the user scrolls down the page
Idle Background: download speed when the browser (and therefore the site) is in the background

This is a government website. Discharge rates exceed our thresholds for many steps. For loading, the speed is more than 2 times that of reference. For the idle foreground or phase of inactivity in the foreground, the consumption should be identical to that of reference. This consumption is abnormal for a site that seems quite light.

Process CPU du services tiers Youtube

We see that Chrome’s CPU process goes up to 10% every second. This explains the overconsumption of energy. By profiling the JavaScript calls in the development tools, we observe processes from base.js which are from the YouTube framework:

Javascript framework Youtube

Note that this processing also impacts scrolling and loading. Is this an expected operation? A bug or a bad implementation? We haven’t been that far into the analysis.

When we look at the page loading, on 1.2MB, nearly 600KB is used for the YouTube plugin. 50kb of CSS and 550kb of Javascript. To the necessary processing, add the heavy CPU usage to parse and run scripts.

Significant point: No video appears on this page. The integration of the plugin is surely necessary for another page. This makes the waste even more critical, it is all the more annoying that the French tested website is public and widely used: Impots.gouv !

Best practices for integrating a video

1 – Directly embed video without third-party services

It is possible to use free solutions without plugins. Integration via HTML5 is native.

2 – Embed an image

Display an image with the same rendering as the video allows to reduce to 1 request. If the user clicks on the video, then the scripts will be loaded and the video launched ultimately lazy loading.

We also did the exercise on a page of our Greenspector website:

On one of our “Case Study” pages was embedded a YouTube video. We replaced this integration by displaying an image (opposite) representing the old integrated video. This modification allowed us to go from a Greenspector ecoscore from 59/100 to 75/100 characterized by an energy gain of -12% in the loading stage, -10% in Idle and -15% in scroll.

Page with embedded video
Page with image

3 – Integrate the plugin only on the desired page

A solution that is not ideal, but preferable to the existing one, is to only use scripts when the page requires a video.

What will it save?

First of all the performance. A large portion of processing related to site wait times is dedicated to third-party services. This is even more true for the YouTube plugin. On the audited site, the size can be reduced by 2, and the loading time reduced by at least 30%.

Power consumption will also be reduced and even more important than data size or performance. In fact, in addition to saving energy from charging, consumption in idle or inactivity phase will be reduced.

Bonus: user privacy

The other problem with this type of project is the use of tracker and user data recovery. Not integrating a third-party service resolves potential issues of data leakage and GDPR non-compliance. By the way, the YouTube plugin seems to allow version without cookies via the call to the URL:

Like any third-party service, it is not that simple. Even with this no-cookie integration, user data is stored:

Données utilisateurs cookies Youtube

The audited site is therefore not GDPR compatible! To manage this, you must ask the user for consent explicitly:

Fenêtre de consentement

The solution of a hosted video or static image will also manage this.


If the integration of a video is necessary, think about it quietly and consider the impacts on resource consumption and GDPR. There are technical solutions more respectful of the user, they are initially perhaps a little more complex to set up, however, the solutions will naturally become simpler and more widespread.

The carbon impact of Instagram app features

Reading Time: 4 minutes
Instagram logo

Have you ever wondered what the environmental cost of a post, a story, watching a live or Instagram feed?

The application launched in 2010 has 1 billion monthly active users (Source) including 28 million unique visitors per month. In France, there are 11 million unique visitors per day. Instagram is the most frequented social network behind Facebook.

For this study, we chose to measure the carbon impact, energy consumption, and data on 5 user journeys on the Instagram mobile application (version

  • The publication of a photo in story
  • The publication of a photo with filter and description in profile
  • Viewing a live Instagram
  • Hosting a live Instagram
  • Scrolling the news feed

The carbon impact of Instagram features per 1 minute unit of time

carbon-impact instagram

The feature that has the least impact on the environment over one minute is the photo publication (0.154 gEqCO2), this is the carbon equivalent of 1.3 meters made by a light vehicle/minute. This feature consumes 10 times less than the most impactful of our measures.

The most impactful feature over one minute is that of the scrolling of the newsfeed (1.549 gEqCO2). Over one minute, it is the equivalent of 13 meters done in a light vehicle. Composed of photos, videos, and advertisements (for an active account), the functionality does not consume the most energy (see following graphs), but in terms of the data exchanged, it is the one that displays the highest value (14.63 MB for one minute).

Regarding the Live feature, whether it is on the viewer or host side, the impact is almost the same (13% less for the viewer). The energy consumption is similar, however, the spectator part exchanges fewer data.

If we consider that the average carbon impact of Instagram is 0.664 gEqCO2 / minute (unweighted average of these 5 uses) and that its users spend an average of 28 minutes / day on the social network (Source). So the average impact of a user on Instagram is 18.6 gEqCO2 / day, the equivalent of 166 meters traveled by a light vehicle.

Average Instagram app carbon impact per day and per user

Energy consumption of Instagram features for 1 minute

energy consumption of instagram features

Posting a photo on your Instagram account consumes 1.8 times less energy than posting a photo as a Story (reduced to a one-minute user journey) and 2.4 times less than hosting a Live. The live features are very consuming here since it is a continuous video stream.

Data exchanged from Instagram features for 1 minute

exchanged data from instagram features

The association of photos, videos and advertisements of the newsfeed feature greatly impacts its data exchange since it has to load new elements when scrolling. It also consumes 2.6 times more data than hosting a live and 16 times more than publishing a photo (user journeys reduced to one minute of use) /


The application is measured on an S7 smartphone (Android 8), the user scenarios were carried out through our GREENSPECTOR Test Runner, allowing the performance of automated tests.

Each measurement is the average of 3 homogeneous measurements (with a low standard deviation). The consumption measured on the given smartphone according to a Wi-Fi type network can be different on a laptop PC with a wired network for example.

To assess the impacts of infrastructure (datacenter, network) in the carbon projection calculations, we relied on the OneByte methodology based on real data measured on the volume of data exchanged. This assessment methodology takes into account the consumption of resources and energy in use for the requested equipment. As this is a very macroscopic approach, it is subject to uncertainty and could be fine-tuned to adapt to a context, to a given tool. For the Carbon projection, we assumed a 50% projection via a wifi network and 50% via a mobile network.

To assess the impacts of mobile phones in the carbon projection calculations, we measure the energy consumption of the user scenario on a real device and in order to integrate the material impact share, we rely on the theoretical wear rate generated by the user scenario on the battery, the first wearing part of a smartphone. 500 full charge and discharge cycles therefore cause a change of smartphone in our model.

For those who like numbers

Use caseEnergy consumption (mAh)Exchanged data (MB)Memory consumption (MB)Test time (second)Carbon impact (gEqCO2) per minuteEquivalence in meters of average car in France / minute
Create Stories3,320,522410220,2772,47
Publish a photo on your feed4,750,806425590,1541,37
Timeline scrolling9,714,63460631,54913,83
Hosting a live23,8410,554471190,7166,39
Live viewing23,398,785221190,6225,55

The environmental impact of search engines apps

Reading Time: 13 minutes


Almost 93% of all internet traffic comes from search engines. It is estimated that Google receives 80,000 requests per second or 6.9 billion requests per day. (Source: Blog du modérateur). Globally, if Google holds nearly 91% of the market share, in recent years, new alternative solutions have been trying to disrupt this digital monopoly of internet research.

What are the impacts of our activities on web or mobile search engine applications? What are the most / least impacting solutions for the environment, network congestion, and the autonomy of our smartphones? Moreover, what are the parameters that can vary this impact and how can we, consumers, better limit our impact?

For this study, we chose to measure 8 of the most popular search engine applications in France on the web and mobile versions on Android: Bing, DuckDuckGo, Ecosia, Google, Lilo, Qwant, StartPage, and Yahoo.

Logos applications moteurs recherche


  1. Website search vs URL search comparison
  2. Local search comparison
  3. Weather Search comparison
  4. Comparison of a basic search according to several criteria
    (auto-completion, dark theme, newsfeed)
  5. Comparison between search engines using a web browser
  6. Our advice for an eco-responsible search
  7. Methodology

Disclaimer: we only measure the user device activity, its inputs/outputs, and project the network and server impacts on the basis of an average impact methodology (see methodology section). We know that some engines use low-energy servers, optimized cooling, “green” electricity… That others better protect your privacy or even finance associations and important causes … We have not had access to the data center of our respondents, and we, therefore, made assumptions based on activity projections based on the volume exchanged. However, since this is a subject that has a direct economic impact, we could imagine that these companies have designed optimized systems so that the purchase of machines and their operation don’t cost them too much!

Website search vs URL

For this first comparison, two scenarios are carried out here: on the one hand we launch a search for the keyword “Fnac” and on the other we launch a search by URL “”, allowing us to directly access the site, without going through the search results. Only two applications do not permit direct URL access: StartPage and Yahoo. StartPage does not appear in this ranking due to a display fault on the Fnac site.

Carbon impact of a basic search vs URL

This is not a surprise and it is always better to measure it, we observe that a search by URL consumes much less on all the measured search engine applications. On average, there is a 35% reduction in the carbon impact. Therefore, prefer a search by URL (if you know it!) without going through the search results page in order to save energy and data!

For this first comparison, we recommend using Ecosia, which is the most efficient engine here, all research combined (0.167 gEqCO2) with a standard deviation of 0.377 gEqCO2 with the least sober in the DuckDuckGo ranking (0.5433 gEqCO2). The second place goes to Google (0.192 gEqCO2) which consumes 13% more than Ecosia.

These results are nevertheless very disparate between the different solutions since if on Ecosia the 2 types of research have almost the same impact, it is 2.3 times more important for Google and 4.4 times more for Lilo for example.

On a basic search, it will cost you a 50% higher battery impact with DuckDuckGo and 6 times more data received than with Ecosia. Nevertheless, we note that the memory consumption used by Ecosia is 1.5 times greater on the user’s smartphone in this scenario than the average of other engines. On this same route, we can also note that the lowest energy consumption for your batteries is that of Qwant (tied with Ecosia) due to a faster route. Here efficiency and user scenario performance go hand in hand. It should also be noted that for the most-used engine on the planet, Google is also the one that has the most autonomy impact on basic search, 28% more than the average for other engines. Special mention for Yahoo, which manages to reconcile a low impact and lower memory consumption (not taken into account in the calculation of the Carbon impact).

On a URL search, DuckDuckGo‘s carbon impact is 2.2 times higher than the average for other engines and almost 4 times higher than the most virtuous Google in this scenario. This is explained by low power consumption on the user device but above all with a data consumption 7.3 times less than the average of the engines and almost 15 times less than DuckDuckGo! Small consolation for DuckDuckGo, it also consumes the least memory on the user device with 50% less than the engine average and up to 93% less than the most memory-intensive Ecosia in this scenario again.

Local search, the impact of an interactive map

Capture d'écran du scénario de recherche locale

For this scenario, we run a local search. The keywords “Restaurant Nantes” are searched, most search engines then display an interactive map with a selection of restaurants.

Carbon impact of local research

For this local search, four applications stand out by not displaying an interactive map on the results page: Ecosia, StartPage, Lilo (display of a Pages Jaunes list), and Yahoo. Although less practical for discovering the suggestions at a glance, we notice that these applications are less “carbon-intensive”. It is therefore not surprising that the display of a presentation cartographic representation is detrimental to the environmental impact.

If we take the averages of applications that do not display a map (0.076 gEqCO2) to those that display one (0.161 gEqCO2): we obtain a carbon impact difference of 52%. Maybe these solutions could offer a 2-step map display and only display the detailed map on user request?

In this ranking, Ecosia is also in the lead (0.055 gEqCO2) followed closely by StartPage (0.078 gEqCO2). The worst applications are Google (0.178 gEqCO2) and Qwant (integration of a PagesJaunes card, 0.216 gEqCO2).

The difference in carbon impact between the best and worst application is 74%. However and again Ecosia is also the one which consumes the most memory on the user device, 50% more than the average of the engines for a local search. In the end, only StartPage manages to combine a low carbon impact and lower consumption of memory resources.

To explain these differences, we can cite the data impact 10 times higher for Qwant compared to Ecosia and 2.7 times higher compared to the average for other engines. On the energy side, the differences measured are smaller, Google and Yahoo are the worst enemies of your battery and of the carbon impact on the user device with 28% more consumption on average than the average for other engines.

Targeted search, the impact of a weather widget

Capture d'écran du scénario de recherche ciblée météo

For this scenario, we launch a weather search for the keywords “Météo Nantes”. All engines work with a weather widget. Only the Lilo and Qwant engines do not display any and do not allow a direct view of the current weather forecast. However, Qwant displays in partnership with Yellow Pages, the nearest meteorological organization, skewing the results.

Carbon impact of targeted «weather» research

We observe for this search comparison targeted on the weather, that the Lilo application (0.045 gEqCO2) which does not display a weather widget, is at the top of the ranking. Followed by Ecosia (0.062 gEqCO2), the most efficient application of those which display a weather widget. Between Lilo and Ecosia, the difference in carbon impact amounts to 26%.

If we compare Lilo to the average of the applications displaying the weather widget (0.083 gEqCO2), the difference in carbon impact then amounts to 45%.

The most impacting engine with the weather widget is DuckDuckGo (0.118 gEqCO2), which is 1.9 times more than Ecosia.

For Qwant (0.199 gEqCO2), the research is inconclusive since the engine does not display a widget but the nearest weather station in the form of a Pages Jaunes business and cartographic representation. This practice is clearly more consuming/impacting, 2.5 times more impacting than the average of other engines, and 4 times more impacting than the Lilo engine.

Lilo consumes little energy on the user device and little data. On this indicator, it consumes more than 4 times less data than the engine average and up to 11 times less than Qwant!

On the memory footprint and user battery consumption part, for targeted research, it is again the most efficient StartPage app with 47% less than the average energy consumption of other engines but also 44% less memory than the average. Yahoo, Qwant, and Google are also the most energy-intensive with an average consumption higher with 13% more than the other engines. On the memory side, it is again Ecosia which over-consumes with 50% more than the average of its competitors and almost twice as much as DuckDuckGo!

Search of a definition

In this part, we analyze different ways of approaching a basic search for a definition. We have chosen THE most searched definition on Google in 2019 in France, that of the word “Procrastination”. In addition, in order to save you research, we give you the meaning: Procrastination (feminine name) “tendency to postpone, to put systematically to the next day”. We will check the major research trends of 2020 in a future study!

Definition search

Capture d'écran du scénario de recherche de définition du mot procrastination

This scenario will be used as a basis for the next ones, we are launching a search for the keywords “procrastination definition”.

Carbon impact of a basic definition search

For a simple research, our top 3 carbon impact side consists of: Lilo (0.065 gEqCO2), Ecosia (0.068 gEqCO2) and StartPage (0.076 gEqCO2). Qwant is disadvantaged by its excessive data consumption, it is more economical in the energy consumed on the device since second on the energy consumption side.

StartPage, in addition to having a low impact, is also less “resource-intensive” in memory than the other engines and 2 times less than Ecosia, especially on this use case. StartPage is also the most energy-efficient and 2 times less than Yahoo in the same search scenario.

Qwant is again last in this ranking in terms of carbon impact because it is too expensive in terms of data, almost 3 times more than the average for other engines, and up to 6 times more than Ecosia.

On this same basic research and on the basis of the average impact of the 8 engines, the share of the impact linked to the network and to the mobile is preponderant and in equal share compared to the share of impact on the server which remains low.

Part en pourcentage de l'impact lié au réseau, au mobile et au serveur

However, this projection must be the subject of a more in-depth analysis by placing probes in data centers in particular.

On average, the carbon impact for all search engines is 0.106 gEqCO2. Google‘s, the most widely used engine in the world, is 0.108 gEqCO2, or the carbon impact equivalent of one meter (0.96m) carried out in a light vehicle.

If one projects based on Google usage statistics, here are some interesting numbers:

The carbon impact of the 80,000 requests made in 1 second (if all these requests were basic requests launched from a mid-range smartphone) worldwide is: 8,660 gEqCO2, ie the equivalent of 77 km traveled in a light vehicle. The carbon impact of a day of Google queries is a carbon equivalent of 6.7 million km in a light vehicle.

Definition search with autocompletion

Capture d'écran du scénario de recherche de définition du mot procrastination en auto-complétion

For this auto-completion or “suggestion” scenario, we run a search for the “definition pro” keywords, the engine then displays a “definition procrastination” or “definition procrastinate” suggestion. We click on this proposition. To evaluate this scenario, we had to activate a parameter which allowed us to deactivate the auto-completion mode on the different engines, only 2 engines allow it and are therefore compared here on this scenario.

Carbon impact of basic research vs auto-completion

Only two search engine applications allow you to completely remove suggestions or auto-completion (Ecosia and DuckDuckGo). We note that for Ecosia, for equivalent energy consumption, a basic search without suggestions, the consumption of data exchanged is reduced by 11% compared to a search offering suggestions. On the DuckDuckGo side, a search without suggestions reduces energy consumption by 22% and the volume of data exchanged by 14%.

We observe on average that research using auto-completion reduces the carbon impact by 14%.

Definition search with dark theme

Capture d'écran du thème sombre de Qwant

For this scenario, we activate the dark theme from the settings of the only two apps offering it: DuckDuckGo and Qwant and run the same search for the definition of the word procrastination.

Carbon impact of a light theme vs dark theme research

For these two applications offering the dark theme on mobile, on average the dark theme reduces the carbon impact by 3%. And a little more optimized for DuckDuckGo than for Qwant with an 8% gain on the default theme.

Definition search with active newsfeed

Capture d'écran du scénario de recherche avec newsfeed actif

For this scenario, we activate the homepage newsfeed of some applications and compare with the without newsfeed version.

Carbon impact of research without and with active newsfeed

3 applications allow the activation and deactivation of the news feed present on the home page: Google, Bing, and Qwant. This has the effect of increasing the carbon impact of these three applications by only 3% on average, with an average increase in data of 4% on these 3 engines and a slight increase in local energy consumption. (1%)

Search with a web browser

Capture d'écran de l'application Chrome

For this scenario, we launch the Chrome web browser (version 83.0.4103.106), the measured search engine is previously defined as the default one. The search for definition is always that of the word procrastination.

Carbon impact of an application vs web search

We chose to compare an app search and a browser search. For this measurement, we have chosen the Chrome browser, you can find our “best browsers to use in 2020” study if you’re looking for a browser ranking. For two of the applications measured: DuckDuckGo and Bing, searching via Chrome is less impactful on average by 8%. For the other applications, for which browsing on Chrome is more impactful, this is an average difference of 116% but which goes up to multiply the impact by 5.3 for Lilo. Overall and on average, search through a browser on all of these engines is 64% more impactful than through the mobile application.

For all of these engines,

  • energy consumption is stable and slightly lower on the web by 2% but with large disparities: + 48% for StartPage and minus 28% for Yahoo.
  • Data consumption is growing sharply for web research, with a volume that doubles (+ 119%). There is a strong contrast, however: when Bing consumes 12% less (the only less “data-consuming”), others consume more with a peak for Lilo in particular (13 times more) and Ecosia (4 times more). Google remains in the average of 2 times more data on the web version.
  • Local memory consumption also increases significantly for a mobile web search versus mobile application search with + 48%. Again, there is a strong contrast with Ecosia last on this criterion for the mobile application and first on this web search criterion with a decrease of 2%. For all the others, it is a strong increase within particular for DuckDuckGo (+ 115%) and StartPage (107%).
  • Note that travel times have decreased by 6% partially explaining lower energy consumption in web search.

Our advice for eco-responsible search

When we observe the environmental impact of a search, it is difficult to give with certainty the best advice, a link saved in your favorites to go directly to the right information, good content will always have less impact than launching a new search. We have not tested other related areas such as the security/use of your data or the accessibility of solutions, here is some information that we could summarize:

Conseils de GREENSPECTOR pour une recherche éco-responsable
  • A shorter search process results in less energy/battery impact on your user’s smartphone and can help reduce the overall carbon impact across the chain.
  • The carbon impacts of our research are mainly distributed between the network part and the user’s mobile part equally.
  • A search has more impact via a mobile browser than with a mobile application (64% carbon gain on average).
  • For the engines with the least carbon impact, opt for StartPage or Ecosia even if the latter consumes a lot of memory, a point to correct.
  • To save your battery and your data plan, choose StartPage.
  • If you’re having memory issues on an older smartphone, give DuckDuckGo a try.
  • If you don’t see a need for it, turn off newsfeed widgets, interactive map display, and other weather widgets. Average carbon gain of 48% to 52%.
  • Switch to dark to light displays, when available. Average carbon gain of 3%.

As for Google, which dominates the market, it is in the average carbon footprint but is also the one that on average consumes the most memory (40% more than other engines for all of these uses). Let us keep in mind that an average google request is equivalent to the carbon impact of a journey of 1 meter in an average light vehicle.


For each of its applications, measured on an S7 smartphone (Android 8), the user scenario was carried out through our GREENSPECTOR Test Runner, allowing the performance of automated tests.

Each measurement is the average of 4 homogeneous measurements (with a low standard deviation). The consumption measured on the given smartphone according to a wifi type network can be different on a laptop PC with a wired network for example.

To assess the impacts of infrastructure (datacenter, network) in the carbon projection calculations, we relied on the OneByte methodology based on real data measured on the volume of data exchanged. This assessment methodology takes into account the consumption of resources and energy in use for the requested equipment. As this is a very macroscopic approach, it is subject to uncertainty and could be fine-tuned to adapt to a given context, to a given tool. For the Carbon projection, we assumed a 50% projection via a wifi network and 50% via a mobile network.

To assess the impacts of mobile phones in the carbon projection calculations, we measure the energy consumption of the user scenario on a real device and in order to integrate the material impact share, we rely on the theoretical wear rate generated by the user scenario on the battery, the first wearing part of a smartphone. 500 full charge and discharge cycles, therefore, cause a change of smartphone in our model. This methodology and method of calculation have been validated by the consulting firm specializing in eco-design Evea.

Search engineVersionWeight (MB) Samsung S7Playstore gradeDownloadsFrench Market Share (%)
Bing11.3.2820730292,84,55 000 000+3,83%
DuckDuckGo5.55.134,14,710 000 000+0,86%
Ecosia3.8.11374,65 000 000+1,11%
Google11.10.11.214184,35 000 000 000+ 91,68%
Lilo1.0.2286,74,3100 000+N/C
Qwant3.5.01794,01 000 000+0,79%
StartPage2.1.574,4500 000+N/C
Yahoo5.10.51114,31 000 000+1,32 %

What’s the carbon impact for social network applications?

Reading Time: 6 minutes

The stay-at-home context has mechanically increased the mobile applications use of the social network type in order to keep people connected. Like the professional use of videoconferencing tools, these uses have brought additional pressure on the network and on the servers of these solutions.

What are our activities impact on social networks? What are the most / least impactful solutions for the environment, network congestion and the autonomy of our smartphones?

For this study, we’ve chosen to measure the news feed of the 10 most popular social media applications: Facebook, Instagram, LinkedIn, Pinterest, Reddit, Snapchat, TikTok, Twitch, Twitter and Youtube. Although these applications are different in terms of functionality, we have chosen to compare them in terms of carbon impact, energy consumption and data exchanged.

For each of its applications, measured on an S7 smartphone (Android 8), the user scenario lasting 1 minute was carried out through our GREENSPECTOR Test Runner, allowing manual tests to be carried out. For each of its applications, the user scenario corresponds to a scrolling of the contents of the news feed of an active account.

Each data measurement is the average of 3 homogeneous measurements (with a small standard deviation). The consumption measured on the given smartphone according to a wifi type network can be different on a laptop PC with a wired network for example.

To make Carbon projections to assess the impacts of infrastructure (data center, network), we relied on the OneByte methodology based on real data measured by the volume of data exchanged. This evaluation methodology takes into account the consumption of resources and energy in use for the equipment requested. As it is a very macroscopic approach, it is subject to uncertainty and could be refined to adapt a context, a given tool. For the Carbon projection, we have assumed a projection of 50% via a wifi network and 50% via a mobile network.

To make the carbon projection of the mobile, we measure both the energy consumption linked to the use case based on real measurement on real device and to integrate the share of material impact, we rely on the rated theoretical wear and tear generated by the use case on the battery, the first wearing part of a smartphone. 500 cycles of full charges and discharges therefore cause in our model a change of smartphone.

Projected data measured in Carbon impact (gEqCO2)

Youtube (0.66 gEqCO2) is first in the ranking, followed closely by Facebook (0.73 gEqCO2) and LinkedIn (0.75 gEqCO2). This is easily explained, since the only videos launching during the news feed for Youtube are thumbnails and this, after 2 seconds. It should be noted that in our test, the scanning of the news feed was slow enough to launch videos according to this principle of tempo.

On the Environmental Impact side of applications, the social network whose news feed is the most impacting is Tik Tok. Unsurprisingly, this social network is based exclusively on watching videos and preloading videos from the news feed at startup. The Shift Project also presents streaming platforms such as Netflix, Youtube and Tik Tok as being responsible for 80% of digital electricity consumption. We had already noted this significant impact, in particular when the application was launched in 2019.

Only 4 applications (Tik Tok, Reddit, Pinterest and Snapchat) are above the average carbon impact (2.1 qEqCO2) observed for this comparison of the news feed. Moreover, the Tik Tok news feed has a carbon impact of 7.4 times greater than that of Youtube.

What if we were to project all of this at the user level?

If we projected this usage “display and progress of the news feed” as being representative over the duration of daily usage/user, we will obtain this data.

According to the Global Web Index 2019, we spend on average 2 hours and 22 minutes on social networks. If we project the average carbon impact of the 10 applications measured (2.10 gEqCO2) over 60 seconds at the average time spent per user, we obtain for a user/day: 280.5 gEqCO2. Or the equivalent of 2.50 km traveled in a vehicle. This also corresponds to 102 kgEqCO2 per user per year, the equivalent of 914 km traveled by medium vehicle in France. This is equivalent to 1.5% of the carbon impact of a French person (7 Tons).

And globally?

If we projected this usage “display and progress of the news feed” as being representative over the duration of daily usage/user, we will obtain this data.

The 2019 figures of LyfeMarketing and Emarsys announce 3.2 billion social network users (42% of the world population) of which 91% access social networks via a mobile device. 80% of the time spent (2 hours and 22 minutes) on social networks is spent on a mobile device. If we project our carbon/user impact to these data, we obtain: 262 million Tons EqCO2 per year for the 3.2 billion users on mobile, the equivalent of 56% of EqCO2 impacts in France.

Energy consumption measurement (mAh)

In terms of energy consumption, the bad students are the news feeds of the Snapchat, Tik Tok and Pinterest applications. The good energy students are Youtube, LinkedIn, and Reddit. The Snapchat news feed consumes 1.6 times more energy here than that of Youtube.

The average established for energy consumption is 10.6 mAh, only 4 applications are above.

If we assume that the application runs continuously on the smartphone, then we can project the remaining battery life time (graph below). We can observe that with Snapchat running, the battery lasts 3.45 hours. On the Youtube side, the battery autonomy lasts 5.46 hours, i.e a ratio of 1.5 (or a difference of 2 hours) between the best and the least good application of this ranking. The average is 4.8 hours for all of these applications. The reference measurement of the test smartphone is 1.32 mAh, its battery capacity of 3000 mAh, we can estimate its autonomy at 18 hours. The use of social networking applications therefore greatly impacts your battery life.

Measurement of data exchanged (MB)

In terms of data exchanged, the bad students are the news feeds of the Tik Tok, Reddit and Pinterest applications. The good students on the data exchanged side are Youtube, Facebook and LinkedIn. Tik Tok consumes 9 times more data than the Youtube application.

The average established for the data exchanged is 19.2 MB for this use. Beware of your data plans! Projection in 1 month, you will have consumed 74 GB!

Taking into account the real average time spent by social network according to the Visionary Marketing blog: if you only use Tik Tok in social network (up to 52 minutes per projected day), you will consume nearly 71 GB per month, while Instagram (up to 53 minutes a day) will consume 25.6 GB! Are you more connected to Facebook? This will make you consume almost 10 GB (up to 58 minutes per day) per month.

For those who like numbers

ApplicationVersionDownloadsGoogle Play Store GradeEnergy consumption (mAh)Data exchanged (MB)Memory consumption (MB)Carbon Impact (qEqCO2)
Facebook270.1/0.66.1275 000 000 000+4,29,551845870.73
Instagram142.0.34.1101 000 000 000+4,510,917,2503,21.91
LinkedIn4.1.451 500 000 000+4,39,26,15492,40.75
Pinterest8.17.0100 000 000+4,611,133,2432,73.53
Reddit2020.18.010 000 000+4,69,243,4414,04.54
Snapchat10.82.5.0 1 000 000 000+4,314,418505,82.03
Tik Tok16.0.43 1 000 000 000+4,312,146,9385,54.93
Twitch9.1.1100 000 000+4,69,69,4374,41.09
Twitter8.45.0 500 000 000+4,510,76,6421,10.83
Youtube15.19.34 5 000 000 000+4,19,15,1379,30.66

Which video conferencing mobile application to reduce your impact?

Reading Time: 5 minutes

Article updated with new measures on StarLeaf, Rainbow and Circuit by Unify on May 19, 2020.
Article updated with new measures on Hangouts and Google Meet on May 4, 2020.
Article updated with new measures on Tixeo and Infomaniak Meet on April 23, 2020.
Article updated with new measures on JITSI and Teams on April 15, 2020.

The current “stay at home” context mechanically increases the use of online collaboration tools, in particular videoconferencing tools. This leads to a pressure on the network and more particularly to a significant load on the servers of each solution. It is therefore important from an efficiency point of view but also an environmental impact one to choose the simplest and most efficient solution.

For this study, we compare 14 videoconferencing applications: Whereby, Webex (by CISCO), Skype, Zoom, JITSI, Microsoft Teams, Tixeo, Infomaniak Meet, Hangouts, GoToMeeting, Google Meet, StarLeaf, Rainbow and Circuit by Unify.

For each of these applications, measured on an Samsung S7 smartphone (Android 8), the following three scenarios were carried out through our GREENSPECTOR Test Runner, allowing manual tests to be carried out over a period of 1 minute:

  • Audio conference only in one-to-one
  • One-to-one audio and video conference (camera activated on each side)
  • One-to-one audio conference and screen sharing

Each measurement is the average of 3 homogeneous measurements (with a small standard deviation). The consumption measured on the given smartphone according to a Wi-Fi type network can be different on a laptop PC with a wired network for example.

Measurement of energy consumption (mAh)

The StarLeaf application consumes the most of all three scenarios. This is due to the fact that the consumption in audio only mode, audio + screen sharing or audio + video is the same. This is a special case of our study. The GoToMeeting application is the least energy-consuming, closely followed by Hangouts, Zoom and Webex.

The energy consumption of all these applications is on average 2.1 times higher when adding video to audio and only slightly higher when adding screen sharing to audio (+14%). It’s not a surprise, avoid sharing with a camera to consume less energy on your devices during your video conferences and save your autonomy and the lifespan of your battery!

Measurement of data exchanged (MB)

GoToMeeting and Webex are the two applications that consume the least data. JITSI and Infomaniak Meet are the ones that consumes the most. Overall and without any surprise we note that the audio scenario is the one that consumes the least data. While the scenario activating both audio + video stream is the most consuming one.

The data consumption of all of these applications is 13 times higher when adding video to audio and almost doubled when adding screen sharing to audio (+77%). It’s not a surprise, avoid sharing video and limit your screen sharing to consume less data on networks in your video conferences!

It should be noted that these significant differences are mainly due to the significant audio-video consumption of the JITSI application with 35 MB transferred in 1 minute compared to 1.13 MB for GoToMeeting! JITSI‘s optimized mode does not reduce this data impact (33.4 MB / minute). Infomaniak Meet based on the JITSI engine meets the same volume anomaly on average and mainly on the audio + video part without improvement with the optimized mode.

Projection of the measured carbon impact data (gEqCO2)

A conference on mobile is 3 times more impactful for the environment when we add video to audio.

The carbon impact projection of all of these applications is on average 3 times greater when adding video to audio and higher when adding screen sharing to audio (+35%). It’s no surprise, avoid sharing video and limit your screen sharing to less impact infrastructure (network, datacenter) and on your devices in the context of video conferences!

Without any surprise, a large part of the carbon impacts are located on the network part (63%) but the impacts part on the device (28%) should not be overlooked!

The JITSI and Infomaniak Meet apps even averages 5.8 times more impact when adding video to audio and 40% more when adding screen sharing.

In the Skype vs Teams battle at Microsoft, the overall results are very close (6%). The Carbon impact is lower for Skype with a lower data impact but higher energy consumption on the mobile than Teams.

Which applications optimize energy and data consumption?

Only Whereby and Webex could be tested on optimization features for the mobile version.

The Whereby application with its “Mobile mode” setting which limits the resolution of the stream as well as other resource consumption optimizations. And Webex thanks to its configuration allowing to deactivate High-definition playback of videos only. Whereby saves 21% on energy consumption on the audio side, 15% on the audio and video side and 3% on the screen sharing side. These gains are nevertheless low considering the results obtained by the application that consumes the most audio and video mode from our panel.

On the Webex side, the gains are barely visible as limited only to the video part. It’s barely 5% gain in the Audio and Video scenario for the energy and carbon impact. The exchanged data is even slightly higher in audio and video mode.

The optimized JITSI application does not improve the data or energy impact. Power consumption is even higher in screen sharing mode in this optimized mode. However, there is a reduction in the data loaded in this optimized but minor mode (11% on average). Same findings for Infomaniak Meet.

The optimization of the TIXEO parameters makes it possible to considerably reduce the impact in audio + video mode and allows it to be classified as the 2nd least impacting application in the panel.

As for the Zoom application, a notification of battery overconsumption appeared several times during the measurements. Although we can optimize the video quality on PC, it does not seem possible to configure this on mobile. Without this optimization, the application becomes the most energy-consuming application in audio + video mode.


  • Promote audio only during your conferences: the video stream will tend to consume much more especially when sharing video via camera.
  • We recommend that publishers provide optimization options to the user and make them as accessible as possible even by default.
  • Prefer videoconferences over travel by car!
  • Comparison for 2 people who talk to each other for 3 hours in video + video (1 gEqCO2 on average per minute) when one of the two made 20 kms (112 g eqCO2 / km in France) round trip for a face-to-face face,
  • In videoconference: 180 * 1 * 2 = 360 gEqCO2.
  • By car: 112 * 20 = 2.4 kg EqCO2. Or 6.7 times more for the physical one-to-one.

Best 2019 Android apps and games ranking by GREENSPECTOR

Reading Time: 2 minutes

Google unveiled the best of 2019 Google Playstore in early December last year. Thanks to the GREENSPECTOR App Mark technology, we are revealing the ranking of these applications according to the App Mark, which assesses applications according to 5 criteria: performance, sobriety, discretion, inclusion and, of course, ecology.

Favorite 2019 applications ranking

At the top of this ranking we find the following three applications: Boosted, 21 Buttons and Omio. Only 1/3 of the applications are below the global ecoscore average. Among the 3 least sober applications of this ranking, 2 are strongly impacted by a zero score on at least one of the key indicators. In fact, the Plant Nanny application presents a score of zero on the ecological side (32 MB of data loaded during our evaluation), for the Curio application, it is the performance indicator which is zero, impacted by the time of application loading more than 23 seconds.

Focus on Boosted vs Music Zen

Here we compare the application with the best GREENSPECTOR App Mark (Bosted) versus the lowest ranked application in this ranking (Music Zen).

Even if the energy consumption is not the strong point of Boosted, MusicZen consumes 2 times more battery than Boosted on an identical route … what not to be “Zen” For its autonomy! Simple explanations: there are many trackers in this application which alters its performance and its sobriety. As a reminder, an added tracker also means an average of 8.5% more resource consumption.

Favorite 2019 games apps ranking

On the podium of the highest ranked game applications, we find: Assassin’s Creed Rebellion, Brawl Stars and Fishing Life. We observe that the last three game applications have a zero score for the ecology indicator. This is explained by two highly high technical criteria: the volume of data loaded as well as the CO2 impact. By the way, gaming applications are also more impactful on average than other applications.

Focus on Assassin’s Creed Rebellion vs Diner Dash Adventures

This time we are comparing the Assassin’s Creed Rebellion application versus Diner Dash Adventures.

To understand everything about these indicators, we invite you to read the following article 5 success keys for your application!

What are the best web browsers to use in 2020?

Reading Time: 8 minutes

The web browser is a main tool on a mobile device. Not only for websites but also for new applications based on web technologies (progressive web app, games, …).

In our 30 most popular mobile apps ranking, among the mails, direct messaging, social networks, browsers categories, web browsing and social networks are on average more consuming than games or multimedia applications. The ratio would be 1 to 4 between the least and most energy consuming applications.

Decreasing the environmental impact of the digital life and increasing the autonomy of phones go in part through the choice of a good browser. Just as if you want to reduce the impact of your mode of transport, it is important to take the most efficient vehicle.

Last year we published the 2018 ranking of the least energy-consuming browsers, we made a new edition for 2020, more complete, made with our GREENSPECTOR App Mark.

Overall Ranking

The average rating is 36/100 which is pretty mediocre. It can be explained by low notes for each of the metrics.
The three least energy-consuming browsers are: Vivaldi, Firefox Preview, Duck Duck Go.

Overall energy consumption (in mAh)

The median is 47 mAh and a large part of the browsers are in this consumption level (8/18 are in the 2nd quartile).
Note that the last 3 browsers in the ranking are recognized by a consumption 75% higher than the median. Firefox, Qwant and Opera Mini are indeed very energy intensive.

Energy consumption of navigation (in mAh)

The last 3 browsers of the global ranking (Opera Mini, Firefox and Qwant) as well as Mint consume much more than the average (between 20 and 35 mAh against 16 mAh).

It is sufficient to say that for most browsers (apart from the previous exceptions), pure navigation is not going to be the reason for the difference in overall consumption. This is mainly due to the use of visualization engines. Most browsers use the Chromium engine. For Opera Mini, the specificity is that a proxy is used and can compress the size of the sites. It seems that this proxy is not good for the energy, in fact the decompression on the user’s phone consumes a lot of energy.

For the Firefox app, over-consumption of energy is a known and shared thing, this is one of the reasons why Mozilla is under development of a new browser. Internal code name is Fenix ​​and public one is Preview. The measures in this ranking are rather encouraging on consumption (in the average).
For Qwant, this is due to the use of the Firefox engine! The measurements between Qwant and Firefox are indeed very close.

Power consumption of features (in mAh)

The main feature that is browsing the web also requires other important features: new tab opening, enter an address in the taskbar … Indeed, when we open a new tab, each browser offers different features: mainly used websites, latest news, …

On pure navigation, browsers differ little, there are significant differences in energy consumption on other features with a ratio of more than 3 (between 4 mAh and 12 mAh).

Note that the first 3 (Firefox Focus, Firefox Preview and Duck Duck Go) have a simple homepage. The consumption of the browser in Idle (inactivity) is then very low. Functional sobriety pays the consequences!

When launching browsers, the energy consumptions are quite similar to each other. Note, however, that opening a tab and writing a URL are actions that are performed several times. If we take a daily projection of 30 new tabs and 10 URL entries, we can still see the difference between browsers and the large advance of Firefox Preview and Focus!

The basic features are not insignificant in the overall consumption.

Projection of autonomy (in number of hours)

If we take this energy data and project it for a navigation of several websites, we identify the maximum time that the user can navigate to the complete discharge of his battery:

Data consumption (in MB)

The difference in data consumption between browsers (8 MB difference) is explained by the pure navigation and the different features.

On the navigation, we explain this difference:

  • some applications do not manage the cache at all for reasons of data protection and confidentiality (Firefox Focus)
  • proxy usage that optimizes data (Opera Mini)
  • a difference in the implementation of cache management. It is possible that some browsers invalidate the cache and that data is loaded while they are cached.
  • additional data consumption continues in the background (idle tabs, background data not blocked …)
  • download performance differences that increase the duration of the measurement. Indeed, if a browser is powerful, the counterpart is that many more data are potentially loaded in the background.

The difference in overall consumption can also be explained by the data consumption of the basic functionalities:

Many browsers are very consuming. We note the 3 MB of Qwant that seem abnormal!
It can be considered that for browsers, this consumption should be close to 0. Indeed, the main feature of a browser is to display a website, any feature (and associated consumption) can be considered as “over-consumption”.
In this context, many browsers consume data when writing the URL. This is mainly explained by the URL proposal features. There is indeed exchange between the mobile and the servers, either directly by the browser or by the associated search engine.

For example, for the Yandex browser below, the details of data exchanges when writing a URL show more than 400 KB of data exchanged.

In contrast, below, trading for Brave is frugal with less than 2 KB.

Browser performance (in seconds)

The measures allow us to evaluate the performance of the key features:

  • Launching the browser
  • Adding a tab
  • Writing a URL
  • Removing the cache
  • Mozilla Kraken Bench

NB: This study does not evaluate the display performance of websites. However, the Mozilla Kraken benchmark allows this in part by evaluating the functionality of browsers.

Efficiency of browsers (in mAh/s)

We can evaluate the efficiency of browsers by taking the performance of the Mozilla Kraken benchmark and the associated energy. Efficiency is the energy consumption per unit of time:

Samsung, Opera Mini and Opera are the most efficient browsers. This ranking is different from that of overall energy consumption. For Samsung Internet, this first place in terms of efficiency on a Samsung hardware can be explained by the optimized link that can have the manufacturer with a pre-installed software. The Opera browser has a good positioning (2nd for overall consumption and 3rd for efficiency).

Track of improvements

It is possible to improve the consumption of navigation.

For the user :

  • Choosing an efficient browser
  • Use bookmarks or favorites to avoid going through the entry bar
  • Configure the energy saving options of browsers (mode or dark theme, data server …)

For developers of sites:

  • Eco-design their site
  • Test and measure on different browsers to identify different behaviors and take them into account

For browser editors:

  • Measure energy consumption and efficiency
  • Eco-design features
  • Reduce resource consumption of recurring features (url write, new tab …)
  • Make the homepage as simple as possible.

Measurement protocol

The measurements were carried out by the laboratory GREENSPECTOR App Mark on the basis of a protocol Standardized: Samsung S7 Smartphone, Android 8, Wi-Fi, 50% brightness. Between 4 and 8 iterations were carried out and the value used is the average of these measurements. Measurement campaigns follow a scenario that evaluates browsers in different situations.

Evaluation of features

  • Launching the browser
  • Adding a tab
  • Writing a URL in the search bar
  • Remove tabs and clean the cache


  • Launch of 6 sites and wait for 20 seconds to be representative of a user journey

Benchmark browser

Evaluation of browser inactivity periods

  • At launch (this allows to evaluate the homepage of the browser)
  • After navigation
  • After closing the browser (to identify closing problems)

For each iteration, the following tests are performed:

  • Deleting the cache and tabs (without measurement)
  • First measure
  • Second measure to measure the behavior with cache
  • Remove cache and tabs (with measure)
  • System shutdown of the browser (and not only a closure by the user to ensure a real closing of the browser)

The average measurement therefore takes into account a navigation with and without cache.

The main metrics analyzed are: display performance, power consumption, data exchange. Other metrics such as CPU consumption, memory consumption, system data … are measured but will not be displayed in this report. Contact GREENSPECTOR for more information.

In order to improve the stability of the measurements, the protocol is completely automated. We use an abstract GREENSPECTOR test description language that allows us to fully automate this protocol. Browser configurations are the default ones. We have not changed any settings of the browser or its search engine.


A notation out of 100 makes it possible to classify the browsers between them. It is based on the notation of 3 main metrics:

PerformanceDuration required for a test stepseconds (s)
EnergyBattery discharge rate found on the device during the test step, compared to the battery discharge rate of the device before the application is launchedMeasurements in uAh / s, then classification in multiples of the reference discharge velocity
DataTotal data volume (transmitted + received) during the test stepkilo-bytes (kB)

A weighting ratio is applied to the 5 step levels (from 5 for dark green to -1 for dark red) as described in the following example table:

The score of this application is then calculated at 61/100 for the energy metric.
Once the score of each of the three metrics obtained on 100 points, the total score of the application is calculated with equal weighting of the three metrics:
Total Score = (Performance Score + Energy Score + Score Data) / 3

Browsers evaluated

Browser nameVersion
Duck Duck Go5.32.3
Firefox Focus8.0.24
Firefox Preview2.3.0
Opera Mini44.1.2254.143

Some browsers were discarded because they did not allow the tests automation. For instance, UC Browser and Dolphin browsers could not be measured. Beyond automation, this is a symptom of a accessibility issue of the application. To improve the accessibility of applications for people with visual impairments (among others), it is necessary to set up buttons labels. The automation that we realized is based on this information. In the end, these browsers do not appear in the ranking, but we can consider that accessibility problems are in all cases a crippling problem.

Note : The 2020 ranking is hardly comparable to that of 2018. Indeed, our protocol having completely evolved, the tests are thus more advanced and automated.

Discover our lastest study: the 2019 Playstore Efficiency Report!