huggingface.co

The numbers

First visit

0.448 g CO₂e

Return visit

<0.001 g CO₂e

Hosting

unknown

LCP

536 ms

CLS

n/a

TTFB

10 ms

At 10,000 views a month this page emits about 40.3 kg CO₂e a year, roughly 165 km in an average petrol car. The estimate assumes 75% new and 25% returning visitors, a measured cache reload ratio of 0%, and world-average grid intensity. How we calculate this

1. Lazy-load below-the-fold mediasave ~0.051 g/visit (456 kB)High impact · quick fix

   15 below-the-fold images/iframes (911 kB) download immediately for every visitor.

   Add loading="lazy" to below-fold img and iframe elements (and keep it off the LCP image). Browsers then fetch them only when scrolling approaches.

   • younes.svg397 kB
   • hugs.svg220 kB
   • activity.svg168 kB
   • modalities.svg31 kB
   • providers.svg23 kB

   WSG 2.9: Optimize media to reduce resource use
2. Audit third-party servicessave ~0.031 g/visit (275 kB)High impact · moderate effort

   4 third-party domains account for 550 kB (18% of the page).

   Remove services that no longer earn their place; load the rest on interaction (facades for embeds, delayed consent-gated tags). Each third party is also a privacy and performance dependency.

   • de5282c3ca0c.edge.sdk.awswaf.com294 kB
   • js.stripe.com252 kB
   • cdnjs.cloudflare.com3.3 kB
   • 0 B

   WSG 3.5: Treat third parties the same as first parties
3. Reduce JavaScript payloadsave ~0.020 g/visit (182 kB)High impact · moderate effort

   60 scripts total 729 kB on the wire (2.19 MB decoded). Bundles this size usually carry a lot of unused code.

   Split bundles per route, tree-shake dependencies, and audit with a bundle analyzer or coverage profile. A 25% cut is a conservative target for bundles this size.

   • challenge.js290 kB
   • v3252 kB
   • index.js48 kB
   • ViewUtils-OpAoqUBd.js38 kB
   • index-client-CkQhurOl.js28 kB

   WSG 3.2: Minify and remove unused codeWSG 3.3: Modularize bandwidth-heavy components
4. Serve images at the size they displaysave ~0.031 g/visit (279 kB)Medium impact · quick fix

   4 images are encoded at more than twice the pixels the layout shows, even accounting for this viewport's pixel density.

   Generate multiple sizes and let the browser pick with srcset/sizes; a 4000px original behind a 400px slot spends bandwidth no screen displays.

   • younes.svg397 kB
   • hugs.svg220 kB
   • models.webp119 kB
   • compute.svg22 kB

   WSG 2.9: Optimize media to reduce resource use
5. Convert and compress imagessave ~0.022 g/visit (202 kB)Medium impact · quick fix

   2 images exceed 300 kB apiece.

   Serve AVIF (or WebP) with responsive srcset sizes, and re-compress oversized files. AVIF typically halves JPEG weight at the same visual quality.

   • younes.svg397 kB
   • younes-dark.svg307 kB

   WSG 2.9: Optimize media to reduce resource use
6. Verify your hosting energyMedium impact · moderate effort

   This host has not published renewable energy evidence with the Green Web Foundation, so its energy source is unknown.

   Choose a provider listed in the Green Web Directory, or ask your current provider to publish evidence (and a carbon.txt). This cuts the data-center share of every single page view.

   • carbon.txtNo carbon.txt found at the site root; publishing one is the lightest first step.

   WSG 4.1: Use sustainable hosting
7. Upgrade compression beyond gzipsave ~0.0050 g/visit (45 kB)Advisory · quick fix

   298 kB of text ships gzip-compressed; Brotli or Zstandard would cut roughly another 15-20%, and browsers without them fall back to gzip automatically.

   Serve precompressed Brotli for static text assets (highest level, compressed at build time) and enable Brotli or zstd for dynamic responses; keep gzip only as the fallback.

   • challenge.js290 kB
   • ProductBanners-CAFfk7n_.js2.5 kB
   • index-client-_NYYaho6.js2.2 kB
   • motion-D-uF7TbO.js1.6 kB
   • telemetry1.4 kB

   WSG 4.3: Reduce data transfer with compression
8. Set a page-weight budgetAdvisory · moderate effort

   At 3.02 MB per view this page rates E. The findings above list where the weight is.

   Agree a transfer budget (e.g. under 975 kB reaches a B), enforce it in CI, and re-scan after each change to hold the line.

   WSG 3.1: Set goals based on performance and energy impact

Where the bytes are

• Images2.12 MB · 27 req
• JavaScript729 kB · 60 req
• CSS87 kB · 2 req
• Fonts61 kB · 4 req
• HTML24 kB · 2 req
• Data (fetch)3.6 kB · 3 req

Trend