Skip to content

www.tate.org.uk: sustainability audit

At a glance

  • 37.0/100 — scoped audit score
    10 passing, 3 with problems, 14 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.

Tate’s visitor information supports the sampled parking task, and its public website statement describes concrete sustainability work. The first investigation is the shared TateDraw image fetched while its promotion is hidden or offscreen. Two specific fixes concern cookie-policy content without JavaScript and uncompressed consent-provider text. Every page’s transfer count is incomplete, so the displayed sizes are incomplete, the annual footprint scenario uses partial transfers, and page footprints and Digital Carbon Ratings are withheld. Separate browser-energy modeling covers only the homepage and Julio Le Parc page; annual figures are assumption-based scenarios, distinct from Tate’s historical estimates.

Results by WSG area

Selected checks by WSG area
AreaPassingGuideline groups checkedNeeds evidence
User experience design58% (7/12)12 of 174
Web development12% (1/8)8 of 166
Hosting, infrastructure and systems33% (1/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
Homepage5.778 MB · partial5.778 MB · partial5.779 MB · partialWithheldWithheld19.42 mWh62.99 mWh
Tate Modern6.017 MB · partial6.017 MB · partial6.235 MB · partialWithheldWithheldNot sampledNot sampled
What's On6.779 MB · partial6.779 MB · partial6.781 MB · partialWithheldWithheldNot sampledNot sampled
Julio Le Parc4.464 MB · partial4.464 MB · partial4.466 MB · partialWithheldWithheld19.98 mWh48.30 mWh
Stories5.155 MB · partial5.155 MB · partial5.185 MB · partialWithheldWithheldNot sampledNot sampled
Creating a greener website4.011 MB · partial4.011 MB · partial4.013 MB · partialWithheldWithheldNot sampledNot sampled
Cookie Policy4.071 MB · partial4.071 MB · partial4.075 MB · partialWithheldWithheldNot 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 transfers19,152.20 kgCO₂e/year1,915.22 kgCO₂e/year less
Client electricity · GreenFrame scenarios491.30 kWh/year49.13 kWh/year less
Client operational emissions · assumed electricity mix242.70 kgCO₂e/year24.27 kgCO₂e/year less

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

Priorities

1. Check when the shared TateDraw image is needed

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

What we found. A roughly 859 kB TateDraw JPG is fetched across the sampled templates, including homepage and greener-website states where its promotion is hidden or offscreen. The evidence establishes a useful investigation target; it does not yet establish a safe change.

Why it matters. A shared request can affect visitors arriving on many different pages. Checking this promotion’s activation offers a focused way to investigate avoidable initial transfer while preserving useful art and navigation.

Next step. Trace the request to the shared promotion, open it with pointer and keyboard controls, and test loading a suitable rendition only when needed. Check image detail at intended screen densities and compare matched complete visits before claiming savings.

How we checked this: Check when the shared TateDraw image is needed

Medium priority · Problem found · WSG 2.17: Provide cross-platform compatibility support

What we found. The cookie policy loses its vendor/cookie list and Manage Preferences material when JavaScript is unavailable. Other sampled reading content remains accessible, but no equivalent policy alternative is provided for this missing information.

Why it matters. Visitors with unavailable or failed scripts cannot inspect the same cookie details or find the same preference material.

Next step. Render the inventory in HTML or link an equivalent static policy and usable preference-management alternative. Confirm a fresh visit without JavaScript can read the policy information and reach the alternative.

How we checked this: Keep the cookie inventory readable without JavaScript

Low priority · Problem found · WSG 4.3: Reduce data transfer with compression

What we found. On What's on, consenTag.js and popup_silent.html return successful text responses without a content-encoding, at roughly 6.6 kB and 12.0 kB. Core Tate scripts and styles are already compressed.

Why it matters. These specific text responses are candidates for smaller transfers through beneficial compression. The achievable change and its effect on energy have not been measured.

Next step. Ask the provider to enable compression through content negotiation. Verify the delivered encoding and preference-manager behavior, then measure a matched visit to establish the transfer change.

How we checked this: Compress the consent-provider script and document

4. Explain how the historical website estimates compare

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

What we found. Tate reports website estimates of 45 metric tons CO₂e in 2019 and 27 metric tons in 2023. Its website-specific statement and Digital Green Team provide useful context, but the captured evidence does not document comparable calculation methods and boundaries.

Why it matters. Readers need to know whether changes in traffic, scope or calculation methods explain part of the difference before treating it as like-for-like progress. These historical estimates also use a different basis from this audit’s current scenarios.

Next step. Publish a concise method note for both years covering service boundary, traffic, model inputs and any recalculations. Add one dated review showing how the team used a result to choose its next action.

How we checked this: Explain how the historical website estimates compare

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
Visitor information stays accessible Passed this check
Check cookie choices and defaults Needs investigation
Visitor information explains the next step Passed this check
Navigation names remain consistent Passed this check
Check the shared interface transitions Needs investigation
No unsolicited notification request was observed Passed this check
Inspect the map and accessible document alternatives Needs investigation
Check code use across visitor interactions Needs investigation
Trace an optional component before changing its loading Needs investigation
Check the narrow cookie-policy layout Needs investigation
Check whether format guidance would help visitors Needs investigation
Parking instructions are reachable from the homepage Passed this check
Investigate the shared TateDraw image Needs investigation
Body fonts have a readable fallback Passed this check
Pages identify their language and main content Passed this check
Page titles and canonical URLs are useful Passed this check
Check reduced-motion behavior in the shared interface Needs investigation
Keep the cookie inventory readable without JavaScript Problem found
Check the purpose of repeated third-party calls Needs investigation
Reusable public assets declare cache policies Passed this check
Compress the consent-provider text responses Problem found
Recheck the skip link after focus settles Needs investigation
Tate publishes website-specific sustainability information Passed this check
A discoverable carbon.txt was not found Problem found
Establish the website hosting evidence Needs investigation
Show how a website review informs the next action Needs investigation
The sampled parking-information task needs no account Passed this check
Explain the basis of the reported website reduction Needs investigation

Next steps for auditing

  1. Trace and test the shared TateDraw promotion before changing its loading; preserve image quality and accessible activation.
  2. Provide an HTML cookie inventory and usable preference alternative, then test the fresh no-JavaScript policy-reading task and the actual privacy choices.
  3. Recheck the skip link after focus and screen layout settle, exercise narrow controls, and inspect the recorded reduced-motion transitions.
  4. Complete the missing transfer coverage and repeat any changed page under matching conditions. Keep annual scenarios separate from historical claims and browser-energy modeling.
  5. Publish comparable methods for the 2019/2023 website estimates, one dated review-to-action example and corroborated hosting evidence.

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

Visitor information stays accessible

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.

Gallery, exhibition, editorial and policy content remains available across the seven pages. Ticket, membership and newsletter prompts relate to Tate, and the parking-information route completes without a modal interruption. No autoplay is recorded in these states.

Next step: Retain clear separation between visitor information and optional promotions when changing these templates.

Where we looked:

Check cookie choices and defaults

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 was observed or operated. The cookie policy offers Manage Preferences and third-party tracking requests occur, but the defaults and accept/reject routes were not tested. This leaves the fairness of the choices unresolved.

Next step: Open Manage Preferences in a fresh visit, inspect the defaults and compare the visibility and operation of accept and reject choices.

Where we looked:

Visitor information explains the next step

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.

Opening times, admission, exhibition dates and ticket routes are labeled. Stories distinguishes reading, listening and watching, while the parking section gives a location and advance-booking contact details. This supports the sampled English information tasks.

Next step: Keep these concrete labels and confirm comprehension with the intended audience when changing visitor instructions.

Where we looked:

Navigation names remain consistent

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.

The seven pages repeat What's on, Visit, Art, Learn, Shop and membership navigation, with recognizable Search and footer patterns. Section headings distinguish each page's purpose.

Next step: Keep shared navigation names consistent as content and templates change.

Where we looked:

Check the shared interface transitions

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 initial video or animation was recorded. Several short interface transitions appear in narrow and reduced-motion states, but the capture does not show which properties move or whether the effects are visible. Harmful motion has not been established.

Next step: Inspect the transitions while opening navigation with reduced motion enabled, and suppress any nonessential movement that the preference should affect.

Where we looked:

No unsolicited notification 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 and show no unsolicited alert dialog. Newsletter signup is optional. Browser notification permission was already denied, which limits this result to the captured states.

Next step: Recheck alert and permission behavior when introducing messaging features.

Where we looked:

Inspect the map and accessible document alternatives

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 gallery labels its PDF map and size, and offers print and digital communication cards; the exhibition links a large-print guide. Print emulation retains page text and removes navigation. The files and actual pagination were not inspected.

Next step: Inspect the map, communication cards and large-print guide for readability, useful content, file size and printed output before changing their formats.

Where we looked:

Parking instructions are reachable from the homepage

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 captured route opens Tate Modern from the homepage and then its Accessibility section. The page gives twelve disabled parking spaces via Park Street and advance phone/email booking instructions. The task ends at finding that information.

Next step: Retain this discoverable route and recheck it after gallery-page changes.

Where we looked:

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

Investigate the shared TateDraw image

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.

A roughly 859 kB TateDraw JPG is delivered across the sampled templates. On the homepage and Creating a greener website page, the associated image has no rendered size and is not visible in the captured desktop state. Other art images use responsive WebP and plausible card dimensions, but rendition quality has not been inspected.

Next step: Find what initiates the TateDraw request and when visitors expose the promotion. Test conditional loading and a proportionate rendition, checking artwork detail, keyboard activation and the same visitor tasks before making a change.

Where we looked:

Body fonts have a readable fallback

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.

Tate body faces use a swap loading policy with Arial/Helvetica fallbacks. Light and bold variants appear where used, while several declared faces remain unloaded. The captured controls have names; this does not establish that any language or glyph support is removable.

Next step: Keep the body-text fallback and verify readability and required characters before changing font delivery.

Where we looked:

Keep the cookie inventory readable without JavaScript

Problem found · WSG 2.17: Provide cross-platform compatibility support

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

Gallery, exhibition, Stories and sustainability text remains available without JavaScript. On the cookie policy, however, the vendor/cookie inventory and Manage Preferences material disappear, leaving only a short policy text without an equivalent alternative. JavaScript-on policy excerpts are capped, so they do not establish every inventory entry.

Next step: Render the inventory in HTML or link an equivalent static policy, and provide a usable preference-management alternative. Confirm a fresh visit without JavaScript can read the same policy information.

Where we looked:

Tate publishes website-specific sustainability information

Passed this check · 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.

Creating a greener website identifies tate.org.uk, describes device, server and production impacts, and lists changes to the CMS, image delivery, editorial guidance, code and data. This supports the public-disclosure check; it does not independently verify delivery or savings.

Next step: Keep the statement discoverable and distinguish completed actions, ongoing work and estimates.

Where we looked:

Web development

Check code use across visitor 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.

The initial-load sample includes shared interface, vendor, page, experimentation and tracking scripts. It does not cover enough menus, filters, gallery disclosures or ticket routes to establish which code can be removed.

Next step: Record code use while completing representative interactions, then identify a specific removable module with source or deployment evidence.

Where we looked:

Trace an optional component before changing its loading

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 site already separates shared scripts from page-specific modules. The evidence does not show which optional components are needed later or whether they can be activated reliably after being deferred.

Next step: Trace one substantial optional component from its first request to visitor activation, then test a deferred version against the same task.

Where we looked:

Check the narrow cookie-policy layout

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.

Main headings and task text remain at 360 CSS pixels, and most pages avoid measured horizontal overflow. The cookie policy does overflow, but its tables and controls were not exercised enough to establish the cause or visitor impact.

Next step: Inspect the cookie tables at narrow widths and complete policy reading, navigation and gallery-disclosure tasks using their controls.

Where we looked:

Pages identify their language and main content

Passed this check · 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.

All seven pages declare English, include a main region and provide meaningful visible page headings. Search has an accessible name, the footer email field has a label, and sampled filters and disclosure controls have visible text. This is a bounded semantics check, not a complete accessibility audit.

Next step: Retain these landmarks and naming relationships when updating shared controls.

Where we looked:

Page titles and canonical URLs are useful

Passed this check · WSG 3.8: Structure metadata for machine readability

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

Each sampled document has a descriptive title and a usable absolute canonical URL matching the page. Optional descriptions and structured data were not required to complete these information tasks.

Next step: Keep titles and canonical URLs aligned with the live page when publishing or moving content.

Where we looked:

Check reduced-motion behavior in the shared interface

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 text remains available when device preferences change and in fresh dark/reduced-motion visits. The greener-website page deliberately stays dark and other pages stay light. Recorded interface transitions lack the detail needed to judge whether reduced motion should change them.

Next step: Inspect the transition effects with reduced motion enabled before deciding which need to be suppressed.

Where we looked:

Check the purpose of repeated third-party calls

Needs investigation · WSG 3.11: Use sustainable JavaScript and APIs

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

The sample includes experiment, location/device, analytics, advertising and listing requests. Some addresses repeat for different events. Their purpose, necessity and response to privacy choices are unresolved, so repetition alone does not identify safe removals.

Next step: Trace request initiators and events while operating cookie choices and the relevant visitor tasks; remove or defer only calls shown to be unnecessary.

Where we looked:

Recheck the skip link after focus settles

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.

The initial keyboard trace reaches meaningful navigation links with blue outlines. The first skip-link position was captured immediately after resetting print media, before a settled frame; it remains offscreen in that instant. That snapshot cannot establish a persistent invisible-focus defect.

Next step: Let the screen layout settle, focus Skip navigation, inspect its final position and indicator, then activate it and confirm the main content is reached. Repeat without preceding print emulation.

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 is a narrow discovery failure; the separate website sustainability statement exists.

Next step: If adopting carbon.txt, publish a valid file linking the existing disclosure and supported provider relationships, then test discovery.

Where we looked:

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

Hosting, infrastructure and systems

Reusable public assets declare cache policies

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.

Versioned Tate styles and scripts expose long public cache lifetimes and validators. Images and external helpers also provide lifetimes or validators. These headers support reuse in principle; a repeat visit was not measured.

Next step: Retain appropriate cache policies for versioned public assets and measure a repeat visit if checking actual reuse.

Where we looked:

Compress the consent-provider text responses

Problem found · 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.

Core Tate scripts and styles use gzip. On What's on, successful responses for consenTag.js and popup_silent.html carry roughly 6.6 kB and 12.0 kB without a content-encoding. These specific third-party text responses fail the selected compression check.

Next step: Ask the provider to enable beneficial compression, then verify compressed delivery and successful preference management. Measure the resulting transfer change before claiming savings.

Where we looked:

Establish the website hosting evidence

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 website statement discusses server electricity and cooling, but the captured evidence does not connect this origin to a named hosting service with independently corroborated operational evidence.

Next step: Identify the service hosting this origin and link current supporting evidence for the same operational boundary.

Where we looked:

  • Disclosure discovery for the origin https://www.tate.org.uk.
  • Captured public evidence for Green website.
  • Captured public evidence for Digital.

Business strategy and product management

Check whether format guidance would help visitors

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.

Stories identifies text, audio and video, and gallery resources distinguish digital and print options. The website statement also describes its dark design. No measured comparison establishes the impact of a visitor choosing one format over another; its OLED percentage is conditional on the device and maximum brightness.

Next step: Compare the usefulness and delivery of one meaningful media or document choice before offering impact guidance.

Where we looked:

Show how a website review informs the next action

Needs investigation · WSG 5.1: Have an ethical and sustainable product strategy

Implement organizational practices around ethics, sustainability, and responsible data use. Publish and maintain policies that demonstrate their implementation.

Tate names a Digital Green Team, reports regular meetings since 2019, and lists website results and actions. The captured statement does not link one dated review of a monitored result to a resulting decision. This leaves that specific governance check unresolved.

Next step: Publish one short, dated example naming the responsible team, the result it reviewed and the action or reasoned continuation it chose.

Assessed scope: Tate Digital Green Team governance for reducing the tate.org.uk website footprint over the reported 2019–2023 baseline/progress period, plus continuing actions described on the public Digital and Creating a greener website pages captured 2026-11-06. Assess accountable review, monitored result and consequent action or reasoned continuation for that web-service commitment. No organization-wide governance or unpublished meeting evidence is in scope.

Where we looked:

The sampled parking-information task 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.

An anonymous desktop visitor using pointer controls reaches the parking location and booking contact instructions without signing in, making contact or purchasing. The audit does not test booking, physical gallery access or unrepresented access needs.

Next step: Extend task testing to keyboard and assistive-technology users before drawing wider accessibility conclusions.

Assessed scope: Anonymous English readers using desktop Chromium with pointer input and JavaScript, 1440 by 1000 CSS pixels: start at https://www.tate.org.uk/, follow the Tate Modern gallery card, open Accessibility, and read the accessible-parking location plus advance-booking phone/email instructions. Completion is obtaining public information; no parking booking, ticket purchase, account, contact or form submission. Keyboard-only, assistive-technology, constrained-device and physical-gallery accessibility are outside this assessment scope.

Where we looked:

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

Explain the basis of the reported website reduction

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

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

Tate estimates website emissions of 45 metric tons CO₂e in 2019 and 27 metric tons in 2023, and attributes part of the change to its CMS. The captured statement does not document comparable traffic, service boundaries or calculation methods. These are historical Tate estimates, separate from this audit’s current model scenarios.

Next step: Add the calculation boundary, traffic and model assumptions for both years, explain method changes or recalculations, and show how a dated review informed the next action.

Assessed scope: The tate.org.uk web service and Tate Digital Green Team commitments described in Creating a greener website: assess the stated 2019 estimated 45 tonnes CO2e baseline, reported 2023 estimated 27 tonnes CO2e result, metric/boundary comparability and ongoing reduction direction as published on 2026-11-06. Exclude Tate buildings, collection transport, commercial shop origin and total organizational emissions; published estimates are self-report, not verified measurement.

Where we looked:

Methodology and reproducibility

The browser measurements were captured from 2026-11-06T08:48:24.435889+00:00 to 2026-11-06T08:50:07.454109+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.tate.org.uk, 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.

Client-energy projection: The 2 energy-sampled URLs out of 7 audited URLs receive equal weights. Take each URL's median of three matching GreenFrame runs, average those unrounded medians, and multiply by estimated pageviews ÷ 1,000 to convert Wh to annual kWh. This assumes every pageview repeats that initial-load desktop scenario; it does not cover later reading, scrolling, other devices, network energy, remote servers or embodied emissions.

Convert client kWh to operational kgCO₂e using 494 gCO₂e/kWh ÷ 1,000. This is an explicit comparison assumption, using the SWDM v4 default unless overridden; the audience's electricity mix is unknown. GreenFrame estimates energy from observed resource use, not an electricity meter. Its fixed display/CPU coefficients and short laboratory duration can dominate these values. Do not add either client projection to SWDM or substitute it for SWDM's entire device segment.

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: a0c0a0c284495c365411b45a9281ed9591f79de9e1a0caf2ad24935129e39bb4. 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.