Manifest position 362 · CrUX rank bucket 1000
https://www.nikkansports.com
Coverage complete
Coverage-complete report-mode audit of four representative public MPA templates.
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-mode screenshot is visually unchanged from the desktop capture; computed styles report color-scheme: normal and a transparent/light surface. F01 high: The site remains light-only when the user requests dark mode. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched reduce; there were no active animations or autoplay media to suppress. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found white #fff text on #9fb0bc at 2.23:1, below 4.5:1; no prefers-contrast/forced-colors adaptation was found. F11 high: Text contrast and preference-adaptive contrast are insufficient. |
implement-natural-interactionsview-transitions | issues | medium | DOM inspection found no view-transition CSS/API evidence, and routes are conventional MPA navigations with no cross-document transition declaration. F05 low: Navigation and state changes use abrupt legacy swaps rather than view transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM and runtime probes found no active animation or scroll-linked motion, so no main-thread scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | high | Representative navigation uses native links and scrolling; no custom pointer gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The page exceeds 6,000 CSS pixels, while DOM/CSS inspection and screenshots show static chrome and no scroll progress or scroll-state treatment. F06 low: Long pages provide no scroll-aware header or progress cue. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or anchored floating-menu interaction was present on the representative public pages. |
provide-guided-navigationdirects-attention | pass | high | Descriptive navigation labels, topic rows, article titles, and breadcrumbs provide explicit destination cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile captures show a dark fixed layer covering the bottom portion of the viewport, with only a small close affordance at the far edge. F03 high: A sticky bottom advertising layer obscures article and listing content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Desktop and mobile captures show a dark fixed layer covering the bottom portion of the viewport, with only a small close affordance at the far edge. F03 high: A sticky bottom advertising layer obscures article and listing content. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport has multiple navigation rows and a busy three-column composition; 394 requests include extensive advertising and recommendation infrastructure. F04 medium: Dense navigation, ads, rankings, job listings, and widgets compete with the news hierarchy. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 device viewport the layout primitive reports no viewport meta, a 980 CSS-pixel layout viewport, and scale 0.367; home, category, article, and search screenshots show tiny desktop text and controls. F02 critical: Canonical pages render a fixed desktop canvas scaled down on phones. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a 360x800 device viewport the layout primitive reports no viewport meta, a 980 CSS-pixel layout viewport, and scale 0.367; home, category, article, and search screenshots show tiny desktop text and controls. F02 critical: Canonical pages render a fixed desktop canvas scaled down on phones. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The platform probe counted 199 visible interactive elements below 24px in at least one dimension; scaling the desktop layout down makes targets still harder to acquire. F13 medium: Many controls are too small for reliable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, category, article, and search pages communicate their news/search purpose with prominent Japanese titles and headlines. |
support-core-task-successprimary-flow-completion | pass | high | The core public flow from headline/listing to article and query URL to search results loaded without an auth wall or dead end. |
support-core-task-successclear-system-state-and-recovery | issues | high | /sitemap.xml returned a 404 document containing a timed AutoJump back to home, which can erase context before users inspect recovery options. F20 medium: The 404 state redirects users instead of offering durable recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.2s, TBT 610ms, Speed Index 12.1s and time-to-interactive 32.7s; the CDP trace observed LCP 16.9s and 898ms total blocking time. F07 high: Loading and interactivity are slow. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.039 desktop/0.044 mobile and Lighthouse CLS was 0.006, all within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured LCP 4.2s, TBT 610ms, Speed Index 12.1s and time-to-interactive 32.7s; the CDP trace observed LCP 16.9s and 898ms total blocking time. F07 high: Loading and interactivity are slow. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 394 requests and 4.34MB transferred, including 110 scripts (2.44MB), parser-blocking legacy scripts, and missing cache headers on major resources. F08 high: The page ships an excessive render and network dependency footprint. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,189KiB unused JavaScript and 176KiB unused CSS, while the HAR attributes 3.43MB to third parties. F09 high: Large amounts of unused CSS and JavaScript are delivered. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt and link-name; the platform probe found unnamed logo/social links and images without alt text. F10 high: Important images and links lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found white #fff text on #9fb0bc at 2.23:1, below 4.5:1; no prefers-contrast/forced-colors adaptation was found. F11 high: Text contrast and preference-adaptive contrast are insufficient. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order; the DOM probe found no main landmark, an empty H1, a second H1, and skipped heading levels. Focus outlines were visible, but structure remains confusing. F12 medium: Heading and landmark structure is inconsistent. |
be-inclusivelegible-text | issues | high | At a 360x800 device viewport the layout primitive reports no viewport meta, a 980 CSS-pixel layout viewport, and scale 0.367; home, category, article, and search screenshots show tiny desktop text and controls. F02 critical: Canonical pages render a fixed desktop canvas scaled down on phones. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360x800 device viewport the layout primitive reports no viewport meta, a 980 CSS-pixel layout viewport, and scale 0.367; home, category, article, and search screenshots show tiny desktop text and controls. The platform probe counted 199 visible interactive elements below 24px in at least one dimension; scaling the desktop layout down makes targets still harder to acquire. F02 critical: Canonical pages render a fixed desktop canvas scaled down on phones. F13 medium: Many controls are too small for reliable touch use. |
follow-best-practicesno-console-errors | issues | high | Lighthouse recorded CORS failures, failed resources, an OpenX JSON parse error, and an uncaught pa.sendEvents TypeError. F14 high: Third-party integrations generate runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 18 images without dimensions, 14 oversized images, 59/59 in legacy formats, 31 below-fold images not natively lazy-loaded, and no responsive sources for 13 relevant images. F15 medium: Image and document asset hygiene is weak. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse recorded CORS failures, failed resources, an OpenX JSON parse error, and an uncaught pa.sendEvents TypeError. F14 high: Third-party integrations generate runtime and network errors. |
be-discoverabletitle-and-description | pass | high | All four templates expose descriptive titles and meta descriptions in rendered DOM. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | At a 360x800 device viewport the layout primitive reports no viewport meta, a 980 CSS-pixel layout viewport, and scale 0.367; home, category, article, and search screenshots show tiny desktop text and controls. F02 critical: Canonical pages render a fixed desktop canvas scaled down on phones. |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical link was present on home, category, article, or search templates; /sitemap.xml returned 404. Raw HTML remained strong at 96% content coverage. F16 medium: Canonical and sitemap indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | pass | high | Pages provide Open Graph metadata; the article template additionally includes JSON-LD matching the visible article. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, Referrer-Policy and Permissions-Policy are missing; 13 of 21 observed cookies lacked Secure and many used SameSite=None. F17 high: Important browser security headers and cookie protections are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 78 third-party origins and 16 known tracker hosts; HAR recorded 314 third-party requests and 3.43MB transferred before user interaction. F18 high: The page has an unusually large tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | Login/account surfaces and extensive Piano scripts are present, but DOM/source recon found no WebAuthn/passkey integration; no permission prompt fired on load. F19 medium: The visible account flow exposes no evidence of phishing-resistant authentication. |
be-private-and-securedefensive-browser-policies | issues | high | HTTPS is used, but CSP, HSTS, nosniff, Referrer-Policy and Permissions-Policy are missing; 13 of 21 observed cookies lacked Secure and many used SameSite=None. F17 high: Important browser security headers and cookie protections are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 96% of rendered content words in raw HTML and no JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | Desktop and mobile captures show a dark fixed layer covering the bottom portion of the viewport, with only a small close affordance at the far edge. F03 high: A sticky bottom advertising layer obscures article and listing content. |
be-resilientoffline-and-installable | not-applicable | high | This public news MPA is content-oriented rather than an app-like workflow; installability/offline app behavior was judged out of scope despite a push manifest. |
be-resilientnetwork-and-http-failure-states | issues | high | /sitemap.xml returned a 404 document containing a timed AutoJump back to home, which can erase context before users inspect recovery options. F20 medium: The 404 state redirects users instead of offering durable recovery. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All sampled templates declare html lang=ja and render in the expected left-to-right Japanese reading context. |
be-internationalisedlocale-aware-data | pass | high | Visible dates and scores are rendered in Japanese conventions on the sampled, deliberately Japanese-localised site. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative pages show publication dates but no cross-time-zone scheduling or recurring-event workflow requiring zone conversion. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, hidden pricing, or forced-continuity flow appeared in the representative public reading/search screenshots. |
be-trustworthyhumane-error-handling | not-applicable | high | The representative search flow has no required-field validation step; no user-data form was submitted. |
be-trustworthytrustworthy-input-assistance | issues | high | The search form works, but its text input has no autocomplete token or explicit aria-label in recon; the UI relies on surrounding presentation. F21 medium: Search input assistance is incomplete. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription cancellation, and authenticated account management require credentials or a purchase and were outside this public, non-destructive audit. |
be-sustainableoptimised-assets | issues | high | The images primitive found 18 images without dimensions, 14 oversized images, 59/59 in legacy formats, 31 below-fold images not natively lazy-loaded, and no responsive sources for 13 relevant images. F15 medium: Image and document asset hygiene is weak. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 1,189KiB unused JavaScript and 176KiB unused CSS, while the HAR attributes 3.43MB to third parties. F09 high: Large amounts of unused CSS and JavaScript are delivered. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 314 requests and 3.43MB; three YouTube thumbnails alone exceed 500KB, while every inspected image uses a legacy format. F22 high: Third-party code and oversized media dominate the page budget. |
be-agent-readystructured-agent-capabilities | issues | high | robots.txt disallows GPTBot, ChatGPT-User, Google-Extended, anthropic-ai and Claude-Web; recon found no WebMCP/agentic tool registration. This is an emerging opportunity, not a conventional SEO failure. F23 low: Content is server-rendered but intentionally unavailable to major AI agents and exposes no structured agent actions. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the sampled news reading/search paths requires on-device inference; its absence is not a failure. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | The baseline heap summary reported 1,049,842 nodes and 52.9MB self size; after ten end-to-end scroll cycles the post summary reported 1,324,198 nodes and 65.4MB. Dynamic ad/feed caching may explain some growth, so leak attribution is medium confidence. F24 medium: Repeated scrolling is associated with substantial retained heap growth. |
be-memory-efficientbounded-footprint | issues | medium | The baseline heap summary reported 1,049,842 nodes and 52.9MB self size; after ten end-to-end scroll cycles the post summary reported 1,324,198 nodes and 65.4MB. Dynamic ad/feed caching may explain some growth, so leak attribution is medium confidence. F24 medium: Repeated scrolling is associated with substantial retained heap growth. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries did not surface Detached* constructors among dominant retained objects; no active animation or media timers appeared in runtime probes. |
Provenance
Canonical report: results/atomic/reports/0362-www_nikkansports_com.json
Report SHA-256: 43b0f532b9ac498ea9f71b6e0ff40bec11b1a5d228c043104883afd86a64dea2
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nikkansports_com/2026-07-20T06-05-49-342Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nikkansports_com/2026-07-20T06-05-49-342Z
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.