# climate-connect.org.uk EcoMark analysis | v2

Dated EcoMark analysis for climate-connect.org.uk: C 70/100 using algorithm v2.

Canonical: https://ecomark.app/assessment/54c9ebb0-4afb-4dc0-84c0-d09aa534f9a9

EcoMark analysis · Algo v2

# climate-connect.org.uk

Published 28 Aug 2026

Rescan website
[Site history](/site/climate-connect.org.uk) C 70 #3 of 6 at publication

This grade belongs to climate-connect.org.uk. It is based on a bounded sample of up to 3 connected public pages plus public evidence. It is not a grade for any one page.

Automated EcoMark v2 approximation using technical crawl evidence, DNS, public policy/identity signals and a Green Web hosting check. Analysis quality: good.
[Algorithm v2](/methodology/v2) · [Raw evidence](/evidence/54c9ebb0-4afb-4dc0-84c0-d09aa534f9a9)

Improve

## Start with these changes.
1
efficiency

### Reduce resource and third-party requests by consolidating assets and removing unnecessary integrations.

Lighter pages consume less bandwidth and device work and remain usable on slower connections.
2
responsibility

### Publish clearly linked privacy, terms, accessibility and contact information, plus a public registration identifier where applicable.

Transparent, secure defaults make digital impact understandable and give visitors meaningful choices.
3
accessibility

### Keep meaningful content in the initial HTML so the page remains useful without heavy client rendering.

Accessible, resilient markup works for more people, assistive technology and older or constrained devices.

Breakdown

## Evidence by category.

Efficiency
30 #6 of 6
1 pages · ~1475 KB measured/page · 1387 resource references/page · 0% sampled assets cacheable.

**Evidence and scoring**

Evidence: 1 pages · ~1475 KB measured/page · 1387 resource references/page · 0% sampled assets cacheable.

- Payload Measured HTML and sampled asset payload is proportionate and optimised. 10/20
- JavaScript Referenced JavaScript weight is kept proportionate. 20/20
- Requests Pages avoid excessive resource references and third-party connections. 0/20
- Media Images and video avoid obvious loading and autoplay waste. 0/20
- Caching and compression Sampled static assets expose effective cache policy. 0/20

Privacy
100 #1 of 6
0 known trackers · 0 tracking-style response cookies · 0% third-party resource references.

**Evidence and scoring**

Evidence: 0 known trackers · 0 tracking-style response cookies · 0% third-party resource references.

- Behavioural tracking Known advertising pixels and cross-site trackers are absent or minimised. 20/20
- Analytics minimisation Analytics technology is absent or privacy-preserving and proportionate. 20/20
- Cookies and consent Non-essential response cookies are avoided before interaction. 20/20
- Third-party disclosure Resource loading does not unnecessarily disclose visits to third parties. 20/20
- Invasive techniques Known session replay and similarly invasive tools are absent. 20/20

Sovereignty
95 #1 of 6
1 US-headquartered visitor-facing provider ecosystems · 100% first-party assets · open technology 95/100 · Next.js. DNS: NS ns39.domaincontrol.com, ns40.domaincontrol.com · MX 10 inbound-smtp.eu-west-1.amazonaws.com · CNAME hftfclimateconnect.netlify.app.

**Evidence and scoring**

Evidence: 1 US-headquartered visitor-facing provider ecosystems · 100% first-party assets · open technology 95/100 · Next.js. DNS: NS ns39.domaincontrol.com, ns40.domaincontrol.com · MX 10 inbound-smtp.eu-west-1.amazonaws.com · CNAME hftfclimateconnect.netlify.app.

- Provider jurisdiction Observable visitor-facing dependencies minimise reliance on US-headquartered platform ecosystems. 15/20
- Third-party geography Known non-EU third-party data exposure is minimised. 20/20
- Portable delivery Pages minimise proprietary embeds and platform-specific content dependencies. 20/20
- Supplier concentration Third-party resource loading is not dominated by one provider ecosystem. 20/20
- Open technology Open standards, first-party delivery, open-source technology and public source code are preferred where practical. 20/20

Accessibility
70 #4 of 6
1 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 9% raw/rendered text ratio.

**Evidence and scoring**

Evidence: 1 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 9% raw/rendered text ratio.

- Semantics HTML exposes basic language, heading and landmark structure. 15/20
- Keyboard access Markup avoids obvious keyboard-hostile interaction patterns. 20/20
- Forms and controls Form controls expose labels or accessible names. 20/20
- Visual accessibility Viewport and media markup avoid obvious visual accessibility barriers. 15/20
- Resilience Meaningful text remains present without relying entirely on client rendering. 0/20

Responsibility
55 #2 of 6
Privacy ✗ · Cookies n/a · Terms ✗ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. no verified green-hosting evidence found. carbon.txt ✗ · 4/5 security headers.

**Evidence and scoring**

Evidence: Privacy ✗ · Cookies n/a · Terms ✗ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. no verified green-hosting evidence found. carbon.txt ✗ · 4/5 security headers.

- Public accountability Privacy, terms, accessibility, contact and applicable registration information are discoverable. 0/20
- Security basics The main response exposes sensible browser security headers. 15/20
- Consent design Tracking and consent markup avoids obvious one-sided choice patterns. 20/20
- Supplier disclosure Detected material visitor-facing providers are reflected in discoverable privacy information. 20/20
- Sustainability evidence Green hosting, carbon.txt and public sustainability information provide discoverable evidence of digital sustainability practice. 0/20
