# zerohour.uk EcoMark analysis | v4 Dated EcoMark analysis for zerohour.uk: C 72/100 using algorithm v4. Canonical: https://ecomark.app/assessment/00a145c4-f3b5-4c6f-83d2-2d464007b153 EcoMark analysis · Algo v4 # zerohour.uk Published 28 Aug 2026 Rescan website [Site history](/site/zerohour.uk) C 72 #2 of 4 at publication This grade belongs to zerohour.uk. It is based on a bounded sample of up to 5 connected public pages plus public evidence. It is not a grade for any one page. Automated EcoMark v4 approximation using up to 5 connected pages, DNS, active policy/sitemap discovery, browser security checks and lightweight performance diagnostics. Browser Run was blocked or incomplete, so the normal public HTML response was used instead. Analysis quality: good. [Algorithm v4](/methodology/v4) · [Raw evidence](/evidence/00a145c4-f3b5-4c6f-83d2-2d464007b153) 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 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. 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 55 #4 of 4 5 connected pages · ~1552 KB measured/page · 0 KB JavaScript/page · 40 resource references/page · 25% sampled assets cacheable. PageSpeed-style checks: 2/7; 7 obvious blocking candidates; 29 images without width/height. **Evidence and scoring** Evidence: 5 connected pages · ~1552 KB measured/page · 0 KB JavaScript/page · 40 resource references/page · 25% sampled assets cacheable. PageSpeed-style checks: 2/7; 7 obvious blocking candidates; 29 images without width/height. - 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. 15/20 - Media Images and video avoid obvious loading and autoplay waste. 5/20 - Caching and compression Sampled static assets expose effective cache policy. 5/20 Privacy 80 #2 of 4 0 known trackers · 0 tracking-style response cookies · 79% third-party resource references. **Evidence and scoring** Evidence: 0 known trackers · 0 tracking-style response cookies · 79% 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. 0/20 - Invasive techniques Known session replay and similarly invasive tools are absent. 20/20 Sovereignty 65 #3 of 4 1 US-headquartered visitor-facing provider ecosystems · 22% first-party assets · open technology 67/100 · no framework signal required/detected. DNS: NS rene.ns.cloudflare.com, stephane.ns.cloudflare.com · MX 1 aspmx.l.google.com, 5 alt1.aspmx.l.google.com. **Evidence and scoring** Evidence: 1 US-headquartered visitor-facing provider ecosystems · 22% first-party assets · open technology 67/100 · no framework signal required/detected. DNS: NS rene.ns.cloudflare.com, stephane.ns.cloudflare.com · MX 1 aspmx.l.google.com, 5 alt1.aspmx.l.google.com. - 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. 0/20 - Open technology Open standards, first-party delivery, open-source technology and public source code are preferred where practical. 10/20 Accessibility 85 #1 of 4 3 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 100% raw/rendered text ratio. **Evidence and scoring** Evidence: 3 semantic issues · 0 keyboard markup issues · 0% unlabelled controls · 100% raw/rendered text ratio. - Semantics HTML exposes basic language, heading and landmark structure. 5/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. 20/20 - Resilience Meaningful text remains present without relying entirely on client rendering. 20/20 Responsibility 80 #1 of 4 Privacy ✓ · Cookies n/a · Terms ✓ · Accessibility ✗ · Contact/About ✓. Public registration IDs: UK company number 12846343. verified green hosting (Cloudflare). carbon.txt ✗ · sitemap ✓ · security 5/6. Missing: HSTS. **Evidence and scoring** Evidence: Privacy ✓ · Cookies n/a · Terms ✓ · Accessibility ✗ · Contact/About ✓. Public registration IDs: UK company number 12846343. verified green hosting (Cloudflare). carbon.txt ✗ · sitemap ✓ · security 5/6. Missing: HSTS. - Public accountability Privacy, terms, accessibility, contact and applicable registration information are discoverable. 15/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. 10/20