Manifest position 830 · CrUX rank bucket 1000
https://www.dagbladet.no
Coverage complete
Coverage-complete representative audit of five public templates/states. Video/live studio, authenticated account management, and purchase submission were not exercised because they are separate high-risk journeys or require credentials; relevant static controls and policies were inspected.
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 | Screenshot under prefers-color-scheme: dark and computed colorScheme=normal show the page remains light; the dark capture is evidence of no user-preference theme adaptation. F01 medium: Dark mode preference is ignored |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce matched, the probe still found 12 running animations, including pulsate and animated-background effects lasting 6–18 seconds. F02 medium: Reduced-motion users still receive continuous animation |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast: more screenshot retained visible text and controls without clipping; Lighthouse isolated a normal-mode color pair rather than a forced/high-contrast disappearance. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS probes across the homepage, listing, and article found no route-transition styling; navigation uses ordinary document swaps with no View Transition signal. F03 low: News navigation swaps documents abruptly |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No applicable scroll-linked motion was observed. |
implement-natural-interactionsphysical-gestures | pass | high | The responsive pages use native document scrolling with no observed custom pointermove gesture layer that fights platform scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The page probe found no container rules and screenshots show fixed, unchanged masthead chrome; no scroll-state-aware header/progress affordance was found on long news pages. F04 low: Long pages provide no scroll-state-aware navigation cue |
provide-guided-navigationanchored-positioning | not-applicable | high | Direct review of representative rendered templates found the expected outcome. |
provide-guided-navigationdirects-attention | pass | high | Real, descriptive links, a skip link to #main, section navigation, and prominent article headings guide navigation across the representative templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Fresh desktop and mobile loads are obscured by a modal consent wall before any news content can be read; the mobile dialog occupies nearly the entire 360×800 viewport. F05 high: Consent wall obscures all news content on first load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM reports a DIV role=dialog aria-modal=true rather than a native <dialog>; the cross-origin consent surface relies on custom modal plumbing. F06 medium: Consent modal uses a custom DIV dialog |
maximize-content-reduce-noisereduced-chrome | pass | high | Behind the consent state, the masthead remains compact and the visual hierarchy is predominantly editorial imagery and headlines rather than application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, homepage and article layout metrics report scrollWidth=clientWidth=360 and horizontalOverflowPx=0, with a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Computed CSS inspection across all representative templates found zero @container rules; reusable cards appear governed only by page/viewport layout. F07 low: Reusable cards do not use container-level adaptation |
adapt-to-the-form-factorinput-modality-aware | pass | high | Lighthouse target-size passed, the DOM includes a keyboard skip link, and mobile controls are visibly large enough for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The masthead, descriptive titles, topical links, and article headline clearly identify a news publication and the next action; consent choices are explicitly labelled. |
support-core-task-successprimary-flow-completion | pass | high | A real crawlable link from the homepage/listing reaches a server-rendered article with 98% no-JS content coverage; the read-news flow has no account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The exercised missing-page route presents a clear “Side ikke funnet” state, explains the problem, and provides a prominent return-to-home action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.7s and FCP 6.3s (performance 0.56); the independent trace measured LCP 6.92s. CLS remained low. F08 high: Largest content appears after roughly seven seconds |
be-fast-and-stablevisual-stability | pass | high | Homepage CLS was 0 and article CLS 0.0133 in layout observers; Lighthouse CLS was 0.007, all comfortably within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded one 54.2ms long task and 4.2ms TBT; Lighthouse TBT was 66.5ms, indicating low blocking despite slow loading. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 4.73MB/118 requests, 10 parser-inserted high-priority stylesheet candidates and multiple images taking over 3s; LCP was 6.9–7.7s. F09 medium: The critical network path is heavy and fragmented |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The homepage loaded 33 scripts (1.12MB), with 43 third-party requests/1.40MB including ad-tech libraries; this is disproportionate scripting for first-paint news reading. F10 medium: Third-party scripting imposes a large startup cost |
be-inclusivenames-roles-labels | pass | high | Lighthouse accessibility scored 0.96 and its image-alt audit passed; skip links and semantic anchors were present. The separate image inventory was treated as a diagnostic because many empty alts are plausibly decorative/link-context images. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found the “KATASTROFEBRANNEN:” kicker at only 3.43:1 (#d60000 on #f1ca3f), below the required 4.5:1 for 16px text. F11 medium: A headline kicker fails text contrast |
be-inclusivestructure-and-focus | issues | high | Homepage and section probes found no H1 at all, while the article DOM includes a second unrelated H1 in recommended content; this weakens page-level heading structure despite Lighthouse heading-order passing. F12 medium: Page-level heading structure is inconsistent |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable text sizing and wrapping; no horizontal clipping was measured at 360px. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport permits scaling (width=device-width, initial-scale=1), 360px reflow had no overflow, and Lighthouse target-size passed. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured “paywall - kilkaya error ReferenceError: kilkaya is not defined” from the homepage. F13 low: A paywall integration throws on load |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 7 missing dimensions, 26 oversized images and 94/100 without srcset; the document itself had a valid viewport and metadata. F14 medium: Image markup wastes bytes and risks instability |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three BFCache failure reasons, including main-resource cache-control:no-store, plus inspector issues. F15 medium: The homepage cannot use the back/forward cache |
be-discoverabletitle-and-description | pass | high | Homepage, listing, article and subscription probes all found unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Internal navigation uses real href links, viewport metadata is valid, robots allows general crawling, and Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | pass | high | All representative public pages returned content with canonical URLs; robots advertises sitemap indexes and does not accidentally noindex these paths. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage/listing expose WebPage JSON-LD and Open Graph metadata; the article exposes NewsArticle JSON-LD and matching article previews. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but the header primitive found no CSP or HSTS and five cookies lacked Secure, including long-lived tracking/session-related cookies. F16 high: Baseline transport defenses and cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 20 third-party origins and known DoubleClick/Rubicon trackers; HAR attributed 43 requests and 1.40MB to third parties before consent choice. F17 high: Tracking starts with a broad third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt or permission-enabled iframe appeared on load; the subscription surface delegates sign-in to aID and exposes no password field in the initial flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy, Permissions-Policy, or nosniff; several SameSite=None cookies were set. F18 high: Browser-enforced defensive headers are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 91% raw-HTML coverage on the homepage and 98% on the article, with title/description and article H1 available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The consent overlay remains contained and actionable at 360px, links are ordinary documents, and representative pages rendered without a broken shell. |
be-resilientoffline-and-installable | not-applicable | high | No app-like install requirement applies to the representative MPA news experience. |
be-resilientnetwork-and-http-failure-states | pass | high | The intentionally invalid route renders a useful branded 404 explanation and a clear return-home control rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Representative pages declare nb-no/nb-NO and render Norwegian copy in the expected LTR reading order at mobile and desktop sizes. |
be-internationalisedlocale-aware-data | not-applicable | high | No applicable locale-sensitive transaction or formatting surface was present. |
be-internationalisedtime-zone-correctness | not-applicable | high | No applicable time-zone scheduling interaction was present. |
be-trustworthyno-dark-patterns | issues | high | Consent uses a saturated blue “Godta alle” primary button while “Tilpass eller avvis” is muted grey, creating visual asymmetry for equally important consent choices. F19 high: Consent choices have unequal visual prominence |
be-trustworthyhumane-error-handling | pass | high | The subscription DOM includes explicit success and payment-error states plus “Prøv ny betaling” and return-to-content controls, giving clear recovery actions. |
be-trustworthytrustworthy-input-assistance | pass | medium | The visible initial subscription flow uses native radio/button controls and a delegated aID sign-in rather than unlabelled free-form credential fields. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The subscription surface exposes distinct plan/payment controls, aID sign-in, Vipps payment, terms, payment-error retry, and return-to-content actions; no purchase was submitted. |
be-sustainableoptimised-assets | issues | high | The image inventory found 26 oversized images, 94/100 lacking srcset and 28 below-fold images not lazy-loaded; HAR transferred 2.04MB of images. F20 medium: Responsive image delivery is under-optimised |
be-sustainableno-wasteful-work | issues | high | Before any content choice, the page initiated 118 requests including 43 third-party requests and loaded advertising/video scripts, indicating substantial background work not needed for reading the first headline. F21 medium: Substantial non-content work begins before user intent |
be-sustainablethird-party-and-media-budget | issues | high | Third parties consumed 1.40MB and the page transferred 683KB media plus 1.12MB script; ad/video vendors dominate a material share of the 4.73MB load. F22 medium: Third-party and media budgets are disproportionate to first-view news reading |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capability is outside the publisher’s explicit robots content policy. |
be-agent-readyon-device-inference | not-applicable | high | No agent/on-device inference surface applies under the publisher’s explicit AI-input restriction. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll-down/up cycles, heap self-size decreased from 32,745,366 to 32,581,159 bytes and node count decreased from 511,156 to 510,501; no retained growth was observed. |
be-memory-efficientbounded-footprint | pass | medium | The settled homepage heap was 32.7MB. Although DOM/native node population is large for a dense publication, the footprint remained stable during repeated feed interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries showed no growth and no Detached* constructor among top retained constructors; closures were effectively unchanged (24,829 to 24,828). |
Provenance
Canonical report: results/atomic/reports/0830-www_dagbladet_no.json
Report SHA-256: 7cd956b4dfece3499375105dceb82a626e74ad75c51418af4895b5058794d0dd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_dagbladet_no/2026-07-23T07-16-00-977Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_dagbladet_no/2026-07-23T07-16-00-977Z
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.