Make your website use less water
Why a website uses water
Every page you send goes through servers and networks. They use electricity and get hot. Many data centres are cooled with water, and making electricity uses water too. Sending less data means less energy and less water.
Ten simple, free steps
- Lighter images: WebP or AVIF, at the right size, with
srcsetso phones get a small version. - Lazy loading:
loading="lazy"anddecoding="async"for images below the fold. - Long cache:
Cache-Control: max-age=31536000, immutablefor files whose name changes with each version. - Static site and CDN: fixed pages, served close to the visitor, with no work on each visit.
- No autoplay video or audio: only play when the person clicks.
- Less JavaScript: remove what is unused, load the rest only on the page that needs it.
- Honour
prefers-reduced-motionand pause animations when the tab is hidden. - Few third-party scripts: no trackers or needless widgets.
- Fonts: few weights, WOFF2, split by alphabet.
- Measure: test your pages with a tool like EcoIndex, before and after.
What Lapis does
- Static pages on a CDN, with no database and no live AI.
- WebP images in three sizes (srcset), lazy-loaded below the first screen.
- WOFF2 fonts split by alphabet: only the needed alphabet is downloaded.
- No trackers, no ads, no autoplay video.
- Game animations pause when the tab is hidden, and “reduce motion” is respected.
Weight measured at first load (390 px phone)
| Page | Before | After |
|---|---|---|
| Accueil /fr/ | 486 KB | 487 KB |
| Jeu /fr/jeu/ | 381 KB | 382 KB |
| Musique /fr/musique/ | 217 KB | 218 KB |
Sources
This guide is free. It recommends no product.