ecomark.

EcoMark analysis · Algo v3

Eco

Published 28 Aug 2026

Site history
B80#1 of 2 at publication

Automated EcoMark v3 approximation using technical crawl evidence, DNS, public policy/identity signals and a Green Web hosting check. Browser Run was blocked or incomplete, so the normal public HTML response was used instead. Analysis quality: good.

Algorithm v3 · Raw evidence

Improve

Start with these changes.

1

sovereignty

Avoid concentrating most third-party delivery in one provider ecosystem.

A more portable and less concentrated stack gives organisations more control over technology and jurisdiction.

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

privacy

Move commonly used assets and services first-party where practical.

Minimising tracking and third-party disclosure reduces profiling and unnecessary visitor data exposure.

Breakdown

Evidence by category.

Efficiency

95
#1 of 2

3 pages · ~550 KB measured/page · 16 resource references/page · 100% sampled assets cacheable.

Evidence and scoring

Evidence: 3 pages · ~550 KB measured/page · 16 resource references/page · 100% sampled assets cacheable.

  • PayloadMeasured HTML and sampled asset payload is proportionate and optimised.15/20
  • JavaScriptReferenced JavaScript weight is kept proportionate.20/20
  • RequestsPages avoid excessive resource references and third-party connections.20/20
  • MediaImages and video avoid obvious loading and autoplay waste.20/20
  • Caching and compressionSampled static assets expose effective cache policy.20/20

Privacy

80
#1 of 2

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

Evidence and scoring

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

  • Behavioural trackingKnown advertising pixels and cross-site trackers are absent or minimised.20/20
  • Analytics minimisationAnalytics technology is absent or privacy-preserving and proportionate.20/20
  • Cookies and consentNon-essential response cookies are avoided before interaction.20/20
  • Third-party disclosureResource loading does not unnecessarily disclose visits to third parties.0/20
  • Invasive techniquesKnown session replay and similarly invasive tools are absent.20/20

Sovereignty

65
#1 of 2

1 US-headquartered visitor-facing provider ecosystems · 43% first-party assets · open technology 73/100 · no framework signal required/detected. DNS: NS jose.ns.cloudflare.com, lily.ns.cloudflare.com · MX 10 mail.protonmail.ch, 20 mailsec.protonmail.ch.

Evidence and scoring

Evidence: 1 US-headquartered visitor-facing provider ecosystems · 43% first-party assets · open technology 73/100 · no framework signal required/detected. DNS: NS jose.ns.cloudflare.com, lily.ns.cloudflare.com · MX 10 mail.protonmail.ch, 20 mailsec.protonmail.ch.

  • Provider jurisdictionObservable visitor-facing dependencies minimise reliance on US-headquartered platform ecosystems.15/20
  • Third-party geographyKnown non-EU third-party data exposure is minimised.20/20
  • Portable deliveryPages minimise proprietary embeds and platform-specific content dependencies.20/20
  • Supplier concentrationThird-party resource loading is not dominated by one provider ecosystem.0/20
  • Open technologyOpen standards, first-party delivery, open-source technology and public source code are preferred where practical.10/20

Accessibility

80
#2 of 2

0 semantic issues · 0 keyboard markup issues · 50% unlabelled controls · 100% raw/rendered text ratio.

Evidence and scoring

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

  • SemanticsHTML exposes basic language, heading and landmark structure.20/20
  • Keyboard accessMarkup avoids obvious keyboard-hostile interaction patterns.20/20
  • Forms and controlsForm controls expose labels or accessible names.0/20
  • Visual accessibilityViewport and media markup avoid obvious visual accessibility barriers.20/20
  • ResilienceMeaningful text remains present without relying entirely on client rendering.20/20

Responsibility

75
#2 of 2

Privacy ✓ · Cookies n/a · Terms ✓ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. verified green hosting (Cloudflare). carbon.txt ✗ · 5/5 security headers.

Evidence and scoring

Evidence: Privacy ✓ · Cookies n/a · Terms ✓ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. verified green hosting (Cloudflare). carbon.txt ✗ · 5/5 security headers.

  • Public accountabilityPrivacy, terms, accessibility, contact and applicable registration information are discoverable.5/20
  • Security basicsThe main response exposes sensible browser security headers.20/20
  • Consent designTracking and consent markup avoids obvious one-sided choice patterns.20/20
  • Supplier disclosureDetected material visitor-facing providers are reflected in discoverable privacy information.20/20
  • Sustainability evidenceGreen hosting, carbon.txt and public sustainability information provide discoverable evidence of digital sustainability practice.10/20