Skip to content
L'endroitRestaurant in Salon-de-Provence

Eco-design statement

L'endroit is committed to an eco-design approach to reduce the environmental footprint of its website. This statement applies to the website www.restaurant-lendroit-salon-de-provence.fr, assessed according to the general framework for the eco-design of digital services (RGESN), 2024 version (new tab), published by Arcep and Arcom in conjunction with ADEME.

Progress score

Progress score: 82% (assessed on October 28, 2026).

Of the framework's 78 criteria, 52 are met, 2 are not yet met, 9 are under assessment and 15 do not apply to this site.

The score follows Arcep's method: the sum of points for the criteria met (65.25) divided by the sum of points for the applicable criteria (79.75), multiplied by 100. A priority criterion is worth 1.5 points, a recommended criterion 1.25 and a moderate criterion 1. A criterion under assessment counts as not met. This is a self-assessment.

Theme Score
1. Strategy 76 %
2. Specifications 70 %
3. Architecture 67 %
4. User experience and interface 93 %
5. Content 79 %
6. Frontend 100 %
7. Backend 100 %
8. Hosting 77 %
9. Algorithms 100 %

Page measurements

Mesure du 19 novembre 2026 sur 45 pages : note EcoIndex moyenne 84/100 (A).

Empreinte estimée par visite : moins de 0,01 g CO₂e en moyenne, environ 0,038 g pour la page la plus lourde (CO2.js, modèle Sustainable Web Design v4, électricité française, hébergement vert).

Page la plus lourde : 629,1 Ko (/de). Page la plus demandeuse : 21 requêtes (/de).

3 pages dépassent un seuil : /carte (C, 205,6 Ko, 11 requêtes), /de/speisekarte (C, 206,1 Ko, 11 requêtes), /en/menu (C, 205,6 Ko, 11 requêtes). Elles sont à corriger en priorité.

Each page is measured with every release using the EcoIndex (new tab) method: number of elements, number of requests and transferred weight. Thresholds set for each page: 1,000 KB and 40 requests at most, grade B at minimum.

Action plan

  • 1.1: Describe the site's usefulness for the business and its audience.
  • 1.2: Describe the target audiences and their needs.
  • 2.2: Test the essential functions on a laptop with a processor that is ten years old or more.
  • 2.3: Measure display on a slow connection (3G and 512 kbit/s).
  • 2.4: List the minimum supported browser versions (versions at least two years old).
  • 3.2: Document the server sizing, which is shared between the agency's sites.
  • 3.5: Distinguish fixes from enhancements in the shared code's version log.
  • 4.3: Check the main user journeys (contact, quote) using audience measurement.
  • 5.7: Check the compression of published documents (PDF).
  • 8.3: Scaleway's DC2 data center has a PUE of 1.50, right at the 1.5 threshold set by the criterion.
  • 8.7: Scaleway does not publish any heat recovery information for this data center.

Criteria details

1. Strategy (76%)

  • 1.1 · Under evaluation. Has the digital service been favorably assessed in terms of usefulness, taking its environmental impacts into account? (priority) Describe the site's usefulness for the business and its audience.
  • 1.2 · Under evaluation. Has the digital service defined its target users, business needs and the real expectations of those users? (priority) Describe the intended audiences and their needs.
  • 1.3 · Validated. Does the digital service have at least one designated lead for digital eco-design? (recommended) Eco-design lead: XMEDIACREATION (new tab), which designs and maintains the site (contact@sillaya.fr).
  • 1.4 · Validated. Does the digital service regularly carry out reviews to ensure its eco-design approach is followed? (priority) With each release, the site is built, validated and checked automatically, and each page is measured using the EcoIndex method (elements, requests, transferred weight). Performance is recorded every week. This statement is reviewed whenever the shared site code changes.
  • 1.5 · Validated. Has the digital service set objectives to reduce or limit its own environmental impacts? (priority) Each page is measured with every release using the EcoIndex method. Objectives: no page below grade B, and an RGESN progress score of at least 80% by the end of 2027.
  • 1.6 · Validated. Does the digital service collect data in a responsible and reasoned way? (recommended) The site collects only what visitors write in the contact form, kept for 3 years after the last exchange. No cookies or trackers: traffic is measured from server logs, with truncated IP addresses.
  • 1.7 · Validated. Does the digital service use a level of encryption suited to its needs? (moderate) Only encryption of exchanges (HTTPS) is used, with automatic redirection from HTTP.
  • 1.8 · Validated. Has the digital service made open-source efforts? (recommended) The shared site code is not published: it is part of the service. It is built on open-source software: Astro (site generation), Decap CMS (content editor), Pagefind (search with no external service), Leaflet (maps, IGN base layers), Node.js; checks with Playwright, axe-core, Lighthouse and the EcoIndex method; server running Debian with Caddy, PHP-FPM, GoAccess, age, zstd, rclone, Git and systemd; monitoring with Uptime Kuma. The content of each site is stored in open files (YAML, Markdown), reusable without us.
  • 1.9 · Validated. Was the digital service designed with interoperable standard technologies rather than specific, closed ones? (priority) Standard website (HTML, CSS, JavaScript as progressive enhancement): the same interface serves computers, tablets and phones, with no app to install.

Not applicable: 1.10 (the site does not control any connected object or peripheral).

2. Specifications (70%)

  • 2.1 · Validated. Has the digital service defined the list of hardware profiles that users can use to access it? (priority) The site works on a computer, tablet or phone with a browser less than three years old, including a ten-year-old laptop.
  • 2.2 · Under evaluation. Can the digital service be used on older device models? (priority) Test the essential functions on a laptop with a processor that is ten years old or more.
  • 2.3 · Under evaluation. Can the digital service be used over a low-bandwidth connection or offline? (recommended) Measure display on a slow connection (3G and 512 kbit/s).
  • 2.4 · Under evaluation. Can the digital service be used on older versions of operating systems and web browsers? (priority) List the minimum supported browser versions (versions at least two years old).
  • 2.5 · Validated. Does the digital service adapt to different types of display devices? (priority) Responsive layout, checked at widths of 390 and 1,280 pixels; menus usable by touch, mouse and keyboard.
  • 2.6 · Validated. Was the digital service designed with a design review and a code review that include reducing the environmental impacts of each feature among their objectives? (recommended) Every change is reviewed before publication and goes through automated checks (content, links, accessibility, page weight). The CSS of absent blocks is removed from each page.
  • 2.7 · Validated. Has the digital service planned a maintenance and decommissioning strategy? (priority) Updates to the shared code are included in the subscription, and unused features are removed from it. On termination, after one month's notice, the client receives a complete version of their site in standard files, ready to be hosted elsewhere; the client area and monitoring are shut down.
  • 2.8 · Validated. Does the digital service require its suppliers to guarantee an approach to reducing their environmental impacts? (priority) Hosting chosen for its renewable electricity and its published indicators (Scaleway). Third-party services reduced to the bare minimum (Google maps and reviews), never loaded without action from the visitor.
  • 2.9 · Validated. Has the digital service taken into account the environmental impacts of the ready-made interface components it uses? (moderate) No ready-made component library or browser-side JavaScript framework: the interface blocks are developed specifically for these sites.
  • 2.10 · Validated. Did the digital service take into account the environmental impacts of the third-party services used when selecting them? (priority) Third-party services are kept to a minimum and load nothing by default: the Google Maps map is displayed only on click, and Google reviews are built into the pages at build time, with no call from the browser.

3. Architecture (67%)

  • 3.1 · Validated. Is the digital service built on an architecture, resources or components designed to reduce their own environmental impact? (priority) Static site: pages are generated once, when the site is published, then served as simple files, with no database and no computation on each visit. Each page loads only the CSS for its own blocks.
  • 3.2 · Under evaluation. Does the digital service run on an architecture that can adjust the amount of resources used to match the service's consumption? (recommended) Document the sizing of the server, which is shared among the agency's sites.
  • 3.3 · Validated. Is the digital service able to support the technical evolution of protocols? (moderate) HTTPS enforced with automatic redirection, TLS 1.3, HTTP/2 and HTTP/3, IPv6 in place.
  • 3.5 · Under evaluation. Does the digital service allow corrective updates to be installed independently of feature updates, in a transparent way? (moderate) Distinguish fixes from new features in the version log of the shared code.
  • 3.6 · Validated. Does the digital service offer incremental updates, so that the entire code is not replaced with each update? (moderate) Updates transfer only the modified files to the server.
  • 3.7 · Validated. Does the digital service optimize its use of development, staging or test environments according to its needs? (moderate) No permanent staging server: the site is built on demand, when a change is made, and the build environment is then released.

Not applicable: 3.4 (the site is not sold with a device).

4. User experience and interface (93%)

  • 4.1 · Validated. Does the digital service include only animations, videos and sounds with autoplay disabled? (priority) No automatic video or sound playback, no automatic scrolling; the only animation (the "open" indicator) stops after three cycles and is not played if the visitor has asked to reduce motion.
  • 4.2 · Validated. Does the digital service display only content without infinite scroll? (priority) No infinite scroll.
  • 4.3 · Under evaluation. Does the digital service optimize the navigation path for each main feature? (recommended) Check the main paths (contact, quote) using audience measurement.
  • 4.4 · Validated. Does the digital service let the user decide whether to activate a third-party service? (recommended) No third-party service is activated without action from the visitor: the map loads when you click "Show map".
  • 4.5 · Validated. Does the digital service mainly use functional components native to the operating system, the browser or the language used? (moderate) Native browser forms, drop-down lists and buttons.
  • 4.6 · Validated. Does the digital service use only video, audio and animated content that carries information? (recommended) No video, no sound, no decorative animation.
  • 4.7 · Validated. Does the digital service choose the most frugal option among text, image, audio or video, according to user needs? (moderate) Text and images are preferred; no video or sound.
  • 4.8 · Validated. Does the digital service limit the number of fonts downloaded? (moderate) Fonts hosted with the site, in WOFF2 format and split by alphabet: less than 400 KB per page.
  • 4.9 · Validated. Does the digital service limit server requests during user input? (moderate) No autocomplete querying the server while typing.
  • 4.10 · Validated. Does the digital service tell the user the expected input format, avoiding unnecessary server requests when a form is submitted? (moderate) Expected formats are indicated and checked in the browser before the form is sent.
  • 4.11 · Validated. Does the digital service tell the user the expected file sizes and formats before transfer? (moderate) The number and formats of accepted photos are indicated before sending; photos are reduced in the browser before they are sent.
  • 4.12 · Validated. Does the digital service tell the user when using a feature has a significant environmental impact? (recommended) The site offers no feature with a high environmental impact.
  • 4.13 · Validated. Does the digital service limit the use of notifications, while allowing the user to turn them off? (priority) The site sends no notifications.
  • 4.14 · Validated. Does the digital service avoid manipulative techniques in its user interface? (recommended) No pop-up window, no consent banner, no pre-ticked box, no countdown.
  • 4.15 · Validated. Does the digital service give the user a means of control over their usage in order to monitor and reduce the associated environmental impacts? (recommended) Each page shows its estimated footprint per visit in its footer (CO2.js by the Green Web Foundation, Sustainable Web Design v4 model) and, if it scores A or B, its EcoIndex rating. The site is frugal by default, with no setting to turn on: no video or sound, images loaded as they come into view, limited fonts, no trackers. Measurements and methodology are detailed on this page.

5. Content (79%)

  • 5.1 · Validated. Does the digital service use a file format suited to the content and viewing context of each image? (recommended) Photos are converted to AVIF and WebP when the site is built.
  • 5.2 · Validated. Does the digital service provide images whose compression level is suited to the content and viewing context? (recommended) Photos are compressed at build time and provided in several widths.
  • 5.7 · Under evaluation. Does the digital service use a file format suited to the content and context of use for each document? (moderate) Check the compression of the documents published online (PDF).
  • 5.8 · Passed. Does the digital service have an automatic or manual strategy for archiving and deleting obsolete or outdated content? (recommended) News items older than two years are removed or archived; projects remain online as long as they are representative.

Not applicable: 5.3 (no video); 5.4 (no video); 5.5 (no video); 5.6 (no audio content).

6. Frontend (100%)

  • 6.1 · Passed. Does the digital service enforce a maximum weight and a request limit per screen? (recommended) Thresholds per page: 1,000 KB transferred and no more than 40 requests, with an EcoIndex grade of B or better. Each page is measured at every release (see "Measurements" above).
  • 6.2 · Passed. Does the digital service use caching mechanisms for all the transferred content under its control? (recommended) Static files (CSS, JavaScript, images, fonts) have versioned names and are kept in the browser cache for one year; pages are revalidated on every visit.
  • 6.3 · Passed. Does the digital service use compression techniques for the transferred resources under its control? (moderate) Text files (HTML, CSS, JavaScript, SVG) are compressed by the server.
  • 6.4 · Passed. Does the digital service mostly display images whose original dimensions match the dimensions of the display context? (recommended) Each photo is generated in several widths and the browser loads the one that fits the display; uploaded images are resized.
  • 6.5 · Passed. Does the digital service avoid triggering the loading of unused resources and content for each feature? (recommended) Only the CSS and scripts needed for the page are loaded; off-screen images are loaded as they come into view.
  • 6.7 · Passed. Does the digital service host all the static resources it transfers on a single domain? (moderate) All the site's resources, fonts included, come from its own domain, over HTTP/2.

Not applicable: 6.6 (the site does not use any device sensors).

7. Backend (100%)

  • 7.1 · Passed. Does the digital service use a server cache system for the most frequently used data? (recommended) Pages are generated in advance: each visit receives a ready-made file, with no server-side computation.
  • 7.2 · Passed. Does the digital service set retention periods for data and documents, with a view to deleting or archiving them once the period has elapsed? (recommended) Requests received via the form are kept for three years after the last exchange, then deleted; server logs are kept for twelve months.
  • 7.3 · Passed. Does the digital service inform the user of a process running in the background? (moderate) While the form is being submitted, the button is disabled and the message "Sending…" is displayed.

Not applicable: 7.4 (no blockchain).

8. Hosting (77%)

  • 8.1 · Passed. Does the digital service use a hosting provider with an approach to reducing its environmental footprint? (priority) Server hosted by Scaleway (new tab) in Paris (DC2 data center, PAR1 region). The host publishes its indicators (PUE, WUE, rDCE) and aims for a PUE below 1.15 for its new data centers and below 1.3 for existing ones.
  • 8.2 · Passed. Does the digital service use a hosting provider with a sustainable equipment management policy? (priority) Scaleway designs its own servers, aims for a lifespan of up to ten years, and reuses or recycles components at end of life.
  • 8.3 · Not passed. Does the digital service use a hosting provider whose PUE (Power Usage Effectiveness) is minimized? (priority) Scaleway's DC2 data center has a PUE of 1.50, right at the 1.5 threshold set by the criterion.
  • 8.4 · Passed. Does the digital service use a hosting provider whose WUE (Water Usage Effectiveness) is minimized? (recommended) WUE published by Scaleway for the DC2 data center: 0.012 L/kWh, below the target of 0.4 L/kWh.
  • 8.5 · Passed. Does the digital service use a hosting provider whose electricity sources are documented and mostly renewable? (recommended) 100% renewable electricity (hydropower for the DC2 data center), with guarantees of origin, according to Scaleway.
  • 8.6 · Passed. Does the digital service use a hosting provider whose geographic location is consistent with its activities and which minimizes its environmental footprint? (recommended) Server in France, where electricity has a low carbon intensity (under 100 g CO₂e/kWh), close to the site's visitors.
  • 8.7 · Not passed. Does the digital service use a hosting provider that handles the heat produced by the servers efficiently? (recommended) Scaleway does not publish any heat recovery for this data center.
  • 8.9 · Passed. Does the digital service duplicate data only when necessary? (recommended) Daily backup, compressed (zstd) and encrypted (age), stored on a Scaleway volume and then copied to an OVH server with graduated retention; Git repositories are also copied. Published files and certificates are not backed up, as they can be rebuilt. About 7 MB per archive.
  • 8.10 · Passed. Does the digital service take external constraints into account to minimize the environmental impact of asynchronous computing and data transfers? (recommended) Scheduled tasks (backups, copies, measurements) run at night, outside peak electricity consumption.

Not applicable: 8.8 (the site hosts far less than 10 TB of data).

9. Algorithms (100%)

  • 9.1 · Met. Did the digital service question the need for a training phase, to avoid unjustified and unreasonable use? (priority) The site does not use any artificial intelligence model: no training phase is needed.

Not applicable: 9.2 (no training phase); 9.3 (no training phase); 9.4 (no training phase); 9.5 (no training phase); 9.6 (no training phase); 9.7 (no model inference).

Contact

For any questions about this statement: contact@sillaya.fr.

Source of the criteria: Référentiel général de l’écoconception des services numériques (RGESN), 2024 version, Arcep / Arcom / ADEME, May 2024, reused without modification. The evaluation texts and measurements are those of XMEDIACREATION.