The way this
Indaru Ecometrics plugin handles emissions seems pretty sketchy. It's basically just using a formula where the estimate grows based on how long the page stays open. If someone leaves a tab running for five hours, the carbon footprint just keeps climbing. I checked out how they do it and it's all about that base_a + base_b * t calculation. They're pulling device type and country code via a network request to get some fixed factors. It definitely beats those old calculators that only look at page weight and grid intensity. But tracking time on page as a primary driver for CO2 feels like it could easily skew the data if you have high bounce rates or just idle tabs. It's also hard to trust any of this when the broader ICT sector stats are so vague, anywhere from 1.5% to 4%. I'd love to see how this handles heavy single-page apps where the initial load is tiny but the session lasts forever. It feels like another metric that might look good in a dashboard but lacks real precision for actual reporting.
article:
https://www.debugbear.com/blog/indaru-ecometrics-website-carbon-footprint-plugin