Manifest position 408 · CrUX rank bucket 1000
https://www.nytimes.com
Partial after retries
Atomic coverage is exact, but 7 checks are blocked because anti-bot protection prevented article, search, login, validation, recovery and account-flow inspection.
Attempts
3 / 3
Judged checks
51 / 58
Blocked
7
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 identical to the light capture, the page declares meta color-scheme=light, and computed body background remains white. F01 medium: The public news experience is locked to a light palette even when the user requests dark mode. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under prefers-reduced-motion: reduce the media query matched, loaded CSS contained reduced-motion handling, and only two finite 300ms animations remained, both finished. |
respect-user-preferencesrespects-contrast | pass | medium | The prefers-contrast: more screenshot retained readable text, controls, borders, and consent actions; CSS also contained prefers-contrast/forced-colors handling. |
implement-natural-interactionsview-transitions | pass | medium | Loaded homepage and section CSS contains view-transition rules, providing declarative transition support for state/route changes. |
implement-natural-interactionsscroll-driven-animations | pass | medium | Loaded CSS contains animation-timeline/scroll-timeline rules; no evidence of a required scroll effect implemented solely with a scroll listener was found. |
implement-natural-interactionsphysical-gestures | pass | medium | Loaded CSS contains scroll-snap and overscroll-oriented platform styling, and the audited news surfaces did not expose a custom gesture that fought native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | The responsive navigation and live-news chrome remain position-aware across desktop/mobile captures, and loaded CSS contains scroll-timeline/state-related styling. |
provide-guided-navigationanchored-positioning | pass | medium | Loaded CSS contains anchor positioning declarations and the semantic navigation dialog remained attached and usable in captured states. |
provide-guided-navigationdirects-attention | pass | medium | Homepage/section hierarchy, live labels, tabs, headings, and state-aware navigation provide clear visual direction across the representative index surfaces. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile first-load screenshots show the “Manage privacy preferences” panel covering the lower 25% of desktop and most of the 360px viewport before any user action. F02 high: A consent panel obscures a large share of the primary news content on every fresh load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | medium | The main navigation overlay is implemented as a native dialog and the consent interruption provides explicit accept, reject, and manage actions. |
maximize-content-reduce-noisereduced-chrome | pass | medium | After rejecting consent, the desktop capture devotes the primary area to editorial headlines and imagery with restrained navigation chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive measured scrollWidth 627px against clientWidth 360px, producing 267px of horizontal overflow despite a valid viewport meta tag. F03 high: The homepage overflows horizontally at a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The DOM/CSS probe found no @container or container-type signal while the same card/navigation patterns appear across differently sized regions. F04 low: Reusable components expose no container-query adaptation in the loaded homepage or section CSS. |
adapt-to-the-form-factorinput-modality-aware | issues | high | A focused primary news link matched :focus-visible but computed to a transparent 2px outline with no box shadow. Lighthouse also identified nine footer target-size groups. F05 medium: Keyboard focus can be effectively invisible and several mobile targets are too tightly spaced. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The homepage and World page have descriptive titles, prominent editorial headings, clear story links, section navigation, subscribe and login actions. |
support-core-task-successprimary-flow-completion | blocked | high | Article, search, and login journeys were attempted, but NYTimes bot protection returned a robot-block page before the representative flows could be completed. |
support-core-task-successclear-system-state-and-recovery | blocked | high | Search and account recovery/error states could not be exercised because bot protection blocked the routes before the application UI loaded. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 32.1s, FCP 13.4s, TBT 2,800ms and performance 0.26; World measured LCP 29.8s, FCP 8.9s and TBT 1,670ms. F06 critical: Cold-load performance is far outside good user-centric thresholds on both audited templates. |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer recorded CLS 0.253, including a single 0.196 shift around 16.8s; Lighthouse independently measured non-zero CLS. F07 high: The World section shifts substantially after load. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded 13 long tasks, a 516.6ms longest task and 899.6ms TBT; Lighthouse attributed 7.5s to script evaluation and measured 2.8s TBT. F08 high: Heavy script execution blocks the main thread during startup. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR captured 385 requests and 12.5MB transferred, including 35 stylesheets and 239 scripts; parser-inserted high-priority video CSS and font/global styles form a large startup chain. F09 high: The homepage performs an exceptionally large, eager network load with many critical-style candidates. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,244KiB unused JavaScript and 85KiB unused CSS; examples include 143KiB wasted hls.js and 72KiB wasted Lottie code. F10 high: Large amounts of JavaScript and CSS are unused on the initial homepage view. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found seven poster images without alt and a role=feed missing required child roles on the homepage; the World template also fails required ARIA parent/child relationships and list semantics. F11 high: Video posters and composite feeds contain accessibility-tree errors. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse did not report a color-contrast failure on either homepage or World, and normal/high-contrast screenshots remained legible. |
be-inclusivestructure-and-focus | pass | medium | Lighthouse accessibility audits, DOM semantics, focus probe, image audit and screenshots. |
be-inclusivelegible-text | pass | medium | Desktop/mobile screenshots show readable serif headlines, clear sans-serif metadata, comfortable line lengths, and no text clipping on the accessible World template. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse identified nine target-size groups; examples include footer links whose safe clickable diameter is 15–18px, below the 24px audit floor. F12 medium: Footer controls do not provide sufficient touch target size or spacing. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured five homepage errors and three World errors, including a production React hydration error #418, FedCM failures, and repeated 404 resources. F13 medium: Both audited templates emit runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 25 of 29 images without width/height attributes, while the World layout showed a large late shift. F14 medium: Most homepage images omit intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found an unload listener in adslot code, a BFCache failure, missing source maps, and DevTools inspector issues. F15 medium: Deprecated unload handling prevents back/forward cache restoration and large first-party bundles lack valid source maps. |
be-discoverabletitle-and-description | pass | medium | Homepage and World each expose unique descriptive titles and meta descriptions in raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found 28 non-crawlable anchor instances (a.tpl-lbl without href), even though the page otherwise server-renders 98% of content. F16 medium: Some homepage links are rendered as anchors without href values. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage and World returned 200, include canonical and hreflang links, are not accidentally noindexed, and robots.txt advertises multiple sitemaps. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Homepage exposes WebSite and NewsMediaOrganization JSON-LD plus Open Graph metadata; World exposes CollectionPage and NewsMediaOrganization metadata aligned with visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers probe found CSP allowing unsafe-inline and unsafe-eval. Cookie inspection found nyt-gdpr and nyt-geo without Secure and six cookies using SameSite=None. F17 high: Cookie and CSP settings weaken otherwise strong HTTPS transport. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The consent UI names 336 vendors; the tracker probe observed 24 third-party origins and known ad trackers, while the HAR attributed 147 requests and 10.1MB to origins classified as third-party. F18 high: The fresh-load privacy and tracking footprint is disproportionate for reading the front page. |
be-private-and-securein-context-permissions-and-modern-auth | blocked | high | The login route was attempted but bot protection blocked access before authentication methods or permission timing could be inspected. |
be-private-and-securedefensive-browser-policies | issues | high | The headers probe found no Referrer-Policy; Permissions-Policy was present but limited to browsing-topics=(), while HSTS, nosniff, and X-Frame-Options were correctly configured. F19 medium: Referrer policy is not explicitly set and the permissions policy only disables browsing topics. |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures found 98% homepage and 97% World rendered-content coverage in raw HTML, with title, h1 and description available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | The loaded index templates expose semantic dialog navigation, server-rendered core content, and no clipped overlay was observed on the accessible homepage/World states. |
be-resilientoffline-and-installable | not-applicable | high | The audited public news pages are content documents rather than an installed app; offline installability is contextual and not required for this report. |
be-resilientnetwork-and-http-failure-states | blocked | high | Representative search/article routes returned the external anti-bot 403 state; offline and application-owned network-failure handling could not be isolated. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | Both templates declare lang=en, provide 7–9 hreflang variants and visible international language links, and loaded CSS contains logical properties. |
be-internationalisedlocale-aware-data | pass | medium | Visible dates/timestamps use semantic time elements with machine-readable datetime values, and regional/language variants are exposed. |
be-internationalisedtime-zone-correctness | pass | medium | Breaking-news timestamps use absolute ISO datetime values while presenting human-readable relative labels, avoiding ambiguous stored local times. |
be-trustworthyno-dark-patterns | pass | medium | The consent first layer gives Accept all and Reject all equal visual prominence and provides direct policy/management links; subscription pricing is visible in the masthead. |
be-trustworthyhumane-error-handling | blocked | high | The search and login forms were attempted but blocked before invalid-input and validation states could be exercised. |
be-trustworthytrustworthy-input-assistance | blocked | high | The login/account form was blocked before field autocomplete and input-assistance attributes could be inspected. |
be-trustworthysafe-commercial-and-account-flows | blocked | high | The login and subscription/account journey was blocked by anti-bot protection before commitments, cancellation, and reauthentication could be assessed. |
be-sustainableoptimised-assets | issues | high | The image primitive classified all 29 image URLs as legacy-format paths, found 25 missing intrinsic dimensions and one missing responsive source set; delivery may negotiate WebP, but markup remains inconsistent. F20 medium: Image markup does not expose an efficient, stability-friendly asset baseline. |
be-sustainableno-wasteful-work | issues | high | The HAR shows 239 scripts and 7.3MB media transfer, while Lighthouse identifies 1.24MB unused JS and 7.5s script evaluation. F21 high: The initial page performs substantial work unrelated to immediate reading. |
be-sustainablethird-party-and-media-budget | issues | high | Two 1080p video segments account for about 7.3MB; total transferred bytes are 12.5MB and third-party-classified origins account for 10.1MB. F22 high: Autoloaded media and third-party delivery dominate the front-page byte budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The publisher explicitly disallows major AI agents in robots.txt and does not signal an intent to expose agent-facing capabilities; this emerging check is judged out of scope. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing task in the audited news index requires on-device inference, and the publisher does not signal agent/on-device-AI intent. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | After ten attempted menu open/close cycles, the separate post snapshot was only 3.0% larger by self size and closure count declined; this is low-confidence evidence and does not establish unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | low | The baseline heap summary contains 1,956,211 nodes and 120.1MB self size, including 385k native nodes, 554k objects and 113k closures. F23 medium: The homepage has a very large initial JavaScript heap/object population for a news index. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Neither heap summary exposed Detached* constructors among dominant retainers, and closure count fell from 113,647 to 111,889 after the interaction run. |
Provenance
Canonical report: results/atomic/reports/0408-www_nytimes_com.json
Report SHA-256: 95050f883d7c040bd5187bddbfdf536f53d8e45e3267a81ef26688179aafec9a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nytimes_com/2026-07-27T22-16-08-694Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nytimes_com/2026-07-27T22-16-08-694Z
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.