Manifest position 105 · CrUX rank bucket 1000
https://de.wikipedia.org
Coverage complete
Atomic coverage complete: 58/58 checks judged across six representative paths. Authenticated editing, account creation, revision history, donation completion and locale variants were not covered because they require credentials, consequential actions, or duplicate templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The prefers-color-scheme: dark screenshot is visually identical to the normal screenshot and the appearance panel shows “Hell” selected; “Automatisch” and “Dunkel” exist but are not the default. F1 medium: The default appearance remains light when the OS requests dark mode. |
respect-user-preferencesrespects-reduced-motion | pass | high | evaluate under prefers-reduced-motion: reduce found no active animations and a media rule forcing animation-duration to 0.01ms, transitions to 0ms and scroll-behavior:auto. |
respect-user-preferencesrespects-contrast | pass | high | forced-colors screenshot retained visible text, controls, selected radios, borders and links; Lighthouse color contrast passed. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS probes found no view-transition rules while the representative site journey uses full-document article navigation. F2 low: Article and route changes are abrupt rather than using cross-document View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scrollytelling, parallax, carousel, or scroll-linked animation exists on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-refresh, draggable carousel, or other gesture-driven control exists on the audited templates. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | scroll probe found dedicated sticky-header and sticky table-of-contents structures and the article exposes persistent orientation/navigation chrome. |
provide-guided-navigationanchored-positioning | issues | high | The overlay probe found eight checkbox-controlled dropdowns, zero popover elements, zero dialogs/details, and relative positioning for the sticky-header table-of-contents dropdown. F3 low: Menus use checkbox-driven, relatively positioned dropdowns rather than anchored popovers with fallback placement. |
provide-guided-navigationdirects-attention | pass | high | screenshots show active-page/tab underlines, clear section headings, table of contents and predictable recovery links after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | initial screenshots across home, article, search and login show core content immediately with no modal, consent wall or interstitial obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The live DOM exposes checkbox toggles for main, appearance, user, language and tools menus but no popover, dialog or details elements. F4 low: Transient menus are implemented with checkbox controls rather than semantic light-dismiss primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | desktop screenshots devote the central, width-limited area to article/content and use restrained utility chrome without advertising. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport the page declares meta viewport width=1120; layout evidence reports a 1120–1430 CSS-pixel viewport and screenshots show desktop columns and very small text scaled into 360px. Lighthouse with a mobile user agent receives the separate Minerva skin, so this specifically affects narrow desktop-UA windows and responsive emulation. F5 high: The desktop skin does not reflow at narrow window widths and instead forces a 1120px layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Lighthouse mobile rendered the separate Minerva presentation with passing viewport and target-size audits; reusable forms and navigation adapt under the mobile user-agent despite the Vector narrow-window defect. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Lighthouse target-size passed and empty login submission visibly focused the first field; screenshots show persistent non-hover controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | home and article screenshots clearly identify Wikipedia, expose search prominently, and place content headings and links before secondary tools. |
support-core-task-successprimary-flow-completion | pass | high | a non-exact search query reached a labelled results page and returned a crawlable article result; direct exact search also resolved to its article. |
support-core-task-successclear-system-state-and-recovery | pass | high | the missing-article state explicitly says the article does not exist and offers prefilled search, help, language search, creation and deletion-recovery routes. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 1.8s, CLS 0 and TBT 10ms on home; trace measured FCP/LCP 676ms and TBT 0ms. |
be-fast-and-stablevisual-stability | pass | high | layout captures measured CLS 0 on article/category and 0.000215 on search; Lighthouse measured CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | trace recorded no long tasks and 0ms total blocking time; Lighthouse main-thread work was 0.7s and TBT 10ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR summary lists multiple Wikimedia images without cache headers; Lighthouse also reports one unsized image, although measured CLS remained 0. F9 low: Several large assets lack useful cache headers and one image lacks dimensions. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 232 KiB unused JavaScript and 99 KiB unused CSS; HAR records 555,475 transferred script bytes across 11 requests, including a 323,285-byte loader response. F8 medium: The homepage ships substantial JavaScript and CSS that Lighthouse identifies as unused. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 0.88 and reported eight aria-hidden-focus failures plus failures for an unlabeled control and a link without a discernible name. F6 high: The homepage accessibility tree contains hidden focusable descendants and unnamed controls/links. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and forced-colors evidence retained legible foreground/background separation. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found tabindex values 1, 2, 3, 7 and 100 on login controls and flagged the navigation checkbox because its referenced label is aria-hidden. F7 medium: The login flow forces a positive tabindex sequence and its mobile menu checkbox has no valid exposed label. |
be-inclusivelegible-text | pass | high | desktop content screenshots show comfortable line length, clear hierarchy and unclipped body text; the separate mobile skin also passed Lighthouse viewport checks. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a requested 360x800 viewport the page declares meta viewport width=1120; layout evidence reports a 1120–1430 CSS-pixel viewport and screenshots show desktop columns and very small text scaled into 360px. Lighthouse with a mobile user agent receives the separate Minerva skin, so this specifically affects narrow desktop-UA windows and responsive emulation. F5 high: The desktop skin does not reflow at narrow window widths and instead forces a 1120px layout. |
follow-best-practicesno-console-errors | issues | high | Lighthouse reports a web app manifest syntax error on auth.wikimedia.org, missing/invalid maps for large first-party JavaScript, inspector cookie issues, and one BFCache prevention reason. F14 low: The login surface logs a manifest parse error, misses source maps and blocks BFCache. |
follow-best-practicessound-document-and-assets | issues | high | The HAR summary lists multiple Wikimedia images without cache headers; Lighthouse also reports one unsized image, although measured CLS remained 0. F9 low: Several large assets lack useful cache headers and one image lacks dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports a web app manifest syntax error on auth.wikimedia.org, missing/invalid maps for large first-party JavaScript, inspector cookie issues, and one BFCache prevention reason. F14 low: The login surface logs a manifest parse error, misses source maps and blocks BFCache. |
be-discoverabletitle-and-description | issues | high | Lighthouse SEO flags meta-description on the homepage; direct homepage and article metadata probes found titles and canonicals but no meta[name=description]. F10 medium: Public homepage and article templates omit meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passed crawlable anchors, robots.txt and viewport; direct DOM links use real href values. |
be-discoverablecanonical-and-indexing-signals | pass | high | homepage and article return HTTP 200 with canonical links; robots allows normal indexing and article metadata has no accidental noindex. Language links expose hreflang values. |
be-discoverablestructured-and-shareable-metadata | issues | high | The Deutschland response provides og:title, og:type and og:image but no Open Graph description and no JSON-LD; homepage probe also reports jsonld: 0. F11 low: Article sharing metadata is incomplete and no structured-data block describes the entity. |
be-private-and-securesecure-transport-and-headers | issues | high | Cookie evidence found six cookies with SameSite=None and dewikimwuser-sessionId without Secure or HttpOnly; Lighthouse separately observed three third-party-cookie uses during central auth/resource requests. The tested identifier was not proven to be an authentication credential. F13 medium: Anonymous-session cookies use SameSite=None broadly and one session identifier is not Secure. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | tracker probe found no known trackers; observed third-party origins were Wikimedia-operated upload/meta/auth services, and secret scanning found no exposed credential. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | no permission prompt appeared on load; login uses autocomplete="username webauthn" and loads Wikimedia passwordless/WebAuthn modules. |
be-private-and-securedefensive-browser-policies | issues | high | Header evidence shows CSP script-src allows unsafe-inline and unsafe-eval across a very broad origin list; no frame-ancestors or X-Frame-Options, Referrer-Policy, or Permissions-Policy was present. HSTS and nosniff were present. F12 high: Browser-enforced defenses are weakened by a broad CSP and absent anti-framing/referrer/permissions policies. |
be-resilientprogressive-enhancement | pass | high | discoverability found 98% of homepage rendered content in raw HTML, no JS shell, and title/H1 preserved without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | representative menu/article/search states loaded without clipping-related dead ends or uncaught errors on primary content pages; DOM remains server-rendered and conventional. |
be-resilientoffline-and-installable | not-applicable | high | The audited surface is a public encyclopedia/content site rather than an installed app; offline installability is contextual and not required for the core read/search task. |
be-resilientnetwork-and-http-failure-states | pass | high | the exercised missing-page route gives an explicit diagnosis and multiple actionable recovery choices rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | html is lang=de and dir=ltr; probe found hreflang markers across German and English Wikimedia destinations and logical inline computed spacing. |
be-internationalisedlocale-aware-data | pass | medium | homepage renders the locale-correct “18. Juli”; loaded modules include CLDR and MediaWiki DateFormatter, and language selection is extensive. |
be-internationalisedtime-zone-correctness | not-applicable | high | The selected read/search/login surfaces contain no scheduling, recurring events, user-entered times, or timezone-sensitive transaction to judge. |
be-trustworthyno-dark-patterns | pass | high | screenshots show no ads, forced consent, confirmshaming, hidden pricing or nagging continuity; donation/account choices are plainly labelled and optional. |
be-trustworthyhumane-error-handling | issues | high | After activating Anmelden with both fields empty, the captured state only focuses the username field; there is no required marker, inline error text, or visible summary, and the DOM probe reports required=false and no aria-invalid. F15 medium: Submitting the empty login form gives focus but no visible or announced required-field explanation. |
be-trustworthytrustworthy-input-assistance | pass | high | login inputs have explicit labels and autocomplete="username webauthn" / "current-password"; focus is visible. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or cancellation flow exists; login was covered, but sensitive authenticated account actions require credentials and were outside this anonymous audit. |
be-sustainableoptimised-assets | pass | high | homepage transfer is 820,804 bytes total with 192,048 image bytes; thumbnails are sized Wikimedia derivatives and no video/font payload dominates. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimates 232 KiB unused JavaScript and 99 KiB unused CSS; HAR records 555,475 transferred script bytes across 11 requests, including a 323,285-byte loader response. F8 medium: The homepage ships substantial JavaScript and CSS that Lighthouse identifies as unused. |
be-sustainablethird-party-and-media-budget | pass | high | no known tracker, font, audio or video request was observed; third-party bytes are Wikimedia-operated image/meta/auth services and trace shows no continuing main-thread work. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Wikipedia exposes content and conventional APIs, but the emerging WebMCP/agent-action surface is not part of this read/search site journey; absence is an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing summarisation or language-model feature is offered on these templates, so on-device inference has no applicable feature to replace. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | after 10 main-menu open/close cycles, native node count changed by only +8 and closures by +1; the 2.0MB self-size increase was almost entirely strings and does not establish unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | high | baseline heap was 232,322 nodes and 16.8MB self size for a 1,269-element content homepage, proportionate to the page purpose. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | before/after summaries show stable native nodes (115,027 to 115,035), closures (7,946 to 7,947) and OoUiWidget count (16 to 16), with no Detached* constructor among top retained types. |
Provenance
Canonical report: results/atomic/reports/0105-de_wikipedia_org.json
Report SHA-256: 9d65fb44d6f30bab5f44a16ce7400c6d82773a1d60b004eeec0305611441ab3f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/de_wikipedia_org/2026-07-18T11-13-50-055Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/de_wikipedia_org/2026-07-18T11-13-50-055Z
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.