Manifest position 884 · CrUX rank bucket 1000
https://www.hln.be
Coverage complete
Atomic audit completed across eight representative public paths. Account sign-in itself could not proceed beyond the observed 406 state; that state is recorded as a direct issue rather than omitted.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Light and dark mobile captures are pixel-equivalent in appearance; the probe reports colorScheme "normal", and captured CSS contains no prefers-color-scheme rule. F01 medium: The site does not adapt to the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The normal and prefers-reduced-motion probes both report the same 13 running animations, including 273,620 ms ticker/swap animations; captured CSS contains no prefers-reduced-motion rule. F02 medium: Continuous ticker and pulse animations continue under reduced-motion. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast: more mobile screenshot remains legible with visible headlines, controls and status chips; Lighthouse contrast audit scored pass. |
implement-natural-interactionsview-transitions | issues | medium | DOM/CSS captures across the home, section and article templates contain no view-transition declaration, so full-page news navigation swaps abruptly. F03 low: Route changes do not use cross-document View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | Screenshots and CSS capture show no parallax/scrollytelling effect and no scroll event driven animation surface; ordinary scrolling remains native. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No audited path exposes a custom swipe, pull-to-refresh, draggable, or snap-based gesture surface; ordinary native scrolling is the only physical gesture. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Captured CSS uses fixed/relative header class toggles but contains no scroll-state container query; the long article has 11,209 px of content with no declarative reading-progress affordance. F04 low: Sticky navigation is not implemented with scroll-state-aware CSS. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, transient popover, or edge-positioned menu was present on the representative public paths, so there is no anchored overlay to judge. |
provide-guided-navigationdirects-attention | pass | high | Article navigation highlights “Buitenland” in red, search results repeat the query in the heading, and the 404 provides a prominent home recovery action. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh screenshot captures expose the lead story immediately; no full-viewport ad or popup obscures content in the tested regional state. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal/dialog/disclosure overlay was present in the representative content, search, video, error, or blocked-login states. |
maximize-content-reduce-noisereduced-chrome | pass | high | Mobile captures prioritise lead story, article body, search results and video cards; header chrome is compact relative to content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Both 360 px layout captures report horizontalOverflowPx 0 and a viewport meta tag; home and article reflow to exactly 360 px. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS from home and article templates contains no @container or container-type declaration, despite cards being reused in hero, rail, list and mobile contexts. F05 low: Templates rely on viewport media queries rather than component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home focus probe reports most links with outline-style none and no box shadow; multiple visible links are only 12–20 px high. The article template has a stronger 2 px focus outline, showing cross-template inconsistency. F06 medium: Keyboard focus and touch-target treatment is inconsistent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home leads with current news, article leads with hero/headline/body, search has a singular labelled query action, and video leads with playable cards. |
support-core-task-successprimary-flow-completion | pass | high | The public core journeys from listing to article and from search query to results completed; article content is readable without account creation. |
support-core-task-successclear-system-state-and-recovery | pass | high | Search clearly reports results for “Belgie”; the 404 explains the failure and offers “Terug naar home”; blocked login explains the alternate-code recovery concept. |
be-fast-and-stablegood-core-web-vitals | issues | high | The 360×800 layout capture measured CLS 0.160156 with a single shift at about 5.08 s; Lighthouse also measured cold-load LCP at 3.7 s on home and 4.2 s on the article. F07 medium: The mobile homepage has a poor layout-stability result. |
be-fast-and-stablevisual-stability | pass | high | The article’s 360 px layout capture measured CLS 0.0052 with no horizontal overflow; the homepage instability is recorded separately under the aggregate CWV check. |
be-fast-and-stableefficient-main-thread | pass | high | Trace summary measured zero long tasks and 0 ms TBT on the home trace; mobile observers saw only two 51–56 ms home tasks and one 71 ms article task. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 143 requests and 7,769,884 transferred bytes. Seven video-segment requests contributed 4,388,646 bytes, while scripts contributed 2,445,626 bytes. F08 high: The homepage loads a disproportionate network payload before the user asks for rich media. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The article HAR recorded 72 scripts and 2,749,557 script bytes; the live script inventory includes repeated pexi.js loads plus advertising, survey, experimentation and analytics libraries. F09 medium: Third-party and duplicated script work dominates page delivery. |
be-inclusivenames-roles-labels | issues | high | The home probe found one unlabelled visible input; the input inventory shows the required newsletter email field has no label or aria-label. The image audit found 100 home images without alt values, including story imagery. F10 medium: Some controls and content images lack robust accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse contrast audit passed and standard/high-contrast screenshots keep text and controls legible. |
be-inclusivestructure-and-focus | issues | high | The article probe jumps from H1 to an H6 newsletter heading before H2; Lighthouse also flags non-sequential heading order in the consent surface. F11 medium: Heading structure skips levels and differs between templates. |
be-inclusivelegible-text | pass | high | Article mobile capture uses a readable measure, strong hierarchy and unclipped body text; search/listing copy remains readable at 360 px. |
be-inclusivezoom-reflow-targets-and-media | pass | high | The tested 360 px reflow has no horizontal overflow, viewport permits scaling, and video cards expose visible play actions and durations. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with an empty item list. |
follow-best-practicessound-document-and-assets | issues | high | The article image audit found 8 images without dimensions, 12 oversized images, 53 without srcset and 29 legacy-format images. F12 medium: Article assets are not consistently dimensioned or responsive. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse reports three BFCache failure reasons around Cache-Control: no-store and a DevTools cookie issue. F13 low: The consent journey prevents back/forward cache restoration and raises browser issues. |
be-discoverabletitle-and-description | pass | high | Rendered home and article probes contain unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All 355 home anchors in the live DOM have href values, viewport metadata is present, and the generic robots policy allows public content paths. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and article expose canonical URLs, article permits large snippets/previews, robots points to current news and archive sitemaps, and document requests succeed. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article exposes NewsArticle, WebSite, BreadcrumbList and VideoObject JSON-LD plus complete Open Graph metadata matching the visible story. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers include HSTS, nosniff and X-Frame-Options, but CSP permits unsafe-inline and unsafe-eval. The cookie audit found 22 of 24 cookies lacking Secure and many SameSite=None cookies. F14 high: Cookie and CSP configuration weakens otherwise strong transport security. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker capture saw 50 third-party origins and 11 known tracker domains. The HAR classified 137 of 143 requests and 7.66 MB of 7.77 MB as cross-origin. F15 high: The default page has an extensive advertising and tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Navigating to /login ends on a 406 “Inlogpoging geblokkeerd” page. It instructs users to go back and use an emailed six-digit code, but presents no actionable return link or phishing-resistant passkey option. F16 medium: The tested login path is blocked and offers no passkey route. |
be-private-and-securedefensive-browser-policies | pass | high | Headers include HSTS preload, X-Frame-Options DENY, nosniff, strict-origin-when-cross-origin Referrer-Policy and a Permissions-Policy; CSP weakness is recorded separately. |
be-resilientprogressive-enhancement | issues | high | Discoverability fetches for home and article each saw about 8 KB of raw HTML, only 3 content tokens, no title/H1/description and 0% rendered-word coverage because the response is a privacy-gate shell. F17 high: Core news content is not present in the raw no-JavaScript response for a generic crawler. |
be-resilientresilient-runtime-behaviour | pass | high | Representative navigation, search, video and 404 states rendered without clipped overlays or blank runtime shells in normal JavaScript operation. |
be-resilientoffline-and-installable | issues | high | The home and article probes find a manifest but no controlling service worker; no offline fallback is available for a news product whose read path benefits from flaky-network resilience. F18 medium: The install manifest is not backed by an active offline experience. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid route returns an explanatory “Er ging iets fout” page with a prominent home action and current-news fallback. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | HLN is a deliberately Dutch-language Belgian news service in the audited scope; no alternate language or writing-mode journey was offered. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited service is single-locale (nl-BE) and exposes no user-selectable locale or cross-locale data-entry flow. |
be-internationalisedtime-zone-correctness | not-applicable | high | No cross-time-zone event scheduling or partial-time input flow exists in the representative news-reading/search scope. |
be-trustworthyno-dark-patterns | pass | high | The tested public article and search flows did not force signup or obscure the free story; subscription and login actions are visibly labelled. |
be-trustworthyhumane-error-handling | pass | high | Required search/email fields use native required/input types; 404 and blocked-login states explain what happened without blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | The home input inventory shows both email fields with an empty autocomplete value, and the required compact newsletter field has no programmatic label. F19 low: Newsletter email inputs omit autocomplete hints. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The 406 blocked-login page contains instructions but no button or link back to the alternative code flow, so the user cannot continue from the state presented. F20 medium: The account entry flow dead-ends in the audited environment. |
be-sustainableoptimised-assets | issues | high | The article image audit found 12 oversized images, 53 without responsive sources and 29 legacy-format assets, including 480 px GIF/JPEG thumbnails displayed at 112 px. F21 medium: Article recommendations ship oversized and legacy media. |
be-sustainableno-wasteful-work | issues | high | The home probe found no autoplay media element, yet the HAR downloaded seven HLS segments totalling 4.39 MB and contacted 50 third-party origins during initial load. F22 high: Background video and vendor work consumes megabytes without an explicit play action. |
be-sustainablethird-party-and-media-budget | issues | high | Cross-origin resources account for 7.66 MB of 7.77 MB transferred on the homepage, including video, player, tag-manager, advertising and experimentation payloads. F23 high: Third-party media cost is disproportionate to a news homepage first view. |
be-agent-readystructured-agent-capabilities | issues | high | robots.txt disallows GPTBot, ChatGPT-User, ClaudeBot, Google-Extended, Perplexity and many peers; captured DOM has no WebMCP/agent-tool surface, although article JSON-LD is strong. F24 low: The site deliberately blocks major AI agents and exposes no structured action interface. |
be-agent-readyon-device-inference | not-applicable | high | On-device generation or summarisation is not necessary to complete the public news reading, search, video, login or recovery tasks audited. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll-down/up cycles, DOM count stayed 3,924 and JS used heap rose about 1.24 MB; heap snapshot self size rose only 0.34 MB (~0.7%), with no evidence of unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | The rich news homepage retained about 48.4 MB self size and 43 MB used JS heap; this is substantial but proportionate to the observed media/vendor-heavy page and remained bounded during the exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries show no Detached* constructor among top retained constructors, DOM node count stayed constant, and closure count rose only 109 after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0884-www_hln_be.json
Report SHA-256: b585d4328ac5fc82a15d8f9915055009db14bd811009ccef666276ae626a9fc4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_hln_be/2026-07-23T15-39-22-978Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_hln_be/2026-07-23T15-39-22-978Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.