What does Lemwatch monitor?

Lemwatch runs 20+ automated checks per site: uptime, response time, SSL/TLS expiry, domain expiry, DNS changes, sitemap health, broken links, content changes, SEO audits, mobile usability, security headers, and more.

Yes. The free tier monitors up to 5 sites. Pro is $19/month for 50 sites and Agency is $59/month for 100 sites, both with full feature access.

How is Lemwatch different from UptimeRobot or Pingdom?

Lemwatch bundles uptime, change detection, SEO audits, security scans, and a public API in one platform — features competitors charge separately for. It also includes team workspaces, white-labelled status pages, and a webhook system out of the box.

Does Lemwatch send alerts?

Yes. Lemwatch supports email, browser push, webhooks, and per-site notification routing so the right person hears about the right incident.

Is there a public API?

Yes. Pro and Agency plans get a public REST API with webhooks for sites, checks, incidents, and reports.

How accurate is a website carbon estimate?

It is a model built on published averages for network, data centre and device energy use. The absolute figure carries real uncertainty; the relative figure — this page against the average, or against itself last month — is reliable enough to act on.

What is the fastest way to reduce a page's carbon?

Images, almost always. Resize them to the dimensions actually displayed, serve a modern format, and lazy-load anything below the fold. On most sites that is the single largest reduction available and it speeds the page up at the same time.

Does green hosting really change the result?

Yes, because the data centre portion of the energy is served from renewable generation. It does not reduce the energy used by networks and devices, so a heavy page on green hosting still produces more than a light page.

Does a lighter page rank better?

Not for its carbon figure, but page weight drives loading performance, and loading performance is part of the page experience signals. The two improvements come from the same work.

Why does the estimate change between runs?

Transferred bytes vary with which advertisements, embeds and third-party scripts load on a given request. Run it a few times and use the range rather than treating a single figure as exact.

Should I count repeat visits?

The estimate models an uncached first visit, which is the worst case. Returning visitors transfer far less because assets are cached, so a site with high repeat traffic has a lower real average than the figure shown.

Free Tool

Updated 7 June 2026

website carbon calculator

Estimate the CO₂ emissions of any web page. See how your site compares to others and get tips to reduce your carbon footprint.

By Deepak Shukla — Founder & CEO, Pearl Lemon

Enter your URL

What This Tool Checks

CO₂ emissions per page view (grams)
Page weight and transfer size
Green hosting verification
Energy consumption estimate (kWh)
Comparison vs. global average

Why This Matters

The internet produces ~4% of global CO₂ emissions. Lighter, more efficient websites are better for the planet, load faster, and rank higher in search results.

How to Fix Issues

1.Optimise and compress images (use WebP/AVIF)
2.Minify CSS and JavaScript
3.Switch to green web hosting
4.Implement effective caching
5.Reduce third-party scripts

Every page view moves data across networks and runs processors in a data centre, and all of that consumes electricity. Enter a URL above and this calculator estimates the carbon produced by a single view of the page, based on how much data it transfers and whether the hosting runs on renewable energy.

What actually drives the number

Page weight dominates. Images that were never resized, video that autoplays, font files loaded in weights nobody uses, and analytics and advertising scripts that each pull in more scripts — these are the whole story on most sites. The second factor is the hosting: the same page served from a data centre running on renewable power produces substantially less carbon than one that is not, which is a decision made once and applied to every view thereafter.

The convenient part of this problem

Reducing a page's carbon and making it faster are the same work. Compressing images, serving modern image formats, removing unused JavaScript, subsetting fonts and deleting the tag that was added for a campaign three years ago all cut transfer size, which cuts both load time and energy use. There is no trade-off to manage: a lighter page is faster for users, cheaper to serve, better for Core Web Vitals and lower carbon, in one change.

Reading the estimate honestly

This is a model, not a measurement. It uses the transferred bytes of the page, published averages for network and device energy intensity, and a grid carbon factor. It cannot see repeat-visit caching, individual device efficiency, or the real energy mix of a specific facility at a specific hour. Treat the absolute gram figure as an indicator and the comparison over time as the useful output: measure, make the page lighter, measure again, and watch the direction.

Turning one measurement into a habit

Page weight creeps. A site that was lean at launch gains a widget here and a hero video there, and nobody notices until it is twice the size. The value is in re-checking after releases and watching the trend, which is the same discipline as performance monitoring — and for the same reason, since the two numbers move together.

Methodology

We load the URL you enter and total the bytes transferred for the document and its subresources, then apply a published energy-intensity model to convert transferred data into estimated electricity use across the network, the data centre and the end-user device. That figure is multiplied by a grid carbon intensity factor to produce grams of CO2 for a single page view. Separately we check the hosting provider against the Green Web Foundation's public registry of providers running on renewable energy, and apply a lower intensity factor when the host is listed. The result is compared against a published global average page weight so the number has context rather than standing alone. This is an estimate built on averages: it assumes an uncached first visit, uses representative rather than measured device efficiency, and cannot know the real-time energy mix of the specific facility serving you. Use it to compare a page against itself over time and against the average, not as an audited carbon figure.

Frequently Asked Questions

Monitor this continuously with LemWatch

A one-off free website carbon calculator shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.