Carbon report
blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption
Scanned · all pages on blog.google
0.078 g
cleaner than an estimated 90.2% of pages on the web
- A+
- A
- B
- C
- D
- E
- F
A+ is 0.04 g or less per view, F is more than 0.359 g CO₂e.
The numbers
- 0.101 g CO₂e
- 0.0073 g CO₂e
- verified green
- 456 ms
- 0.023
- 234 ms
At 10,000 views a month this page emits about 9.3 kg CO₂e a year, roughly 38 km in an average petrol car. The estimate assumes 75% new and 25% returning visitors, a measured cache reload ratio of 7%, and world-average grid intensity. How we calculate this
What to fix
apply everything → ~0.040 g/visit, rating A
Audit third-party servicessave ~0.023 g/visit (243 kB)Medium impact · moderate effort
8 third-party domains account for 486 kB (58% 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.com294 kB
- fonts.gstatic.com113 kB
- www.gstatic.com31 kB
- storage.googleapis.com25 kB
- cdn.ampproject.org18 kB
- fonts.googleapis.com4.0 kB
Reduce JavaScript payloadsave ~0.0094 g/visit (101 kB)Medium impact · moderate effort
18 scripts total 405 kB on the wire (1.21 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.
- js154 kB
- gtm.js140 kB
- index.js46 kB
- cookienotificationbar.min.js28 kB
- amp-story-player-v0.js18 kB
Upgrade compression beyond gzipsave ~0.0054 g/visit (58 kB)Advisory · quick fix
384 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.
- index.min.css71 kB
- icons.svg70 kB
- icons.svg70 kB
- how-google-is-making-private-ai-practical-wit…63 kB
- index.js46 kB
Where the bytes are
- JavaScript405 kB · 18 req
- Other140 kB · 2 req
- Fonts113 kB · 4 req
- CSS89 kB · 14 req
- HTML63 kB · 1 req
- Images25 kB · 6 req
- Data (fetch)622 B · 2 req
Ten heaviest requests
| Resource | Type | Wire size | Cache-Control |
|---|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-TMN2946Z0E&cx=c>m=4e68c1 | script | 154 kB | private, max-age=900 |
| www.googletagmanager.com/gtm.js?id=GTM-TRV24V | script | 140 kB | private, max-age=900 |
| blog.google/static/keyword/css/blog/index.min.css?version=pr20260729-1718 | stylesheet | 71 kB | public, max-age=31536000 |
| blog.google/static/blogv2/images/icons.svg?version=pr20260729-1718 | other | 70 kB | public, max-age=31536000 |
| blog.google/static/blogv2/images/icons.svg?version= | other | 70 kB | public, max-age=31536000 |
| blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption/ | document | 63 kB | n/a |
| blog.google/static/keyword/js/all/index.js?version=pr20260729-1718 | script | 46 kB | public, max-age=31536000 |
| fonts.gstatic.com/s/googlesans/v70/4UasrENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RPjIUvQ.woff2 | font | 37 kB | public, max-age=31536000 |
| fonts.gstatic.com/s/googlesansflex/v22/t5sEIQcYNIWbFgDgAAzZ34auoVyXkJCOvp3SFWJbN5hF8Ju1x6sKCyp0l9sI40swNJwInycYAJzz0m7kJ4qFQOJBOjLvDSndo0SKMpKSTzwliVdHAy4bxTDHg_ugnAakp8ubq8BIo1pdkkXZj4iNdvKMDV8.woff2 | font | 34 kB | public, max-age=31536000 |
| www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.js | script | 28 kB | private, max-age=3000 |
Share this report
<a href="https://carbonless.cc/report/blog.google/security/how-google-is-making-private-ai-practical-with-homomorphic-encryption"><img src="https://carbonless.cc/api/badge?url=https%3A%2F%2Fblog.google%2Fsecurity%2Fhow-google-is-making-private-ai-practical-with-homomorphic-encryption" alt="Carbon rating for this page" width="150" height="30" loading="lazy" /></a>The badge is a lightweight SVG (under 1 kB) served with long-lived caching, so a new scan can take up to a day to show through.