How this category score was calculated
- PayloadMeasured HTML and 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 3/4 · 15/20
- MediaImages and video avoid obvious loading and autoplay waste. · media_issue_count (lower is better)Level 0/4 · 0/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 · ~148 KB measured/page · 33 resource references/page · 0% sampled assets cacheable.
Evidence: 1 pages · ~148 KB measured/page · 33 resource references/page · 0% sampled assets cacheable.
Why it matters
Lighter pages consume less bandwidth and device work and remain usable on slower connections.
HIGH PRIORITYSimple action
Lazy-load below-the-fold media and remove autoplay.
How this category score was calculated
- Behavioural trackingKnown advertising pixels and cross-site trackers are absent or minimised. · tracker_count (lower is better)Level 4/4 · 20/20
- Analytics minimisationAnalytics technology is absent or privacy-preserving and proportionate. · analytics_risk (lower is better)Level 4/4 · 20/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
0 known trackers · 0 tracking-style response cookies · 0% third-party resource references.
Evidence: 0 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.
LOW PRIORITYSimple action
Remove behavioural advertising pixels and cross-site trackers.
How this category score was calculated
- Provider jurisdictionObservable 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
- First-party deliveryAssets are delivered directly from the site where practical. · first_party_asset_percent (higher is better)Level 4/4 · 20/20
What we found
1 US-headquartered provider ecosystems · 100% first-party assets · 0 proprietary embeds.
Evidence: 1 US-headquartered provider ecosystems · 100% first-party assets · 0 proprietary embeds.
Why it matters
A more portable and less concentrated stack gives organisations more control over technology and jurisdiction.
LOW PRIORITYSimple action
Reduce critical dependence on large non-European platform ecosystems where practical.
How this category score was calculated
- SemanticsHTML exposes basic language, heading and landmark structure. · semantic_issue_count (lower is better)Level 3/4 · 15/20
- Keyboard accessMarkup avoids obvious keyboard-hostile interaction patterns. · keyboard_issue_count (lower is better)Level 3/4 · 15/20
- Forms and controlsForm controls expose labels or accessible names. · unlabelled_control_percent (lower is better)Level 0/4 · 0/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 4/4 · 20/20
What we found
1 semantic issues · 1 keyboard markup issues · 100% unlabelled controls · 82% raw/rendered text ratio.
Evidence: 1 semantic issues · 1 keyboard markup issues · 100% unlabelled controls · 82% raw/rendered text ratio.
Why it matters
Accessible, resilient markup works for more people, assistive technology and older or constrained devices.
MEDIUM PRIORITYSimple action
Give every form control a programmatic label or accessible name.
How this category score was calculated
- TransparencyPrivacy, cookies, accessibility and contact information are discoverable. · missing_transparency_links (lower is better)Level 2/4 · 10/20
- Security basicsThe main response exposes sensible browser security headers. · security_header_count (higher is better)Level 0/4 · 0/20
- Consent designTracking and consent markup avoids obvious one-sided choice patterns. · consent_issue_score (lower is better)Level 4/4 · 20/20
- Supplier disclosureDetected material providers are reflected in discoverable privacy information. · undisclosed_provider_percent (lower is better)Level 4/4 · 20/20
- Responsible defaultsThe observable site defaults avoid trackers, autoplay and weak transparency/security. · responsible_default_issue_count (lower is better)Level 3/4 · 15/20
What we found
1/5 security headers · 2 missing transparency links · 0% detected providers undisclosed.
Evidence: 1/5 security headers · 2 missing transparency links · 0% detected providers undisclosed.
Why it matters
Transparent, secure defaults make digital impact understandable and give visitors meaningful choices.
MEDIUM PRIORITYSimple action
Add the missing browser security headers, prioritising HSTS, CSP and a clear referrer policy.