huggingface.co/learn

The numbers

First visit

1.10 g CO₂e

Return visit

0.973 g CO₂e

Hosting

unknown

LCP

1.26 s

CLS

n/a

TTFB

107 ms

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

1. Convert and compress imagessave ~0.423 g/visit (2.94 MB)High impact · quick fix

   12 images (6.53 MB) ship in legacy formats (JPEG/PNG/GIF).

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

   • huggy-learn.png1.74 MB
   • thumbnail.png1.44 MB
   • ml-for-games.png1.04 MB
   • smol-logo.png586 kB
   • thumbnail.png442 kB

   WSG 2.9: Optimize media to reduce resource use
2. Fix caching for returning visitorssave ~0.242 g/visit (1.63 MB)High impact · quick fix

   On a repeat visit 6.53 MB of static assets were re-downloaded instead of coming from cache.

   Serve static assets with Cache-Control: public, max-age=31536000, immutable and versioned filenames so returning visitors download almost nothing.

   • huggy-learn.pngno Cache-Control header · 1.74 MB
   • thumbnail.pngno Cache-Control header · 1.44 MB
   • ml-for-games.pngno Cache-Control header · 1.04 MB
   • smol-logo.pngno Cache-Control header · 586 kB
   • thumbnail.pngno Cache-Control header · 442 kB

   WSG 4.2: Optimize caching and support offline access
3. Audit third-party servicessave ~0.041 g/visit (284 kB)High impact · moderate effort

   4 third-party domains account for 568 kB (8% 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.com312 kB
   • js.stripe.com252 kB
   • cdnjs.cloudflare.com3.3 kB
   • 0 B

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

   57 scripts total 740 kB on the wire (2.22 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.js308 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
5. 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.

   WSG 4.1: Use sustainable hosting
6. Upgrade compression beyond gzipsave ~0.0073 g/visit (51 kB)Advisory · quick fix

   338 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.js308 kB
   • learn28 kB
   • telemetry1.4 kB

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

   At 7.44 MB per view this page rates F. 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

• Images6.53 MB · 13 req
• JavaScript740 kB · 57 req
• CSS87 kB · 2 req
• Fonts46 kB · 3 req
• HTML28 kB · 2 req
• Data (fetch)3.6 kB · 3 req