ecomark.

EcoMark analysis · Algo v1

Zero Hour - Join the campaign for climate and nature

Published 28 Aug 2026

Site history
B80#1 of 1 at publication

Automated EcoMark v1 analysis of 1 public page. The homepage was browser-rendered.

Algorithm v1 · Raw evidence

Improve

Start with these changes.

1

efficiency

Lazy-load below-the-fold media and remove autoplay.

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

2

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.

3

responsibility

Make privacy, cookie, accessibility and contact information easy to find.

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

Breakdown

Evidence by category.

Efficiency

45
#1 of 1

1 pages · ~113 KB measured/page · 75 resource references/page · 0% sampled assets cacheable.

Evidence and scoring

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

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

Privacy

100
#1 of 1

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 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.20/20
  • Invasive techniquesKnown session replay and similarly invasive tools are absent.20/20

Sovereignty

95
#1 of 1

1 US-headquartered provider ecosystems · 100% first-party assets · 0 proprietary embeds.

Evidence and scoring

Evidence: 1 US-headquartered provider ecosystems · 100% first-party assets · 0 proprietary embeds.

  • Provider jurisdictionObservable 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.20/20
  • First-party deliveryAssets are delivered directly from the site where practical.20/20

Accessibility

80
#1 of 1

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

Evidence and scoring

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

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

Responsibility

85
#1 of 1

4/5 security headers · 2 missing transparency links · 0% detected providers undisclosed.

Evidence and scoring

Evidence: 4/5 security headers · 2 missing transparency links · 0% detected providers undisclosed.

  • TransparencyPrivacy, cookies, accessibility and contact information are discoverable.10/20
  • Security basicsThe main response exposes sensible browser security headers.15/20
  • Consent designTracking and consent markup avoids obvious one-sided choice patterns.20/20
  • Supplier disclosureDetected material providers are reflected in discoverable privacy information.20/20
  • Responsible defaultsThe observable site defaults avoid trackers, autoplay and weak transparency/security.20/20