ecomark.

Algorithm v4 · current

How EcoMark scores a website.

EcoMark uses observable website evidence. AI does not decide the score.

v1 v2 v3 v4

  1. EnterAdd a public website.
  2. CrawlCheck a small sample and key policy pages.
  3. AnalyseMeasure weight, tracking, providers and accessibility signals.
  4. GradeApply the public EcoMark algorithm.
  5. ImproveShow the clearest next steps.

Scoring

Twenty-five published criteria.

Each criterion gets a level from 0 to 4. Category scores are weighted into the final score.

25%

Efficiency

Resource use, page weight and avoidable computation.

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

Privacy

Tracking, cookies, profiling, analytics and consent.

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

Sovereignty

Ownership, geography, openness, portability and dependency.

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

Accessibility

Inclusive, semantic and resilient implementation.

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

Responsibility

Transparency, security basics and responsible choices.

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

Grades

A simple final band.

A 90–100 · B 80–89 · C 70–79 · D 60–69 · E 50–59 · F 0–49

Versioning

Scoring changes get a new version.

Historical results keep the algorithm that produced them.