How this category score was calculated
- PayloadMeasured HTML and sampled asset payload is proportionate and optimised. · average_page_kb (lower is better)Level 4/4 · 20/20
- JavaScriptReferenced JavaScript weight is kept proportionate. · average_javascript_kb (lower is better)Level 4/4 · 20/20
- RequestsPages avoid excessive resource references and third-party connections. · average_resource_references (lower is better)Level 2/4 · 10/20
- MediaImages and video avoid obvious loading and autoplay waste. · media_issue_count (lower is better)Level 3/4 · 15/20
- Caching and compressionSampled static assets expose effective cache policy. · cacheable_asset_percent (higher is better)Level 0/4 · 0/20
What we found
1 pages · ~112 KB measured/page · 45 resource references/page · 0% sampled assets cacheable.
Evidence: 1 pages · ~112 KB measured/page · 45 resource references/page · 0% sampled assets cacheable.
Why it matters
Lighter pages consume less bandwidth and device work and remain usable on slower connections.
MEDIUM PRIORITYSimple action
Add long-lived cache headers to versioned static assets.
How this category score was calculated
- Behavioural trackingKnown advertising pixels and cross-site trackers are absent or minimised. · tracker_count (lower is better)Level 1/4 · 5/20
- Analytics minimisationAnalytics technology is absent or privacy-preserving and proportionate. · analytics_risk (lower is better)Level 2/4 · 10/20
- Cookies and consentNon-essential response cookies are avoided before interaction. · nonessential_cookie_count (lower is better)Level 4/4 · 20/20
- Third-party disclosureResource loading does not unnecessarily disclose visits to third parties. · third_party_percent (lower is better)Level 4/4 · 20/20
- Invasive techniquesKnown session replay and similarly invasive tools are absent. · invasive_tracker_count (lower is better)Level 4/4 · 20/20
What we found
4 known trackers · 0 tracking-style response cookies · 0% third-party resource references.
Evidence: 4 known trackers · 0 tracking-style response cookies · 0% third-party resource references.
Why it matters
Minimising tracking and third-party disclosure reduces profiling and unnecessary visitor data exposure.
MEDIUM PRIORITYSimple action
Remove behavioural advertising pixels and cross-site trackers.
How this category score was calculated
- Provider jurisdictionObservable visitor-facing dependencies minimise reliance on US-headquartered platform ecosystems. · us_provider_count (lower is better)Level 3/4 · 15/20
- Third-party geographyKnown non-EU third-party data exposure is minimised. · known_non_eu_data_percent (lower is better)Level 4/4 · 20/20
- Portable deliveryPages minimise proprietary embeds and platform-specific content dependencies. · proprietary_embed_count (lower is better)Level 4/4 · 20/20
- Supplier concentrationThird-party resource loading is not dominated by one provider ecosystem. · top_provider_share_percent (lower is better)Level 4/4 · 20/20
- Open technologyOpen standards, first-party delivery, open-source technology and public source code are preferred where practical. · open_technology_score (higher is better)Level 4/4 · 20/20
What we found
1 US-headquartered visitor-facing provider ecosystems · 100% first-party assets · open technology 90/100 · no framework signal required/detected. DNS: NS ns2.meganameservers.eu, ns3.meganameservers.eu · MX 10 alt3.aspmx.l.google.com, 1 aspmx.l.google.com · CNAME proxy-05b86f87047461da66d30f5b.nationbuilder.com.
Evidence: 1 US-headquartered visitor-facing provider ecosystems · 100% first-party assets · open technology 90/100 · no framework signal required/detected. DNS: NS ns2.meganameservers.eu, ns3.meganameservers.eu · MX 10 alt3.aspmx.l.google.com, 1 aspmx.l.google.com · CNAME proxy-05b86f87047461da66d30f5b.nationbuilder.com.
Why it matters
A more portable and less concentrated stack gives organisations more control over technology and jurisdiction.
LOW PRIORITYSimple action
No material issue was detected in this category. Maintain the current practice and re-run EcoMark after material website changes.
How this category score was calculated
- SemanticsHTML exposes basic language, heading and landmark structure. · semantic_issue_count (lower is better)Level 1/4 · 5/20
- Keyboard accessMarkup avoids obvious keyboard-hostile interaction patterns. · keyboard_issue_count (lower is better)Level 4/4 · 20/20
- Forms and controlsForm controls expose labels or accessible names. · unlabelled_control_percent (lower is better)Level 4/4 · 20/20
- Visual accessibilityViewport and media markup avoid obvious visual accessibility barriers. · visual_issue_count (lower is better)Level 3/4 · 15/20
- ResilienceMeaningful text remains present without relying entirely on client rendering. · raw_text_ratio_percent (higher is better)Level 1/4 · 5/20
What we found
3 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 24% raw/rendered text ratio.
Evidence: 3 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 24% raw/rendered text ratio.
Why it matters
Accessible, resilient markup works for more people, assistive technology and older or constrained devices.
MEDIUM PRIORITYSimple action
Fix basic document semantics: language, one clear H1 and meaningful landmarks/headings.
How this category score was calculated
- Public accountabilityPrivacy, terms, accessibility, contact and applicable registration information are discoverable. · transparency_evidence_score (higher is better)Level 0/4 · 0/20
- Security basicsThe main response exposes sensible browser security headers. · security_header_count (higher is better)Level 2/4 · 10/20
- Consent designTracking and consent markup avoids obvious one-sided choice patterns. · consent_issue_score (lower is better)Level 1/4 · 5/20
- Supplier disclosureDetected material visitor-facing providers are reflected in discoverable privacy information. · undisclosed_provider_percent (lower is better)Level 4/4 · 20/20
- Sustainability evidenceGreen hosting, carbon.txt and public sustainability information provide discoverable evidence of digital sustainability practice. · sustainability_evidence_score (higher is better)Level 0/4 · 0/20
What we found
Privacy ✗ · Cookies ✗ · Terms ✗ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. no verified green-hosting evidence found. carbon.txt ✗ · 3/5 security headers.
Evidence: Privacy ✗ · Cookies ✗ · Terms ✗ · Accessibility ✗ · Contact/About ✗. Public registration IDs: none detected. no verified green-hosting evidence found. carbon.txt ✗ · 3/5 security headers.
Why it matters
Transparent, secure defaults make digital impact understandable and give visitors meaningful choices.
HIGH PRIORITYSimple action
Publish clearly linked privacy, terms, accessibility and contact information, plus a public registration identifier where applicable.