Skip to content

www.w3.org: sustainability audit

At a glance

  • 37.0/100 — scoped audit score
    10 passing, 2 with problems, 15 needing more evidence.
  • 7 pages reviewed
    1 visitor journey; public-site evidence.
  • 27 of 71 guideline groups scored
    44 untested; 0 not applicable. Tests cover selected aspects of each guideline.

W3C’s standards and introductory resources provide a useful HTML reading baseline, and the sampled catalog route reaches WCAG 2.2 without an account. Add a main-content landmark to the long WCAG report, then investigate video activation on the sustainability page and the catalog’s expanded print output. Six initial transfer captures are complete within the protocol; the sustainability page remains incomplete because its embedded frame may be missing traffic. Browser-energy collection failed, so browser/network energy and the annual client-energy projection are unavailable. The public sustainability mission provides wider context but does not establish operational results for www.w3.org.

Results by WSG area

Selected checks by WSG area
AreaPassingGuideline groups checkedNeeds evidence
User experience design58% (7/12)12 of 175
Web development0% (0/8)8 of 166
Hosting, infrastructure and systems67% (2/3)3 of 121
Business strategy and product management25% (1/4)4 of 263

Passing percentages apply to the selected checks. Full-guideline conformance has not been established.

Page measurements

Page measurements
PageFirst loadAfter waitingAfter scrollingEstimated footprintCarbon ratingBrowser energyNetwork energy
Homepage532.5 kB532.5 kB532.5 kB0.08 gCO₂eAUnavailableUnavailable
W3C standards and drafts260.3 kB260.3 kB260.3 kB0.04 gCO₂eA+Not sampledNot sampled
Web Content Accessibility Guidelines (WCAG) 2.2120.8 kB120.8 kB120.8 kB0.02 gCO₂eA+UnavailableUnavailable
Accessibility Fundamentals Overview641.6 kB641.6 kB641.6 kB0.10 gCO₂eBNot sampledNot sampled
Images Tutorial149.7 kB149.7 kB149.7 kB0.02 gCO₂eA+Not sampledNot sampled
Web Sustainability1.350 MB · partial1.350 MB · partial1.354 MB · partialWithheldWithheldNot sampledNot sampled
Contact182.3 kB182.3 kB182.3 kB0.03 gCO₂eA+Not sampledNot sampled

Estimated annual footprint

A traffic scenario of 24,937,909 pageviews/year gives the estimates below. These are alternative views of overlapping activity, so they should not be added together.

Annual footprint and improvement scale
ScopeAnnual estimateIf per-view impact fell by 10%
Site browsing · SWDM v4 · partial transfers1,709.34 kgCO₂e/year170.93 kgCO₂e/year less

The 10% column shows the scale of a hypothetical improvement, not a predicted saving from the findings below.

Client-energy projection unavailable: No complete client-energy scenarios.

Priorities

1. Give the WCAG report a main-content landmark

Medium priority · Problem found · WSG 3.6: Ensure code follows good semantic practices

What we found. The full WCAG 2.2 page has a primary heading and language declaration, but no main-content landmark was recorded. The other six sampled pages provide one.

Why it matters. A main landmark gives people using assistive navigation a direct way to locate the report’s primary content, especially in a long normative document.

Next step. Wrap or identify the normative content as main, keep its table of contents as navigation, and verify landmark traversal reaches the report. Retain the complete HTML text.

How we checked this: Give the WCAG report a main-content landmark

2. Check a lighter way to open the sustainability video

Medium priority · Needs investigation · WSG 3.3: Modularize bandwidth-heavy components

What we found. The sustainability page starts loading an external video environment before the visitor chooses playback. Its initial transfer is incomplete at about 1.35 MB, so the full cost and a tested alternative remain unresolved.

Why it matters. Visitors can read the page without playing the video. Loading the player on request could reduce initial work, but only a functional comparison can establish whether that approach serves readers and saves transfer.

Next step. Test a lightweight preview with an explicit play control. Verify keyboard access, captions and playback, then compare matched complete visits with the current embed before deciding whether to adopt it.

How we checked this: Check a lighter way to open the sustainability video

3. Check the catalog’s expanded print output

Medium priority · Needs investigation · WSG 2.13: Reduce the impact of downloadable and physical documents

What we found. The catalog’s print state includes substantially more text than its screen state. The audit did not inspect printed pagination or determine whether the expanded report and history details belong in the reader’s intended list.

Why it matters. Unexpected expansion may make a printed list harder to use, while historical report details may have continuing reference value. Text length alone does not establish wasted pages.

Next step. Inspect the actual printed pages for representative filtered and unfiltered lists. Retain necessary version/status details and select print defaults that match the reader’s task; verify the revised output before claiming a paper reduction.

How we checked this: Check the catalog’s expanded print output

Further checks

These outcomes apply to the selected checks and sample. Open a check's explanation for the observation, limitations and useful follow-up.

Browse all check outcomes

All selected check outcomes
CheckOutcome
Reading tasks remain in view Passed this check
Check applicable choices before judging their fairness Needs investigation
Resources explain their audience and purpose Passed this check
Different templates support recognizable tasks Passed this check
Inspect the WAI link-transition effects Needs investigation
No unsolicited permission request was observed Passed this check
Check what the catalog includes when printed Needs investigation
Check code use during the relevant interactions Needs investigation
Investigate loading the sustainability video on request Needs investigation
Complete the tasks at narrow widths Needs investigation
Check whether media or print guidance would be useful Needs investigation
The catalog route reaches WCAG 2.2 Passed this check
Inspect image detail before reducing renditions Needs investigation
Typography includes fallback strategies Passed this check
Give the WCAG report a main-content landmark Problem found
Clarify canonical URLs for catalog filters Needs investigation
Check the applicable preference controls and effects Needs investigation
Core reading content remains without JavaScript Passed this check
Trace repeated requests to their purpose Needs investigation
Reusable assets provide caching or validation Passed this check
Material text responses are compressed Passed this check
Verify focus indicators on corporate controls Needs investigation
Look for a statement about operating www.w3.org Needs investigation
A discoverable carbon.txt was not found Problem found
Establish operational hosting evidence for this origin Needs investigation
The sampled report-reading route needs no account Passed this check
Keep useful standards history and explain review triggers Needs investigation
Separate the sustainability mission from website targets Needs investigation

Next steps for auditing

  1. Add the WCAG main-content landmark and verify landmark navigation through the complete report.
  2. Test a user-activated video preview with usable playback and captions, then compare complete initial-transfer captures.
  3. Inspect actual catalog print pages and test narrow menus, filters and report navigation against the same visitor tasks.
  4. Resolve the embedded-frame transfer gap and obtain a successful independent energy run before reporting client energy; keep unavailable measurements unfilled.
  5. Clarify operational website disclosure and targets, hosting evidence, catalog indexing rules and the standards collection’s review triggers.

The sample covers selected pages and visitor tasks, not every page on the site. Expand it where the checks above identify an untested template, interaction or audience need.

Detailed findings

This appendix explains the evidence in ordinary language. This audit used public-site evidence without a source checkout. Unavailable documents or internal records do not establish that the organization has none.

User experience design

Reading tasks remain in view

Passed this check · WSG 2.5: Design to assist and not to distract

Give users control over notifications and focus, prioritize task-relevant content, and avoid designs that distract or unnecessarily extend engagement.

The seven pages present useful headings, indexes, navigation and status information. No autoplay or disruptive visible modal is recorded, and catalog result counts support filtering. This result covers the sampled states.

Next step: Keep reading and filtering tasks clear of disruptive prompts when changing the templates.

Where we looked:

Check applicable choices before judging their fairness

Needs investigation · WSG 2.6: Avoid being manipulative or deceptive

Avoid deceptive patterns, clearly label ads, respect consent for tracking, and ensure search, sharing, and discoverability practices prioritize user needs over optimization or manipulation.

No cookie banner or accept/reject pair was observed or operated. Reading and catalog filtering work without an account, while sign-in and membership routes are identifiable. The evidence does not establish all applicable defaults or visual choice prominence.

Next step: Identify the applicable privacy controls and test their defaults and choices in the represented context. No observed banner does not establish absence of tracking.

Where we looked:

Resources explain their audience and purpose

Passed this check · WSG 2.7: Make deliverables understandable and reusable

Create discoverable, maintainable, and reusable documentation and code resources that support long-term understanding, reuse, and sustainability.

Headings and summaries distinguish standards, normative WCAG requirements and introductory WAI resources. Catalog examples, report version information and contact categories explain the next step. Specialist terminology is appropriate to the normative report, with introductory alternatives available.

Next step: Keep introductory routes and clear status/version labels alongside specialist documents.

Where we looked:

Different templates support recognizable tasks

Passed this check · WSG 2.8: Use a design system for interface consistency

Use design systems and established patterns to ensure consistent, efficient, and sustainable interfaces through reusable components and clear maintenance practices.

Corporate pages share navigation names and catalog controls. WAI has consistent resource navigation, while WCAG uses a document table of contents and version details. These task-specific differences do not establish inconsistent controls.

Next step: Keep names consistent within each template and explain transitions between introductory guidance and normative reports.

Where we looked:

Inspect the WAI link-transition effects

Needs investigation · WSG 2.10: Ensure animation is proportionate and easy to control

Use animation sparingly and efficiently, only when it supports understanding, while limiting performance impact and giving users control over motion.

No screen animation or moving media is observed in the sampled desktop and preference states. Two brief link animations appear during WAI print transitions, but their properties and visible purpose were not captured. Their impact remains unresolved.

Next step: Inspect those effects while changing print and reduced-motion preferences, then decide whether any visible movement needs suppression.

Where we looked:

No unsolicited permission request was observed

Passed this check · WSG 2.12: Avoid unwanted notifications

Send only user-requested notifications and provide clear, accessible controls for managing preferences, opt-in, and account and contact settings.

The seven pages make no recorded notification-permission request. Catalog result counts provide task feedback and report dialogs remain hidden. Browser permission was already denied, so the result covers these observed states.

Next step: Recheck permission and alert behavior when adding notifications or new status messages.

Where we looked:

Check what the catalog includes when printed

Needs investigation · WSG 2.13: Reduce the impact of downloadable and physical documents

Reduce paper use through digital-first workflows, optimize and reuse accessible downloadable documents, and provide clear, user-controlled document previews and formats.

The sampled resources are readable HTML. Print emulation retains content and removes much navigation, but catalog text expands substantially, from about 46,700 to 177,700 characters. Actual printed pages and the value of the expanded entries were not inspected; long text snapshots elsewhere are capped.

Next step: Preview the catalog’s printed pages, identify which report/history details expand, and compare them with the reader’s intended list before changing print defaults.

Where we looked:

The catalog route reaches WCAG 2.2

Passed this check · WSG 2.4: Design efficient and streamlined user journeys

Design clear, efficient journeys that help users complete tasks and find content with minimal effort.

The recorded desktop route follows Standards to the catalog, enters WCAG, activates Show results and opens the exact WCAG 2.2 URL with its full visible title. The separate task trace corroborates completion. This does not establish the shortest route or success for every visitor.

Next step: Retain the clear filtering and exact report link when changing catalog navigation.

Where we looked:

  • Browser observations for Homepage.
  • Recorded visitor task starting at Homepage.

Inspect image detail before reducing renditions

Needs investigation · WSG 2.9: Optimize media to reduce resource use

Include media only when it supports user needs. Manage, optimize, and load media efficiently. Ensure users have control over playback and data use.

Most task content is text. Homepage cards, member logos and the larger WAI graphic have plausible display sizes, including possible higher-density use. The sample does not include the visual rendition checks needed to establish a safe size reduction.

Next step: Compare representative raster graphics at intended screen densities and preserve necessary detail before selecting smaller versions.

Where we looked:

Typography includes fallback strategies

Passed this check · WSG 2.11: Use optimized web typography

Use font strategies that minimize downloads and complexity while supporting required languages and dynamic content.

Corporate and WAI content load regular and semibold Noto Sans with fallback behavior; WAI examples can use Noto Sans Mono. WCAG uses system sans-serif with no webfont observed. Unloaded language and icon declarations do not establish extra downloads.

Next step: Keep readable fallbacks and required language coverage when changing font files or subsets.

Where we looked:

Core reading content remains without JavaScript

Passed this check · WSG 2.17: Provide cross-platform compatibility support

Document compatibility, avoid unnecessary obsolescence, and test across devices, systems, and network conditions.

Fresh visits without JavaScript retain catalog list/filter markup, WCAG text, WAI summaries and navigation, and mission/contact reading content. The sampled reading tasks do not require an account or player. Capped excerpts do not prove word-for-word equivalence of long documents.

Next step: Retain the HTML reading baseline and test individual enhanced controls separately when changing them.

Where we looked:

Look for a statement about operating www.w3.org

Needs investigation · WSG 2.1: Identify, assess, disclose, review, and mitigate sustainability impacts

Assess and report the planet, people, and prosperity impacts of digital projects, and plan measurable reductions to the real-world effects of their activity.

The sustainability mission describes WSG, research, implementation measurement and outreach. This provides useful context for W3C’s wider work, but does not identify the operational impacts and mitigation of the audited website. The limited search cannot establish that no such statement exists.

Next step: Link a website-specific operational sustainability statement, if available, with its service boundary and mitigation actions.

Where we looked:

  • Disclosure discovery for the origin https://www.w3.org.
  • Captured public evidence for Sustainability.

Web development

Check code use during the relevant interactions

Needs investigation · WSG 3.2: Minify and remove unused code

Minify code and data, and remove unused characters to reduce file size and improve loading efficiency and maintainability.

WAI and the report load distinct enhancement scripts; corporate and catalog pages use shared and page modules. A short initial execution sample does not cover menus, filters, translations or report navigation sufficiently to identify removable code.

Next step: Record representative interactions and corroborate a specific unused module before removing it.

Where we looked:

Investigate loading the sustainability video on request

Needs investigation · WSG 3.3: Modularize bandwidth-heavy components

Split large components into smaller, on-demand modules to improve loading efficiency while balancing maintainability and caching performance.

The sustainability page loads an external video environment during its initial visit. Its recorded initial transfer is incomplete at about 1.35 MB, while the explanatory reading content is already available. A working alternative activation route was not tested.

Next step: Compare the current embed with a lightweight preview that loads the player on request. Verify keyboard activation, playback and captions, and measure matched complete visits before claiming a reduction.

Where we looked:

Complete the tasks at narrow widths

Needs investigation · WSG 3.10: Ensure layouts work for different devices and requirements

Use responsive, progressively enhanced, and carbon-aware design to ensure accessible, adaptable functionality across devices and interaction methods while managing resource use.

All seven pages retain their task headings at 360 CSS pixels and avoid measured horizontal overflow. Narrow menus and the WCAG table of contents differ from desktop, but their controls were not operated in those states.

Next step: Use the narrow menus, catalog controls and report navigation to complete the same tasks on an appropriate device.

Where we looked:

Give the WCAG report a main-content landmark

Problem found · WSG 3.6: Ensure code follows good semantic practices

Use standards-compliant HTML and web platform features, and avoid unnecessary complexity or non-standard code.

The WCAG report has a meaningful language declaration and primary heading, but no main element or main role was recorded. The other six pages have a main region. This is a specific failure of the selected semantic expectation, not a complete WCAG conformance judgment.

Next step: Identify the normative report content with a main landmark, keep its table-of-contents navigation distinct, and verify that landmark navigation reaches the report.

Where we looked:

Clarify canonical URLs for catalog filters

Needs investigation · WSG 3.8: Structure metadata for machine readability

Include essential document metadata and structured data to improve usability, accessibility, and machine readability.

Titles are descriptive, WAI/WCAG canonical URLs are usable, and captured WAI structured data parses. Corporate, catalog, mission and contact pages omit canonical metadata. Whether catalog filter/query URLs need a declared representative URL remains unresolved.

Next step: Document the catalog indexing policy and test representative filter URLs; add canonical metadata where that policy requires it.

Where we looked:

Check the applicable preference controls and effects

Needs investigation · WSG 3.9: Use media queries that support sustainability goals

Support user preferences via media queries for color, motion, contrast, data use, and related settings to improve accessibility and efficiency.

Task content remains available during preference changes and fresh dark/reduced-motion visits. Light page colors alone do not establish a defect, and WAI offers Change Text Size or Colors guidance. Recorded WAI link effects need inspection before their reduced-motion behavior can be judged.

Next step: Inspect the link effects under reduced motion and exercise documented preference controls before prescribing a theme change.

Where we looked:

Trace repeated requests to their purpose

Needs investigation · WSG 3.11: Use sustainable JavaScript and APIs

Write efficient JavaScript and use APIs that minimize processing, data use, and energy consumption.

Member-logo, catalog and external-video requests have plausible purposes. The limited capture does not establish sustained polling, freshness needs or unnecessary repeats, so it cannot support a removal or backend-cost claim.

Next step: Trace recurring requests by initiator and event, then compare unchanged repeats with actual visitor needs.

Where we looked:

Verify focus indicators on corporate controls

Needs investigation · WSG 3.6: Ensure code follows good semantic practices

Use standards-compliant HTML and web platform features, and avoid unnecessary complexity or non-standard code.

Initial keyboard paths reach meaningful skip, language, navigation and report links. WAI and WCAG show supported outline behavior. Corporate skip/language controls have transparent outlines, but other focus styling was not fully captured, leaving their visible indicator unresolved.

Next step: Inspect the complete focused appearance of the corporate skip and language controls, then verify activation and navigation.

Where we looked:

A discoverable carbon.txt was not found

Problem found · WSG 3.13: Include expected and beneficial files

Include standard website metadata and configuration files to support discoverability, transparency, and operational best practices.

The tested root and well-known carbon.txt addresses return 404, and no usable delegation or parseable file was established. This failure is limited to discovery and does not measure the site’s emissions or the value of W3C’s sustainability work.

Next step: If adopting carbon.txt, publish a valid file with supported service/provider relationships and verify discovery.

Where we looked:

  • Disclosure discovery for the origin https://www.w3.org.

Hosting, infrastructure and systems

Reusable assets provide caching or validation

Passed this check · WSG 4.2: Optimize caching and support offline access

Use caching and offline capabilities to reduce network load, improve resilience, and balance performance with sustainability.

Corporate styles and scripts expose validators, catalog fingerprinted assets have long public lifetimes, and WAI/report assets have bounded lifetimes or validators. These policies support reuse; actual warm-cache behavior was not measured.

Next step: Retain appropriate asset policies and use a matched repeat visit to check actual reuse if needed.

Where we looked:

Material text responses are compressed

Passed this check · WSG 4.3: Reduce data transfer with compression

Compress server responses and media files to reduce bandwidth, storage use, and delivery overhead while balancing processing costs.

Successful material documents, scripts and styles use gzip or Brotli across the seven sampled response sets. Already-compressed graphics, fonts and media are outside this check.

Next step: Keep compression enabled when deploying new text assets or changing delivery services.

Where we looked:

Establish operational hosting evidence for this origin

Needs investigation · WSG 4.1: Use sustainable hosting

Select and manage infrastructure using sustainability metrics, prioritizing low-carbon energy use and low-impact hosting and domain choices in selection, and extending hardware lifespan and minimising emissions in management.

The captured evidence does not connect www.w3.org to a named hosting service with independently corroborated operational sustainability evidence. Sustainability standards and advocacy do not supply that relationship.

Next step: Identify the hosting service for this origin and link independent evidence covering the same service and operational scope.

Where we looked:

  • Disclosure discovery for the origin https://www.w3.org.
  • Captured public evidence for Sustainability.

Business strategy and product management

Check whether media or print guidance would be useful

Needs investigation · WSG 5.4: Communicate the environmental impact of user choices

Empower users, allowing them to make decisions when their choices can influence the environmental impact they have.

Reading HTML, printing reports and choosing the mission video may have different resource implications. The mission discusses wider web impacts, but no tested format or print comparison supports advice about those specific visitor choices.

Next step: Compare one consequential media or print choice for task usefulness, transfer and printed page count before adding contextual guidance.

Where we looked:

The sampled report-reading route needs no account

Passed this check · WSG 5.13: Evaluate if a digital product or service is necessary

Assess alignment with sustainability goals, validate product need, and reduce barriers to access, usability, and fairness.

The anonymous desktop pointer/text-input route reaches the exact WCAG 2.2 report and full visible title without an account or personal-data request. The task trace confirms the declared completion; other input methods and access constraints were not tested.

Next step: Extend the route to keyboard, assistive-technology and relevant constrained-access testing before making wider usability claims.

Assessed scope: Anonymous English desktop readers with JavaScript enabled, a pointer and ordinary text input at 1365x900: start at https://www.w3.org/, follow standards to the public technical-report catalogue, filter for WCAG and open the full WCAG 2.2 report. Completion requires its exact URL and visible full report title, with no account or personal-data submission. Keyboard-only, mobile, impaired-network and geographic access are not represented.

Where we looked:

  • Browser observations for Homepage.
  • Recorded visitor task starting at Homepage.

Keep useful standards history and explain review triggers

Needs investigation · WSG 5.18: Promote responsible data practices

Respect user data rights and manage data lifecycle through minimized collection, user control, portability, deletion, and content archiving.

WCAG 2.2 has dated drafts and Recommendations from 2020–2024, version/history/errata links, named editors and a feedback route. These support publication and continued reference use. The captured status excerpt is capped and does not establish a review schedule or applicable update decision.

Next step: Document the collection’s review triggers or cadence and one resulting update decision, while retaining historical standards that readers still need.

Assessed scope: Public English WCAG 2.2 technical-report collection, from the first 2020 working draft through the December 2024 Recommendation and its currently published history as captured on 2026-11-06: review stated maintenance/review arrangements, an applied publication/update decision and discoverable historical reports. The broader WAI collection and organization-wide CMS practices are excluded; continuing reference value of historical standards is retained.

Where we looked:

  • Captured public evidence for Wcag22.
  • Captured public evidence for Wcag22.
  • Browser observations for Wcag22.

Separate the sustainability mission from website targets

Needs investigation · WSG 5.6: Define clear organizational sustainability goals and metrics

Define measurable sustainability goals and metrics, and communicate progress over time.

The mission describes a sustainable-web direction, guidance and implementation measurement. It does not supply an operational target, measurement boundary and comparable dated baseline/progress for www.w3.org. The website’s own goals remain unresolved.

Next step: Publish any established website-operation target with its metric, service boundary and comparable baseline/progress, or clarify what is still being established.

Assessed scope: Operation and delivery of the public www.w3.org web service as described by its sustainability mission page at the 2026-11-06 capture. Assess whether published direction, metrics, service boundary and dated comparable baseline/progress refer to this service. W3C advocacy for the wider web and development of WSG are context, not evidence of this service achieving operational targets.

Where we looked:

Methodology and reproducibility

The browser measurements were captured from 2026-11-06T08:49:16.153741+00:00 to 2026-11-06T08:50:45.195994+00:00. Initial-load tests used a 1280 × 800 desktop viewport and a 3-second observation window. Cookie choices and scrolling were recorded afterward. Supplementary tests covered narrow layouts, color and motion preferences, print, JavaScript availability and bounded keyboard navigation.

Audit judgments: Codex native subagent, gpt-6.1-sol, high reasoning. Report wording: Codex native subagent, gpt-6.1-sol, high reasoning.

The scoring method is agent-breadth-v3. A guideline group counts once even if it has several checks. Observed problems take precedence over unresolved checks in that group. 0 groups were excluded as not applicable; 44 were untested. Unknowns remain in the passing-percentage denominator; untested and inapplicable groups do not. Area percentages use the same rule as the overall score.

First load

Data downloaded before clicking or scrolling, using the first recorded initial visit for each URL, including its completeness limit. Decimal kB = 1,000 bytes; MB = 1,000,000 bytes.

Cookie choices and waiting

No cookie banner was observed in this sample. The intermediate checkpoint waits without clicking. Later columns show cumulative totals, including the initial load of that visit. They are not additional amounts to add together or guaranteed savings.

Scrolling

Cumulative downloads after scrolling to the bottom, following the cookie-choice or waiting checkpoint of the same visit. Compare accept and reject values within their own visit; do not subtract the first-load headline from a different visit.

Partial measurements

A partial result means some requests failed or did not finish in the observation window, so their transferred size is uncertain. The site is measured as it behaved; a failed analytics request is context, not automatically a priority fix. Failed document loads and HTTP error responses are shown as unavailable, since their bytes do not represent the requested page. Carbon estimates and ratings are withheld for failed or incomplete initial captures. Unmarked transfer figures are complete within the test conditions, not a measure of every possible download.

Estimated footprint and Digital Carbon Rating

Both use the same initial visit as the first-load column. Footprints are estimates in grams of carbon dioxide equivalent (gCO₂e) per first visit. They display two decimal places, with a minimum of 0.01 gCO₂e for positive estimates. Digital Carbon Ratings use unrounded estimates from the fixed comparison model. Recorded model: Sustainable Web Design Model version 4 through @tgwf/co2@0.19.0, assuming 100% first visits. The comparison gives no green-hosting credit. These are model assumptions, not verified electricity-supply facts. Ratings remain provisional because the capture protocol has not been independently validated; they do not establish whole-site sustainability.

Browser and network energy

Energy is shown in milliwatt-hours (mWh = 0.001 Wh). Browser energy includes modeled CPU, memory, disk and display use. Not sampled means no energy experiment was supplied for that page; unavailable means a supplied experiment did not yield a usable result. Neither means zero energy.

Energy method: GreenFrame 2.0.1 uses separately recorded browser scenarios, with three fresh-context visits per page, page load followed by a three-second wait, and no cookie interaction or scrolling. The median client-device estimate and median network estimate are reported separately; their medians must not be added to derive a total. This is a resource-use model, not metered whole-device electricity. Browser startup and the collector warm-up are excluded; browser close is included.

The pinned container uses Chromium 110 and a fixed Chrome 89 user-agent, independently of the transfer collector. The model assumes a 14 W display; that assumption contributes substantially to these short visits. CPU, memory and disk estimates use the collection host's properties. Background activity on this shared workstation was not independently isolated. These figures support repeat experiments under the same conditions, not device-independent rankings. GreenFrame network energy and SWDM carbon estimates overlap in scope and are not added together.

Illustrations were captured separately from the transfer measurements. Their capture dates, viewports, URLs and file hashes are retained in the screenshot manifest. No source checkout was included in this audit.

Annual footprint

Traffic: CrUX dataset month 2026-09, exact origin https://www.w3.org, popularity bucket 100,000. The CrUX popularity metric is a coarse navigation-based rank, not a pageview count. The rank-to-pageviews mapping applies medians calibrated on US government sites using 2025 analytics and December 2025 ranks. This population and period differ from this site. No calibrated site-level uncertainty interval is available; these are scenarios, not measured analytics or a forecast.

SWDM v4: Annual pageviews × the arithmetic mean of unrounded emissions per sampled URL ÷ 1,000 = kgCO₂e/year. Use the first recorded initial visit per URL, equal page weights and 100% first visits. The actual mix of pages and returning visitors is unknown. SWDM v4 covers modeled operational and embodied browsing emissions across devices, networks and data centers; it is not a complete inventory of this site's backend, builds or organization.

Partial transfer inputs can support this explicitly labeled scenario, but do not establish a complete footprint or qualify for a Digital Carbon Rating. Ratings remain withheld where initial captures are incomplete.

No valid client-energy projection is available; it is not treated as zero.

Potential improvement scale

The illustrative reduction equals each annual estimate × 0.10 at unchanged traffic. It assumes that average per-view impact falls by 10% across the modeled population; it does not establish that any recommended fix will achieve this. A 10% byte reduction is not automatically a 10% reduction in measured client energy. Validate a change with matched before/after scenarios, then apply its measured difference only to the affected share of annual pageviews. Baseline device/display activity is not automatically removable by site changes.

All annual figures scale linearly with the traffic assumption: half as many pageviews halves them; twice as many doubles them. Replace the rank proxy with matching-origin analytics, page weights, repeat-visit proportions and audience device/electricity data to improve the estimate. Sample minimum/maximum intensities in the artifact are sensitivity cases, not confidence bounds.

Technical files for reproducing this report

The report above can be read without these files. They retain exact evidence, original judgments and calculation inputs for independent reproduction.

Original review SHA-256: 155fe68c6fc27938766f79d97bbf62656a1fa905d15d9edda3dbca977da67966. Recalculate with audit/assess.py using the preserved reviews, rubric, weights and evidence. New collection or model review requires a new session; it can produce different results.