voyager.lumafield.com/project/b82cd1db-b69d-4e93-ba42-c2c5e6c518c6

The numbers

First visit

61.91 g CO₂e

Return visit

18.64 g CO₂e

Hosting

unknown

LCP

2.40 s

CLS

0

TTFB

564 ms

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

1. Reduce JavaScript payloadsave ~0.101 g/visit (829 kB)High impact · moderate effort

   24 scripts total 3.32 MB on the wire (11.79 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.

   • index-BOYjUO_L.js1.80 MB
   • @mui-bundle-5N3JtF0c.js216 kB
   • js188 kB
   • gtm.js166 kB
   • js147 kB

   WSG 3.2: Minify and remove unused codeWSG 3.3: Modularize bandwidth-heavy components
2. Audit third-party servicessave ~0.078 g/visit (634 kB)High impact · moderate effort

   30 third-party domains account for 1.27 MB (0% 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.

   • www.googletagmanager.com789 kB
   • connect.facebook.net175 kB
   • fpjscdn.net71 kB
   • js.hs-analytics.net44 kB
   • snap.licdn.com42 kB
   • js.hubspot.com29 kB

   WSG 3.5: Treat third parties the same as first parties
3. 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.txtThe host publishes a carbon.txt; its evidence has not reached the Green Web Foundation dataset yet.

   WSG 4.1: Use sustainable hosting
4. Upgrade compression beyond gzipsave ~0.041 g/visit (338 kB)Advisory · quick fix

   2.25 MB 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.

   • index-BOYjUO_L.js1.80 MB
   • fbevents.js110 kB
   • 66134519955385365 kB
   • b82cd1db-b69d-4e93-ba42-c2c5e6c518c647 kB
   • 7802750.js44 kB

   WSG 4.3: Reduce data transfer with compression
5. Remove references to broken resourcessave ~<0.001 g/visit (516 B)Advisory · quick fix

   1 request answered 4xx/5xx on load: transfer and connections spent on nothing, on every single visit.

   Delete or fix the references (stale asset URLs, dead third-party tags). Each one is a request the page provably does not need.

   • c16b5e5d-1207-420f-8a2a-b4f70332f389HTTP 401 · 516 B

   WSG 4.4: Setup necessary error pages and redirection links
6. Set a page-weight budgetAdvisory · moderate effort

   At 417.73 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

• Data (fetch)414.37 MB · 28 req
• JavaScript3.32 MB · 24 req
• Images27 kB · 8 req
• Data (XHR)16 kB · 14 req
• CSS3.6 kB · 1 req
• HTML3.6 kB · 1 req
• Other844 B · 3 req