tailscale.com

The numbers

First visit

0.524 g CO₂e

Return visit

0.088 g CO₂e

Hosting

unknown

LCP

252 ms

CLS

0.22

TTFB

78 ms

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

1. Audit third-party servicessave ~0.112 g/visit (951 kB)High impact · moderate effort

   24 third-party domains account for 1.90 MB (54% 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.

   • cdn.sanity.io979 kB
   • www.googletagmanager.com740 kB
   • snap.licdn.com40 kB
   • www.redditstatic.com33 kB
   • cdn.rudderlabs.com32 kB
   • scripts.clarity.ms26 kB

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

   49 scripts total 1.58 MB on the wire (4.74 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.

   • 3vj7wgh3koo6n.js231 kB
   • js192 kB
   • js192 kB
   • js190 kB
   • gtm.js166 kB

   WSG 3.2: Minify and remove unused codeWSG 3.3: Modularize bandwidth-heavy components
3. Convert and compress imagessave ~0.024 g/visit (205 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.

   • af5c10c534518d99737ba515229b2da310feabd8-806x…393 kB
   • a88cf9aad8777f4b0641202a5ed6c02bbb005d8c-266x…317 kB

   WSG 2.9: Optimize media to reduce resource use
4. Fix caching for returning visitorssave ~0.0020 g/visit (13 kB)Medium impact · quick fix

   On a repeat visit 54 kB 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.

   • events-webinars-og-imageCache-Control: public · 49 kB
   • s0inv2qfklCache-Control: no-cache, no-store · 843 B
   • 07d853f507039b2489d9818cb6ee7442c1b60e2a-30x1…Cache-Control: public, max-age=31536000, s-maxage=2592000 · 661 B
   • collectno Cache-Control header · 508 B
   • GA4.min.jsCache-Control: max-age=3600 · 340 B

   WSG 4.2: Optimize caching and support offline access
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.

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

   WSG 4.1: Use sustainable hosting
6. Optimize web fontssave ~0.0069 g/visit (59 kB)Advisory · quick fix

   3 font files total 168 kB.

   Subset fonts to used glyphs, prefer one variable font over multiple weights, serve WOFF2 only, and consider system fonts for UI text.

   • MDIO_VF-s.p.33edr4bt_fhb7.woff283 kB
   • Inter_var_italic_latin-s.p.0drijf_kb0ae0.woff246 kB
   • Inter_var_latin-s.p.2mp7er-_xfdzs.woff239 kB

   WSG 2.11: Use optimized web typography
7. Upgrade compression beyond gzipsave ~0.0022 g/visit (18 kB)Advisory · quick fix

   122 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.

   • insight.min.js21 kB
   • pixel.js21 kB
   • insight.old.min.js19 kB
   • bat.js16 kB
   • pixel.js13 kB

   WSG 4.3: Reduce data transfer with compression
8. Remove references to broken resourcessave ~<0.001 g/visit (883 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.

   • externalHTTP 403 · 883 B

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

   At 3.53 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
10. Simplify the document structureAdvisory · larger effort

    The page renders 2820 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.

    Flatten wrapper markup, render long lists virtually or paginate, and prefer semantic elements over nested divs.

    WSG 3.6: Ensure code follows good semantic practices

Where the bytes are

• JavaScript1.58 MB · 49 req
• Images1.05 MB · 35 req
• Data (fetch)659 kB · 113 req
• Fonts168 kB · 3 req
• HTML41 kB · 1 req
• CSS22 kB · 2 req
• Data (XHR)6.6 kB · 6 req
• Other939 B · 6 req