Skip to main content

LOGIN OR JOIN

logo

Eco Conception

1. We are committed to optimizing digital tools to limit their impact and consumption.

2. WE ARE COMMITTED TO DEVELOPING SERVICE OFFERS THAT ARE ACCESSIBLE TO ALL, INCLUSIVE, AND SUSTAINABLE.

3. WE ARE COMMITTED TO ETHICAL AND RESPONSIBLE DIGITAL PRACTICES.

4. WE ARE COMMITTED TO RESPONSIBLE DIGITAL PRACTICES THAT ARE ESSENTIAL FOR ENSURING THE RESILIENCE OF ORGANIZATIONS.

5. We are committed to promoting the emergence of new behaviors and values.

Sharewoop was designed and developed in accordance with eco-responsible best practices.

  • Eliminate non-essential features
  • Precisely quantify the need
  • Optimize the user journey
  • Prefer assisted input over autocompletion
  • Favor a simple, clean, web-friendly design
  • Prioritize a "mobile first" approach, or at least adaptive loading
  • Adhere to the principle of fast navigation through history
  • Offer asynchronous processing whenever possible
  • Limit the number of HTTP requests
  • Store static data locally
  • Favor static pages
  • Create a modular application architecture
  • Choose the most suitable technologies
  • Use performance-oriented application forks
  • Select an appropriate data format
  • Limit the number of domains serving resources
  • Replace official social media share buttons
  • Split CSS files
  • Limit the number of CSS files
  • Prefer CSS over images
  • Write efficient CSS selectors
  • Group similar CSS declarations
  • Use shorthand CSS notation
  • Provide a print CSS
  • Favor standard fonts
  • Prefer glyphs over images
  • Validate pages with the W3C
  • Externalize CSS and JavaScript
  • Do not resize images in the browser
  • Avoid using bitmap images for the interface
  • Optimize vector images
  • Use lazy loading
  • Use partial reloading of a content area
  • Avoid JavaScript/CSS animations
  • Only use essential portions of JavaScript libraries and CSS frameworks
  • Do not modify the DOM when traversing it
  • Make DOM elements invisible when modifying them
  • Minimize repaint (appearance) and reflow (layout)
  • Use event delegation
  • Modify multiple CSS properties at once
  • Validate your code with a Linter
  • Cache frequently accessed objects in JavaScript
  • Reduce DOM access via JavaScript
  • Use all levels of CMS caching
  • Optimize and generate media before importing them into a CMS
  • Encode sounds outside the CMS
  • Cache frequently used computed data
  • Eliminate all warnings and notices
  • Avoid SQL queries inside a loop
  • Only connect to a database when necessary
  • Optimize database queries
  • Avoid transferring large amounts of data for processing
  • Minify CSS, JavaScript, HTML, and SVG files
  • Compress CSS, JavaScript, HTML, and SVG files
  • Combine CSS and JavaScript files
  • Optimize images
  • Optimize cookie size
  • Favor HSTS Preload list over 301 redirects
  • Implement a site end-of-life plan
  • Choose an eco-friendly hosting provider
  • Favor an eco-friendly electricity provider
  • Adapt service quality and availability level
  • Use virtualized servers
  • Optimize server energy efficiency
  • Install the minimum required on the server
  • Cache entirely in RAM (opcode and kvs)
  • Store data in the cloud
  • Host resources (CSS/JS) on a cookie-free domain
  • Avoid redirects
  • Display static error pages
  • Use an asynchronous server
  • Use a CDN
  • Use HTTP caching
  • Add Expires or Cache-Control headers
  • Cache Ajax responses
  • Limit server logs to necessary information
  • Disable Apache DNS lookup
  • Apache Vhost: disable AllowOverride
  • Disable binary logs
  • Compress documents
  • Optimize PDFs
  • Limit heavy and redundant emails
  • Only use double opt-in files
  • Limit the size of sent emails
  • Adapt sounds to listening contexts
  • Adapt texts to the web
  • Adapt videos to viewing contexts
  • Limit analytics tools and collected data
  • Limit the use of animated GIFs
  • Avoid automatic video and sound playback and loading
  • Use CSS compartments
  • Provide a text alternative for multimedia content
  • Favor HTTP/2 over HTTP/1
  • Save bandwidth with a ServiceWorker
  • Implement an efficient sitemap
  • Ensure compatibility with the oldest devices and software in the park
  • Reduce stored data to the strict minimum
  • Implement a data expiration and deletion policy
  • Limit the use of canvases
  • Ensure user journeys allow them to complete their intended action
  • Have a page title and meta description relevant to the page content
  • Use the latest language version
  • Only load data/code when necessary
  • Eliminate unused features
  • Prefer a PWA over a similar native mobile app
  • Avoid blocking times with long JavaScript processing
  • Implement an elastic architecture
  • Limit the number of HTTP API calls
  • Limit the use of carousels
  • Have a content end-of-life strategy
  • Implement a "Circuit breaker"
  • Favor "Request collapsing"
  • Rely on managed services
  • Prefer pagination over infinite scrolling
  • Maintain your site regularly
  • Limit the number of extensions in a CMS
  • Secure access to the administration
  • Do not display documents inside pages

The "Web Eco-design Reference (REW)" is published by GreenIT.fr as part of the work of the Responsible Digital Design Collective under the terms of the Creative Commons Attribution - Non-Commercial - No Derivatives 4.0 International License. Based on a work available at https://collectif.greenit.fr/

This work, creation, site, or text is licensed under the Creative Commons Attribution - Non-Commercial - No Derivatives 4.0 International License. To view a copy of this license, please visit https://creativecommons.org/licenses/by-nc-nd/4.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.

🡽