Manifest position 361 · CrUX rank bucket 1000
https://www.nikkei.com
Coverage complete
Coverage-complete audit of six representative public paths/templates. Excluded: subscriber checkout/cancellation and post-login account states because credentials/purchase authorization were unavailable; no claims are made about those deeper authenticated states.
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 | The dark-emulated screenshot is visually identical to the light page; the probe reports colorScheme "normal", body text rgb(51,51,51), and no color-scheme media rules. F-respect-user-preferences-respects-color-scheme medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Preference probe under reduce reported zero active animations; screenshots showed no auto-advance. |
respect-user-preferencesrespects-contrast | issues | high | The preference CSS probe found no prefers-contrast or forced-colors rules, and Lighthouse failed its color-contrast audit. F-respect-user-preferences-respects-contrast medium: Contrast preferences are not explicitly supported and ordinary contrast defects remain. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no authored view-transition rules while the representative navigation is an MPA with page-to-page route changes. F-implement-natural-interactions-view-transitions low: Cross-document navigation swaps are abrupt. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS/runtime probe found no authored animation-timeline and observed no scroll-linked motion, so no main-thread scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile evidence showed native document scrolling and standard controls without custom pointer-driven gestures fighting the platform. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop and mobile captures show a stable, consistent global navigation hierarchy and section state rather than disorienting chrome changes. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned menu requiring anchored positioning was present in the exercised reader paths. |
provide-guided-navigationdirects-attention | pass | high | Skip link, strong active navigation styling, descriptive headlines and clear section tabs direct attention across home/listing/search. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a large consent panel over the lead story; on mobile it covers roughly the lower third of the first viewport. F-maximize-content-reduce-noise-no-intrusive-interruptions high: A consent prompt obscures primary news content on initial load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found no dialog, role=dialog, or popover while the screenshot shows modal-like overlay content delivered through a third-party iframe. F-maximize-content-reduce-noise-semantic-dismissible-primitives medium: The consent overlay is not exposed as a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | pass | high | Aside from the separately reported consent overlay, article/listing templates use restrained borders and prioritize headline/content space. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360px, layout reported scrollWidth=clientWidth=360 and 0px horizontal overflow; the mobile screenshot shows a reflowed single-column layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS capability probe found no authored @container rules despite cards and navigation components appearing in multiple widths. F-adapt-to-the-form-factor-component-level-responsiveness low: Reusable components rely on viewport styling rather than container responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size, and the interaction probe found numerous visible links only 13–23px high. F-adapt-to-the-form-factor-input-modality-aware high: Many interactive targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage immediately identifies Nikkei and presents lead news; listing/search/article pages use explicit headings and recognizable next actions. |
support-core-task-successprimary-flow-completion | pass | high | Home-to-listing/article links are real URLs, search returned a query state, and the subscriber article clearly identifies its access requirement. |
support-core-task-successclear-system-state-and-recovery | pass | high | The paywall clearly states member-only status, and the exercised unknown route presents a specific not-found explanation rather than a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.0s and Speed Index 6.9s; the independent trace measured LCP 2.15s, showing variable but material load risk. F-be-fast-and-stable-good-core-web-vitals high: Lab LCP misses the good Core Web Vitals threshold. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer recorded CLS 0 and no shifts; Lighthouse CLS was 0.014, within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 116ms long task and 66ms TBT; Lighthouse TBT was 35ms, both showing a generally responsive main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 113 requests and 1.65MB transferred; it identified an uncached 66.9KB campaign image and multiple high-priority tracking scripts. F-be-fast-and-stable-efficient-resource-delivery medium: Resource delivery is request-heavy and includes weak cache hygiene. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR attributes 59 requests and 1.34MB, about 81% of transfer, to non-main origins; Lighthouse also reports missing source maps for large first-party JavaScript. F-be-fast-and-stable-trim-unused-and-duplicate-code medium: Third-party code dominates the transferred payload. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name and the DOM probe found multiple visible image-only article links without direct text/ARIA naming; the images audit reported 31 missing alt values, including decorative and potentially meaningful images. F-be-inclusive-names-roles-labels high: Some links lack discernible accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s color-contrast audit failed on the homepage. F-be-inclusive-sufficient-contrast high: Some text does not meet minimum color contrast. |
be-inclusivestructure-and-focus | pass | high | The page has a skip link, headings/landmarks, and the focused skip link showed a 3px solid visible outline. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable Japanese typography, adequate line spacing, and no clipping at the tested sizes. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360px layout has no horizontal overflow, but Lighthouse failed target-size and the probe recorded many controls below 24px high. F-be-inclusive-zoom-reflow-targets-and-media medium: Reflow succeeds, but target sizing remains inadequate. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console; HAR also recorded failed Facebook, ad, tag-manager and ORB-blocked tracking requests. F-follow-best-practices-no-console-errors medium: The page logs browser errors during load. |
follow-best-practicessound-document-and-assets | issues | high | The image probe reports 95 of 100 images without width/height attributes, 35 oversized images, 82 below-fold images not lazy-loaded, and 43 legacy-format assets. F-follow-best-practices-sound-document-and-assets medium: Image markup and delivery have widespread sizing/efficiency defects. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed inspector-issues and valid-source-maps for large first-party JavaScript. F-follow-best-practices-browser-platform-hygiene low: DevTools reports browser-platform hygiene issues. |
be-discoverabletitle-and-description | pass | high | DOM and discoverability evidence confirm a descriptive title and meta description on the public homepage; article rendered title is specific. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors even though the viewport meta and most sampled navigation links use real href values. F-be-discoverable-crawlable-and-mobile-friendly medium: Some links are not crawlable. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, exposes canonical https://www.nikkei.com/, robots links a sitemap, and no accidental global noindex was observed. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage includes WebSite JSON-LD plus Open Graph/Twitter title, description, image and URL metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | The cookie probe found lux_uid without Secure and a 400-day analytics cookie; the response CSP only sets frame-ancestors while a meta CSP allows unsafe-inline and unsafe-eval across a very broad origin list. F-be-private-and-secure-secure-transport-and-headers medium: Cookie and CSP posture has avoidable weaknesses. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 12 third-party origins including Facebook and Google Tag Manager; HAR attributes 59 requests and 1.34MB to non-main origins before consent interaction. F-be-private-and-secure-data-minimisation-and-third-parties high: The homepage has a large tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login redirects to NIKKEI ID and exposes autocomplete="username webauthn" plus passkey/WebAuthn support. |
be-private-and-securedefensive-browser-policies | pass | high | Headers include HSTS, nosniff, frame-ancestors, strict-origin-when-cross-origin and Permissions-Policy; clickjacking protection is present through CSP. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 32% overlap for the representative article; its rendered title and h1 were absent from raw HTML. Homepage overlap was 43%. F-be-resilient-progressive-enhancement high: Article identity and much rendered content are missing from the raw no-JavaScript representation. |
be-resilientresilient-runtime-behaviour | pass | high | Representative home/listing/article/search pages rendered stable controls; no clipped menu was observed, and the consent panel remains within the viewport. |
be-resilientoffline-and-installable | not-applicable | high | Nikkei is a live news/market service rather than an install-focused app; offline installability was judged out of scope, while progressive enhancement and failure handling were still tested. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown route renders a clear Japanese not-found explanation and preserves global navigation for recovery. |
be-internationalisedlang-dir-and-logical-properties | pass | high | html lang is ja; Japanese uses default LTR direction, and CSS probe found substantial logical-property use alongside physical declarations. |
be-internationalisedlocale-aware-data | pass | high | Rendered market values and Japanese date/time labels are locale-appropriate; machine-readable time elements accompany visible labels. |
be-internationalisedtime-zone-correctness | pass | high | Sampled time elements use UTC Z or explicit +09:00 offsets, avoiding ambiguous stored timestamps. |
be-trustworthyno-dark-patterns | pass | high | Consent presents equally prominent Reject and Agree actions with a details link; subscriber-only content is marked with lock icons before navigation. |
be-trustworthyhumane-error-handling | pass | high | Login uses native email/password input types and the exercised 404 state explains the problem without blaming the user. |
be-trustworthytrustworthy-input-assistance | pass | high | Login fields provide username webauthn and current-password autocomplete tokens; search is correctly typed as search. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Login clearly redirects to NIKKEI ID, supports WebAuthn/passkeys, and subscriber-only article access is stated before content continuation. |
be-sustainableoptimised-assets | issues | high | The image audit found 35 oversized images, 43 legacy-format images and 6 without responsive sources. F-be-sustainable-optimised-assets medium: Image assets are frequently oversized or delivered in legacy formats. |
be-sustainableno-wasteful-work | issues | high | The HAR recorded 59 third-party requests while Lighthouse reported forced reflow and the page loaded multiple analytics/tracking integrations. F-be-sustainable-no-wasteful-work medium: Non-content background integrations perform substantial work on initial load. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party origins account for 1.34MB of 1.65MB total transferred; the CMP alone transferred about 500KB across its origins. F-be-sustainable-third-party-and-media-budget high: Third-party transfer is disproportionate for a text-first news homepage. |
be-agent-readystructured-agent-capabilities | not-applicable | high | robots.txt explicitly blocks major AI agents and directs machine-learning users to licensing, demonstrating a deliberate choice not to expose an agent-facing surface. |
be-agent-readyon-device-inference | not-applicable | high | The publisher explicitly blocks AI-agent use and no user-facing inference task is promised; on-device inference is therefore not applicable to the audited journeys. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After 10 open/close cycles, the heap summary rose from 22.64MB/310,078 nodes to 24.30MB/330,095 nodes (about 7% bytes and 6.5% nodes). Separate browser sessions lower confidence, but constructor counts also rose. F-be-memory-efficient-no-leak-under-repeated-interaction medium: Repeated menu interaction correlates with retained heap growth and needs leak investigation. |
be-memory-efficientbounded-footprint | issues | medium | Baseline heap summary contains 310,078 nodes and 22.64MB self size before deliberate interaction. F-be-memory-efficient-bounded-footprint low: The homepage has a relatively large live heap/DOM footprint for its initial state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary listed Detached* constructors among the largest populations; no direct detached-DOM accumulation signal appeared. |
Provenance
Canonical report: results/atomic/reports/0361-www_nikkei_com.json
Report SHA-256: 0a908d9652197ba3491b78205703d8dc492a55c19f0e873bbff56e5f5cc3b21c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nikkei_com/2026-07-20T05-52-43-612Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nikkei_com/2026-07-20T05-52-43-612Z
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.