ecometer

Analyse your website's ecodesign maturity

Browse it

For decision-makers and IT professionals, ECOMETER assesses the environmental impact of your online service on all phases of its life cycle.

Test it green

ECOMETER tests 115 ecodesign best practices from the reference book published by Eyrolles, with contributions by more than 34 business experts.

Improve it

Internationally intended, conducted with ADEME's financial support, ECOMETER is community driven, open-source, free and pedagogically oriented.

The results given by this tool are for educational and diagnostic purpose only, it is not intended to compare websites.
This tool is in beta version and still in active development, all given informations may change in the future.

Best pratice examples...

From design to hosting, 115 best practices are tested and explained. Here are some examples, but be sure to check the other ones:

Development #810

Avoid expensive JavaScript/CSS animations

JavaScript/CSS animations can be very expensive in terms of CPU power and RAM usage. They all trigger actions such as (re)paint/(re)flow that consume a lot of resources. Thus avoid using animations as much as possible, and only do so when absolutely necessary.
If you must include an animation, only employ the opacity and transform CSS3 properties as well as the related functions: translate, rotate, scale and transform. These two properties are automatically optimized by the browser, and the animation can be handled by the GPU. lists the DOM-related actions triggered by an animation.
You can help the browser minimize the resources consumed by using will-change to warn it that an amination will take place.

Learn more about this best pratice

Development #170

Keep the number of domains serving resources to a minimum

When a website or online service hosts a web page’s components across several domains, the browser has to establish an HTTP connection with every single one. Once the HTML page has been retrieved, the browser calls the sources as it traverses the DOM (Document Object Model).

Some resources are essential for the page to work. If they are hosted on another domain which is slow, it may increase the page’s render time. You should therefore, when possible, group all resources on a single domain.

The only exception to this is for static resources (style sheets, images, etc.), which should be hosted on a separate domain to avoid sending one or multiple cookies for each browser GET HTTP request. This reduces response time and unnecessary bandwidth consumption.

Learn more about this best pratice

With the support of

ADEME

The collaborative approch of ecometer tool's creation has been supported by ADEME Bourgogne Franche-Comté within the scope of the 2015 call for projects about Circular Economy.

Partnerships

AER Atol Conseils & Développements Cadoles

Logomotion Planet Bourgogne Pulsar DS Bourgogne Franche-Comté Numérique