Manifest position 733 · CrUX rank bucket 1000
https://m.bild.de
Coverage complete
Coverage-complete audit. Consent UI prevented first-run interaction with underlying content, but server-rendered DOM, no-JS output, representative templates and objective browser evidence remained inspectable.
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 | Under prefers-color-scheme: dark, the site remains light; the platform probe found no prefers-color-scheme rules and computed color-scheme is light/normal. F02 medium: The site does not provide a user-preference-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | The loaded CSS contains prefers-reduced-motion handling, and document.getAnimations() returned zero on the first-run state. |
respect-user-preferencesrespects-contrast | pass | high | Under forced-colors: active and prefers-contrast: more, consent text, links, borders and controls remain visible with system colors. |
implement-natural-interactionsview-transitions | issues | high | The CSS/platform probe found no view-transition usage across the homepage bundle, while the site exposes many route and carousel state changes. F03 low: Route and state changes have no View Transition treatment |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation was present to implement with main-thread scroll handlers; getAnimations() was zero and the page uses native scrolling. |
implement-natural-interactionsphysical-gestures | pass | high | The loaded CSS uses scroll-snap for carousel-like content and no evidence showed pointer-driven scrolling fighting the platform. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The article is about 4,749 CSS px high and the homepage about 25,889 CSS px, but the CSS probe found no scroll timeline and screenshots show no reading-progress affordance. F04 low: Long news pages do not expose scroll-state guidance |
provide-guided-navigationanchored-positioning | pass | high | The loaded CSS contains anchor positioning support, providing declarative attachment for positioned UI. |
provide-guided-navigationdirects-attention | pass | medium | Skip-to-main, descriptive navigation labels, carousel control names, and visible headline hierarchy provide concrete navigation cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile and desktop screenshots of the homepage, section, article and search all show the same full-viewport modal before any content can be used. The only immediate paths are accepting tracking, opening settings, or paying for BILD Pur. F01 critical: Consent-or-subscribe wall blocks all content on every tested route |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | The page contains a native dialog plus a role=dialog consent wrapper rather than an unlabelled generic full-screen div. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Behind the modal, the page uses edge-to-edge editorial cards and imagery; the main failure is interruption rather than a persistent application frame. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 390x844, scrollWidth, clientWidth and innerWidth were all 390 with zero horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The loaded styles contain container query/container-type usage and the narrow layout reflows without overflow. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The homepage has no H1 and begins its sampled hierarchy at H3. The probe also found many carousel buttons rendered only 4 CSS px high. F09 medium: Homepage document structure and compact controls weaken keyboard/AT navigation |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage title, nav and headline cards clearly establish a current-news destination; the search page has an H1 and explicit search prompt. |
support-core-task-successprimary-flow-completion | issues | high | All four representative routes are obscured by the consent-or-pay wall; the agent could inspect server-rendered content but a first-time user cannot read or search before choosing tracking or subscription. F05 high: The primary read/search journeys are gated before they begin |
support-core-task-successclear-system-state-and-recovery | pass | high | A synthetic missing route returned HTTP 404 with an explicit German error document; the consent state clearly presents settings and subscription alternatives. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured performance 0.53, FCP 8.7 s, LCP 16.3 s and TTI 16.5 s. A separate warm trace measured LCP 2.22 s, showing the cold path is the material risk. F06 high: Cold mobile loading is slow |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer measured CLS 0 with no shifts; all 100 sampled images had explicit width and height. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured performance 0.53, FCP 8.7 s, LCP 16.3 s and TTI 16.5 s. A separate warm trace measured LCP 2.22 s, showing the cold path is the material risk. The HAR recorded 155 requests and 1.75 MB transferred during the sampled load, including 78 scripts; Lighthouse reported 2.96 MiB total, about 930 ms render-blocking savings, 185 KiB unused JS and 40 KiB unused CSS. F06 high: Cold mobile loading is slow F07 high: The critical path ships excessive render-blocking and unused resources |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 155 requests and 1.75 MB transferred during the sampled load, including 78 scripts; Lighthouse reported 2.96 MiB total, about 930 ms render-blocking savings, 185 KiB unused JS and 40 KiB unused CSS. F07 high: The critical path ships excessive render-blocking and unused resources |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR recorded 155 requests and 1.75 MB transferred during the sampled load, including 78 scripts; Lighthouse reported 2.96 MiB total, about 930 ms render-blocking savings, 185 KiB unused JS and 40 KiB unused CSS. F07 high: The critical path ships excessive render-blocking and unused resources |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name and frame-title. The DOM probe counted 143 links with no visible or fallback text and 184 controls without a detected name; the image primitive found 32 images without alt attributes. F08 high: Some links and frames have no accessible name |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 0.94 without a contrast failure, and forced-colors retained legible text and controls. |
be-inclusivestructure-and-focus | issues | high | The homepage has no H1 and begins its sampled hierarchy at H3. The probe also found many carousel buttons rendered only 4 CSS px high. F09 medium: Homepage document structure and compact controls weaken keyboard/AT navigation |
be-inclusivelegible-text | pass | high | Consent copy remains readable at mobile width with clear spacing and no clipping; article text is server-rendered and uses responsive layout. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The homepage has no H1 and begins its sampled hierarchy at H3. The probe also found many carousel buttons rendered only 4 CSS px high. F09 medium: Homepage document structure and compact controls weaken keyboard/AT navigation |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console; its run also reported an out-of-bounds source-map mapping for html-load.com/loader.min.js.map. F10 medium: The page logs browser errors |
follow-best-practicessound-document-and-assets | issues | high | The image audit found six oversized images and Lighthouse estimated 146 KiB image savings. The load also shipped 2.96 MiB overall despite the first viewport being blocked by consent. F16 medium: Media and code delivery exceed a proportionate first-view budget |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed errors-in-console; its run also reported an out-of-bounds source-map mapping for html-load.com/loader.min.js.map. F10 medium: The page logs browser errors |
be-discoverabletitle-and-description | pass | high | Homepage and article have descriptive titles and meta descriptions; article values accurately name the visible story. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed the robots-txt audit with one error, although manual inspection confirmed public crawling rules and four sitemap declarations. F17 low: robots.txt contains a syntax issue reported by Lighthouse |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage/article returned 200, declare canonical URLs and index/follow, and robots.txt lists four sitemap endpoints. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article supplies matching Open Graph fields plus NewsArticle and BreadcrumbList JSON-LD with dates, author, image and canonical entity URL. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirmed HTTPS but found no CSP, HSTS, X-Content-Type-Options, clickjacking policy, Referrer-Policy or Permissions-Policy on the audited document. Seven of eight observed cookies were flagged insecure; several analytics identifiers were SameSite=None and two persisted for 400 days. The response also lacked clickjacking, referrer and permissions policies. F11 high: Core browser security headers are absent F13 medium: Cookie and defensive policy posture is weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe saw 26 third-party origins and a known AppNexus origin. The HAR attributed 149 of 155 requests and 1.62 MB to origins other than m.bild.de (including related BILD hosts), and cookies were created before consent. F12 high: The pre-consent page has a large tracking and third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No notification or geolocation request code was found on load; the public reading journey requires no authentication. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive confirmed HTTPS but found no CSP, HSTS, X-Content-Type-Options, clickjacking policy, Referrer-Policy or Permissions-Policy on the audited document. Seven of eight observed cookies were flagged insecure; several analytics identifiers were SameSite=None and two persisted for 400 days. The response also lacked clickjacking, referrer and permissions policies. F11 high: Core browser security headers are absent F13 medium: Cookie and defensive policy posture is weak |
be-resilientprogressive-enhancement | pass | high | Raw HTML retained 81% of homepage content and 100% of article content; neither route is a JavaScript shell. |
be-resilientresilient-runtime-behaviour | pass | high | The first-run overlay remains within the viewport at desktop/mobile, uses fixed overflow handling, and CSS anchor positioning is available for attached UI. |
be-resilientoffline-and-installable | issues | high | A valid manifest is linked and includes icons, theme and language metadata, but the runtime probe found no controlling service worker. F14 medium: The installable news experience has no active offline controller |
be-resilientnetwork-and-http-failure-states | pass | high | A fabricated route returned HTTP 404 with an explicit German error page rather than a successful blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | html lang is de; the CSS bundle uses logical inline properties and the manifest also declares lang de and dir ltr. |
be-internationalisedlocale-aware-data | pass | high | Visible dates use German formatting while time elements carry unambiguous ISO datetime values. |
be-internationalisedtime-zone-correctness | pass | high | Published and modified times are represented as ISO timestamps with Z offsets, while presentation is localised for German readers. |
be-trustworthyno-dark-patterns | issues | high | The first-run modal gives a prominent free “Alle akzeptieren” action while the no-tracking route costs €3.99/month (€2.99 for subscribers); no equivalent free reject action is presented in the initial view. F15 high: Consent choice architecture is coercive |
be-trustworthyhumane-error-handling | not-applicable | high | No data-entry or submission form was present in the selected public reading/search path, so invalid-field timing and recovery do not apply. |
be-trustworthytrustworthy-input-assistance | pass | medium | The search page provides a visible “Was suchen Sie?” prompt and clearly named SUCHEN action; no checkout/address/payment fields occur in the selected primary journey. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The first-run modal gives a prominent free “Alle akzeptieren” action while the no-tracking route costs €3.99/month (€2.99 for subscribers); no equivalent free reject action is presented in the initial view. F15 high: Consent choice architecture is coercive |
be-sustainableoptimised-assets | issues | high | The image audit found six oversized images and Lighthouse estimated 146 KiB image savings. The load also shipped 2.96 MiB overall despite the first viewport being blocked by consent. F16 medium: Media and code delivery exceed a proportionate first-view budget |
be-sustainableno-wasteful-work | issues | high | The HAR recorded 155 requests and 1.75 MB transferred during the sampled load, including 78 scripts; Lighthouse reported 2.96 MiB total, about 930 ms render-blocking savings, 185 KiB unused JS and 40 KiB unused CSS. F07 high: The critical path ships excessive render-blocking and unused resources |
be-sustainablethird-party-and-media-budget | issues | high | The tracker probe saw 26 third-party origins and a known AppNexus origin. The HAR attributed 149 of 155 requests and 1.62 MB to origins other than m.bild.de (including related BILD hosts), and cookies were created before consent. The image audit found six oversized images and Lighthouse estimated 146 KiB image savings. The load also shipped 2.96 MiB overall despite the first viewport being blocked by consent. F12 high: The pre-consent page has a large tracking and third-party footprint F16 medium: Media and code delivery exceed a proportionate first-view budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | BILD explicitly disallows the audited AI/agent crawler set in robots.txt, indicating it does not intend an agent-facing capability surface for this content. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative feature is offered in the audited news reading/search experience, so on-device inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten down/up scroll cycles, retained self size changed only 104,366 bytes (0.22%) and object/closure populations were stable. |
be-memory-efficientbounded-footprint | pass | high | The content-heavy homepage retained about 47.2 MB; object and closure counts stayed stable across the comparison, proportionate to a large news page though improvable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither summary reported a growing Detached* constructor; object and closure counts were flat after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0733-m_bild_de.json
Report SHA-256: e55b103050ab6be3bf9f6c2219170c99020ed43f88d0db39ab473e5dae39ede2
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_bild_de/2026-07-22T17-39-23-916Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_bild_de/2026-07-22T17-39-23-916Z
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.