Eco-design declaration

We ran a survey among our readers between July and October 2024 and obtained 64 responses in total.

We measured their interest in a media outlet about responsible digital technology and what types of content they wanted to read (multiple answers possible):

• 70% were interested in current affairs articles
• 69% in explanatory deep-dives
• 59% in good practices (e.g. 5 tips to reduce the electricity consumption of your devices)
• 58% in interviews with committed actors
• 44% in experience reports

The proposed digital service also contributes to the following Sustainable Development Goals (SDGs):

• SDG 4: Ensure inclusive and equitable quality education and promote lifelong learning opportunities for all
• SDG 9: Build resilient infrastructure, promote inclusive and sustainable industrialization and foster innovation
• SDG 12: Ensure sustainable consumption and production patterns
• SDG 13: Take urgent action to combat climate change and its impacts
• SDG 16: Promote peaceful and inclusive societies for sustainable development

Reference: French SDG portal

Cécile Rouyer, member of Les e-novateurs and a graphic designer committed to accessibility, helped redefine the media’s graphic charter.

She supported us during the survey and in defining target users and their expectations and needs.

Her synthesis can be consulted online (FR).

The referent is Jérémy Pastouret, a web developer attentive to eco-design topics.

He contributed to the new edition of the Web eco-design publication: 115 best practices (Green IT collective) and to the frugal AI reference framework (AFNOR - Sustainable Development General Commission).

Reviews are performed via automated tests before each production deployment only.

• Tests with Playwright (mp4 video – 1MB) to ensure main pages and new features work correctly.
• EcoIndex score check using Playwright: the homepage, the new article and/or new brief, and the article list are reviewed and must obtain a score above 50.
  

We aim to reduce the size of our cover images because they are oversized. A script is being developed and tests must be performed.

We also want to find a host for our videos using PeerTube to avoid hosting them locally and to enable better distribution.

The service only collects visit data via Matomo, installed on the same server.

Email addresses are collected with user consent solely to send the monthly newsletter.

The site is only available over HTTPS; data is therefore encrypted during transmission.

The source code is available on GitHub but currently private. API key cleaning, Git history cleanup and README work are needed before making it public.

No closed technology is used within the association or the media. We use Next.js / TailwindCSS and a Slim PHP API.

The service does not rely on a connected object or hardware peripheral.

The service works on desktop, tablet and smartphone with a working internet connection. JavaScript is recommended for comfort but not required to access the content.

Tests were carried out to verify the site works on a Samsung J3 (2017, Android 7) and a Samsung Galaxy S5 (Android 6.0.1).

The test video under Samsung Galaxy S5 can be viewed (mp4 – 6MB).

The service also works on computers under Windows XP, 7 and 10.

Tests for XP were done using an emulator on macOS M1 with UTM (512MB RAM, 1GHz CPU). The test video can be viewed (mp4 – 14.8MB).

The service is functional on older terminals, though comfort is degraded: emojis not interpreted and accessibility impacted by text not perfectly adapting on very old browsers.

Tested in Firefox after clearing cache and setting connection speed to Regular 2G. Thanks to Next.js and PWA technology, content is downloaded progressively.

Text (highest priority) loads quickly, then images with lazy loading. A cache system allows offline use (practical e.g. on a train).

Tests were performed while traveling by train, in tunnels or during network cuts: content already cached worked correctly.

Firefox tests are viewable (mp4 – 5.7MB).

The test carried out in 2.2 also validates this criterion (Firefox 45 under Windows XP + older Chrome under Android).

Tested with Firefox using the following screen types:

• LG M2362DP TV screen – 23" (homepage screenshot – 614KB)
• iPhone 5SE 320x568 (screenshot – 167KB)
• iPad iOS 14.7 1080x810 (screenshot – 235KB)
• MacBook Pro M1 – 13" (screenshot – 596KB)

By default we eco-design each functionality, but we have no dedicated external human review per addition.

The service has no QA or test environments; only local development environments and several private GitHub repositories.

Decommissioning is simple: make the project public on GitHub (open source) and shut down the single production server.

For maintenance, an auto-restart and alert system is in place if the platform becomes inaccessible.

Host Ikoula performs regular maintenance and monitoring of VPS (e.g. via Zabbix agents).

The service uses TailwindCSS for design, allowing optimization & compression of used class code. Components rely on TailwindCSS and are developed to be reusable.

When a possible component addition (due to a gap) arises, we research existing components first.

This approach also helps keep code clean and avoid accumulating unused components.

Only two third-party services on the media:

• Matomo: installed on our own server, with archiving option enabled to avoid DB overload.
• Mailchimp: newsletter management tool. An API call occurs each time a visitor subscribes.

The service relies on Next.js and we use it to precompile all pages. SSR ensures pages aren’t generated on each user request and content is optimized.

We use a VPS provided by Ikoula and perform Debian updates.

Hardware choice & compatibility is handled by Ikoula. The OS is widely used and community-supported.

Currently nothing suggests the service won’t follow new protocols.

We are a web service; we follow framework updates and are not tied to specific mobile/PC OS configurations.

A web service with live updates whenever users connect. Bugs are fixed as soon as possible.

At build time Next.js compares pages present in code with those already generated. If new or modified, it rebuilds.

We consider this criterion not aimed at a web service, but we provide complementary info.

Development occurs locally. Tests are run locally; file updates on server are done by a sober git pull then build directly on server.

Animations/videos/sounds are rare; when present, autoplay is disabled.

No page uses infinite scroll; pagination is employed when relevant.

The service delivers information; we have few core features and their functioning is clearly indicated.

For Matomo, if Do Not Track is enabled or an AdBlocker-like extension is used, tracking is automatically disabled.

For Mailchimp, the API is called only if the user enters their email and clicks submit.

We use web standards and haven’t added custom fonts.

Video is an alternate format for accessing information. Most content is text with illustrative images. Videos mainly stem from our own interviews or are useful to illustrate an article.

Text remains the priority; there is one cover image per article/brief in line with press codes. Other images illustrate useful points. Few images lack alt text because most images are meaningful.

For infographics we strive for maximum accessibility. We build them combining HTML/CSS and when not possible use SVG vector formats.

To avoid many ChatGPT screenshots just to show a fact, we developed a component replicating its visual codes for lighter, more integrable content than images.

We use only standard system fonts; no custom font files.

Newsletter subscription field shows format and is controlled by browser validation.

We make a habit of indicating size and format of any file users might download.

No functionality with significant environmental impact – criterion N/A.

No notification system.

We are not aware of questionable designs. During donation campaigns we may highlight key association information, but we do not push users to perform unwanted actions.

An eco-index badge is available in the footer; the eco-design page is open access.

We also provide a free browser extension for Firefox/Chrome (and Firefox Android) to display EcoIndex badges on any site consulted: presentation (FR) on Les Bases (ANCT).

All images are compressed in webp format.

Next.js Image component adapts to device viewport with appropriate compression. My hack/tutorial explains the Image module functioning (FR).

We have two types of video: embedded YouTube (we minimize resolution, user can adjust on YouTube) and self-hosted videos in two formats for compatibility, usually with subtitles.

Self-hosted videos are compressed and provided in low quality for storage & environmental reasons.

As above: either compressed by default or YouTube embedded at low resolution.

Our interview videos are also available as podcasts, but this option is not visually integrated on the media.

We manually remove non-useful content based on page views or maintenance status. Articles are rarely deleted; historical memory is essential.

We rely on EcoIndex values or manual visual control via dev tools console.

With Next.js + PWA we set up caching for site content.

Provided by Next.js by default.

Content is displayed progressively via Next.js lazy loading.

We do not call browser APIs for geolocation or other sensor-based functions.

All resources are on the same domain (les-enovateurs.com) secured with HTTPS.

As the site is precompiled we consider cache generated at each new version.

No long-running background processing.

No blockchain-like system integrated.

Answer provided by Ikoula

Commitments:

Continuously improve infrastructure energy performance & develop clean energy usage for data centers

• Monitoring PUE (Power Usage Effectiveness)
• Optimizing cooling: cold corridor
• Responsible energy management (ISO 50001)
• Internal training/awareness (ISO 50001)
• Use of 100% green energy
• Energy transition plan

Reduce the carbon footprint of activities

• Carbon footprint assessment
• Contribution to compensation projects
• Emissions monitoring
• Continuous optimization of showcase site to reduce energy consumption
• Participation in Net Zero Initiative workshops (Group)

Reduce environmental impact overall

• Zero-paper policy
• Digitization of invoicing & HR processes
• Remote work
• Teams meetings encouraged
• Reduction of non-essential professional travel
• Encouraging more ecological transport (Trainline, easier train booking)

Align to best sector practices

• Member of Green Web Foundation
• Signatory of Climate Neutral Data Centre Pact
• CISPE
• Alignment with Code of Conduct (CoC)
• Support from recognized actor Greenly (via parent company)

Answer provided by Ikoula

Commitments:

Reduce environmental impact at hardware design & manufacturing stage

• Limiting production chains – on-site manufacturing of part of our own server ranges
• Low-consumption components (TDP)
• Choice of high energy-performance materials
• Rationalization of IT purchasing
• Optimization for multi-products / hardware scalability

Extend hardware lifespan & limit e-waste

• Durable materials – extending product lifecycle
• Waste reduction and recovery
• Material recycling
• Refurbished server range (Classic) / highlighted via comms (blog article, promo)
• Donations to organizations/entities in need if hardware still functional but below our security standards

Answer provided by Ikoula

Reims 1.7 / Eppes 1.56

Continuous PUE improvement policy (ISO 50001) – recent renewal (June 2025)

Answer provided by Ikoula

Close to 0 – Ikoula does not use water for cooling

Answer provided by Ikoula

Use of electricity 100% from renewable sources

Answer provided by Ikoula

Two owned data centers in France: Reims (51) & Eppes (02) – 50 km apart

Answer provided by Ikoula

A study was conducted to reuse waste heat; current conditions do not allow it.

Answer provided by Ikoula

Ikoula does not host hot/cold data separately.

Answer provided by Ikoula

Yes, duplication only for redundancy & backups (3-2-1 rule).

Answer provided by Ikoula

All equipment respects ISO 27001 perimeter rules for energy efficiency (power vs consumed energy).

We also dimension resources according to need (avoid oversizing & overconsuming).