Core concepts you need to know
Website carbon footprint
The total greenhouse gas emissions associated with delivering a website to users over a defined period. It typically includes emissions from data transfer, server compute, and client device energy use. The footprint is usually expressed in kilograms or grams of carbon dioxide equivalent per page load or per period of traffic.
Carbon dioxide equivalent
Often written as CO2e, this is a single unit that converts different greenhouse gases into the same warming potential as carbon dioxide. Using CO2e lets practitioners aggregate emissions from electricity, refrigerants, and other greenhouse gases into a single number.
Carbon intensity
Carbon intensity describes the amount of CO2e released per unit of electricity generated, commonly expressed in grams of CO2e per kilowatt hour. It is a location and time dependent factor that converters use to turn energy consumption into emissions.
Operational emissions
Emissions that result from running infrastructure and delivering content. For websites this covers the electricity consumed by servers, network equipment, CDNs, and end user devices while rendering pages and handling interactions.
Embodied emissions
Emissions embedded in the manufacture and disposal of hardware. While important for long term assessments, embodied emissions are usually considered separately from operational emissions when evaluating page level changes.
Performance and delivery metrics that feed carbon calculations
Page weight
Amount of data transferred to render a page, measured in bytes. Page weight is a primary driver of network energy use because larger transfers require more router and transmission energy and often more client processing. Reducing unnecessary bytes reduces both user wait time and the data transfer portion of the footprint.
Number of requests
Total HTTP requests required to load a page. Each request adds protocol overhead and may trigger extra round trips and server work. Reducing requests can lower both latency and energy consumed by client and network equipment.
First Contentful Paint
A Core Web Vital that measures the time until the browser paints the first piece of content. Faster values usually mean less idle device time and lower perceived energy cost. Core Web Vitals are relevant to SEO because search engines use them as ranking signals.
Largest Contentful Paint
Another Core Web Vital that reports time to the largest visible element. It correlates with user perception of page usefulness and with the duration the device and network are actively working to render the main content.
Time to Interactive
Time until the page is reliably responsive to user input. Long interactive delays often signal heavier client CPU work and therefore higher device energy use per visit.
Total CPU time and main thread work
Measured either in browser profiling or synthesized lab runs, CPU time quantifies how much processor work a page triggers. Higher CPU time often translates to more energy use on client devices and on any servers that perform dynamic rendering.
Server processing per request
Server CPU cycles and memory use attributed to serving a page. This metric matters when pages are dynamically generated or when server side rendering is used. Lower server processing reduces energy at the origin and any cloud or edge compute tiers consumed.
Emission calculation components and methods
Measurement boundary
Defines what is included in an assessment. Common boundaries include only the client network transfer, client device work, server compute, or a combined scope. Be explicit about boundaries because they determine which optimisations will show up in reported numbers.
Conversion model
The formula used to convert bytes and CPU work into energy, and energy into CO2e. Conversion requires assumptions about device power draw, network equipment energy per byte, and electricity carbon intensity. Different tools use different models and assumptions, so avoid comparing raw numbers from mismatched tools without normalising the method.
Per visit versus aggregate metrics
Per visit metrics express emissions for a single page load. Aggregate metrics scale per visit values by actual traffic over a period. Per visit metrics are useful for A B tests and micro optimisations. Aggregate metrics are necessary for reporting total organisational impact.
Attribution rules
Decisions about which component receives emissions when content is cached, served from a CDN, or processed in third party services. Clear attribution rules help teams avoid double counting and make trade offs transparent when changing CDN or caching strategies.
SEO specific terms and why they matter
Core Web Vitals
A defined set of performance metrics that search engines use to evaluate user experience. These metrics matter for both search ranking and for carbon because improving Core Web Vitals typically reduces unnecessary network and client work.
Indexing and crawl budget
How search engines allocate crawling resources to a site. Heavier pages and pages with multiple redirects can increase crawl load. Optimising payloads and server response behaviour can reduce the energy search engine crawlers consume while crawling the site and improve SEO efficiency.
Structured data and payload overhead
Structured data helps search engines understand content. Use lightweight JSON LD snippets and avoid redundant large schemas. The content benefit must be balanced against payload cost; structured data should be useful for indexing or rich results to justify its size.
Mobile first and device variability
Search engines prioritise mobile experience. Mobile devices often have less efficient radios and smaller batteries, which can change the relationship between bytes and emissions. Measuring on representative mobile profiles is important when prioritising SEO and carbon reductions.
How to use these metrics in practical SEO work
Choose the right primary metric for your goal
If the immediate aim is to reduce user friction and improve SEO signals, focus on Core Web Vitals and page weight. If the aim is to report organisational carbon, choose a boundary and aggregate per visit emissions across real traffic.
Prefer measurement over guesswork
Run lab tests for comparability and field measurements for real world impact. Use consistent conversion models when you report changes so stakeholders see true improvements rather than artifacts of different tools.
Audit auditability and transparency
Document the measurement boundary, the conversion model, and the carbon intensity assumptions. That makes results reproducible and prevents accusations of greenwashing when numbers are published for SEO or sustainability pages.
Decision criteria when trading page features for emissions
Ask whether a feature materially improves search visibility or user conversion and whether a lighter alternative exists. Prioritise changes that reduce bytes or CPU without reducing content quality that search engines value.
Common questions site owners ask
Will reducing page weight always improve SEO
Not always. Reducing unnecessary bytes usually improves load times and Core Web Vitals which helps SEO. However removing content or structured data that helps ranking can harm visibility. Test and measure the SEO impact before removing ranking signals.
Which metric should I display on a sustainability page
Publish both a per visit CO2e value and an aggregate period total with clear boundaries and assumptions. Include a short explanation of the conversion model and the carbon intensity used so readers can interpret the numbers reliably.
Can I compare emissions across tools
Only if the tools use the same boundary and conversion assumptions. When comparing, normalise for traffic, device profile, and carbon intensity, or report relative improvements from the same baseline test setup.
Practical next steps for SEO and sustainability teams
Set a clear measurement boundary
Choose whether you report per page load, per session, or site wide. Record the devices and locations used for measurements and the carbon intensity assumptions.
Map SEO signals to carbon drivers
Identify which SEO relevant elements cause the biggest bytes or CPU cost. Common examples include large images, third party embeds, and heavy client side scripts. Prioritise fixes that retain SEO value while reducing transfer and compute.
Report both performance and carbon
Include Core Web Vitals and the per visit CO2e number in optimisation reports. This helps teams connect SEO improvements with sustainability outcomes and choose the changes that deliver both user and environmental benefits.