Manifest position 490 · CrUX rank bucket 1000

https://www.foxnews.com

Coverage complete

Atomic coverage complete across representative homepage, section, article, search, 404, and login-entry surfaces.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The dark-mode screenshot is visually identical to the light screenshot, and computed styles report color-scheme: normal. F01 medium: The site ignores the user’s dark color-scheme preference.
respect-user-preferences `respects-reduced-motion`	pass	high	Reduced-motion emulation matched and getAnimations() returned zero active animations.
respect-user-preferences `respects-contrast`	pass	high	The high-contrast screenshot retained readable navigation, headlines, images, and controls.
implement-natural-interactions `view-transitions`	issues	high	The DOM/CSS probe found no view-transition usage on homepage or article templates; search and route changes swap abruptly. F02 low: Page and state changes do not use View Transitions.
implement-natural-interactions `scroll-driven-animations`	pass	high	No scroll-linked animation was observed or found in the CSS probe, so the page avoids main-thread scroll animation handlers for this use case.
implement-natural-interactions `physical-gestures`	pass	high	The mobile news and search surfaces use ordinary scrolling and large card links without custom pointer-drag behavior that fights platform gestures.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The 49,638 px mobile homepage and 13,694 px article expose static chrome with no scroll progress or scroll-state styles in the CSS feature probe. F03 low: Long news pages provide no position-aware reading or navigation cue.
provide-guided-navigation `anchored-positioning`	pass	high	No tooltip or floating contextual popover requiring edge-aware anchoring was present on the representative paths. Navigation remains in normal flow.
provide-guided-navigation `directs-attention`	pass	high	Selected topic tabs use clear active styling and the search results preserve the query and selected All tab.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	Initial desktop and mobile captures show primary news content immediately with no blocking modal or consent interstitial.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The rendered homepage has zero dialog, popover, and details elements while exposing expandable navigation and search UI. F04 low: Interactive menus and search use custom controls rather than native overlay primitives.
maximize-content-reduce-noise `reduced-chrome`	pass	high	The primary viewport devotes most area to headlines and imagery, while global chrome is compact and paid content is labeled.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	The layout primitive measured scrollWidth 417 px against clientWidth 360 px, producing 57 px horizontal overflow on the core article path. F05 high: The article template overflows horizontally on a 360 px viewport.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The CSS/computed-style probe found no active container-type or @container usage across homepage cards and navigation components reused at different widths. F06 low: Reusable components rely on viewport breakpoints rather than container-aware adaptation.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Lighthouse found eight target-size failures, including footer links only 14 px high with safe clickable spacing below 24 px. F07 medium: Some mobile touch targets are too small or tightly spaced.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Homepage, section, article, and search first viewports clearly identify their purpose and expose headline reading or search as the next action.
support-core-task-success `primary-flow-completion`	pass	high	The user can move from homepage headline to a fully rendered article and can submit a query to receive linked results.
support-core-task-success `clear-system-state-and-recovery`	issues	high	A deliberately unmatched query returned an unrelated January article and no “no results” explanation, query suggestion, or recovery guidance. F08 medium: Search does not present a trustworthy empty-result state.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured FCP 5.7 s, LCP 8.6 s, Speed Index 6.3 s, and Time to Interactive 19.0 s; its performance score was 0.54. F09 high: Mobile load performance misses the Core Web Vitals loading bar.
be-fast-and-stable `visual-stability`	pass	high	Mobile homepage CLS was 0.0031 and article CLS was 0, both with reserved primary media space.
be-fast-and-stable `efficient-main-thread`	issues	high	Lighthouse reported 3.9 s of main-thread work and 1.5 s JavaScript execution; the trace recorded four long tasks and 171 ms total blocking time. F10 medium: Heavy script work blocks the main thread.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR captured 188 requests and 5,188,601 transferred bytes. Lighthouse found eight render-blocking requests with an estimated 1,240 ms saving and 1,524 KiB cache-lifetime savings. F11 high: The critical network path is heavy and includes render-blocking resources.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 545 KiB unused JavaScript and 38 KiB unused CSS; ag.core.js and core-app.js appear more than once in coverage results. F12 high: The homepage ships substantial unused and duplicated client code.
be-inclusive `names-roles-labels`	issues	high	Lighthouse found 12 label-content-name-mismatch failures even though generic button and link naming audits otherwise passed. F13 medium: Visible labels and accessible names disagree on multiple controls.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse color-contrast audit passed, corroborated by readable desktop/mobile captures.
be-inclusive `structure-and-focus`	pass	high	Lighthouse heading-order passed; DOM contains main/nav landmarks and focus probing showed a visible browser outline on primary controls.
be-inclusive `legible-text`	pass	high	Article and listing text use clear hierarchy, comfortable line lengths, and no visible clipping at desktop or mobile sizes.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Lighthouse found eight insufficient touch targets, and the 360 px article layout overflowed by 57 px. F14 medium: Touch reflow quality is reduced by undersized targets and article overflow.
follow-best-practices `no-console-errors`	issues	high	Lighthouse captured “Not signed in with the identity provider” as a console error. F15 low: The homepage logs a browser error during a normal anonymous load.
follow-best-practices `sound-document-and-assets`	pass	high	DOM reports HTML doctype, UTF-8 charset, useful image alt text, and Lighthouse passed image aspect-ratio and resolution audits.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported one deprecated API, missing source maps for a large first-party script, an Inspector issue, and a BFCache blocker. F16 medium: Browser platform hygiene has several avoidable failures.
be-discoverable `title-and-description`	pass	high	Homepage and article have descriptive titles and meta descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	Lighthouse SEO scored 1.0; links are crawlable, viewport metadata is present, robots allows indexing, and link text passed.
be-discoverable `canonical-and-indexing-signals`	pass	high	Both public templates returned 200, expose canonical and hreflang links, allow indexing, and robots.txt points to sitemaps.
be-discoverable `structured-and-shareable-metadata`	pass	high	Homepage has Organization/WebSite/WebPage JSON-LD; article has NewsArticle, ImageObject, VideoObject, author, Open Graph, and accurate visible headline metadata.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers showed no CSP or X-Content-Type-Options. Cookie audit found 17 cookies lacking Secure, many with SameSite=None, while HTTPS and HSTS were present. F17 high: Security headers and cookie attributes are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Network evidence found 30 third-party origins and 186 of 188 requests classified off the main origin, with about 5.1 MB transferred outside www.foxnews.com. F18 high: The anonymous homepage has a broad third-party and analytics footprint.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No notification, geolocation, camera, or microphone prompt appeared on load. The public content paths do not require authentication.
be-private-and-secure `defensive-browser-policies`	issues	high	No CSP, frame-ancestors/X-Frame-Options, Referrer-Policy, or X-Content-Type-Options was present; Permissions-Policy grants client-hint features but does not restrict sensitive capabilities. F19 medium: Browser-enforced defensive policies are incomplete.
be-resilient `progressive-enhancement`	pass	high	Discoverability found 100% homepage and 93% article content coverage without JavaScript, with nonempty server HTML and article H1 present.
be-resilient `resilient-runtime-behaviour`	pass	high	Homepage, section, search, and article rendered usable content across desktop/mobile without cut-off primary menus or blank shells.
be-resilient `offline-and-installable`	not-applicable	high	Not applicable to the audited public news scope.
be-resilient `network-and-http-failure-states`	pass	high	A deliberate invalid URL produced a specific 404 heading, explanation, Go to Home recovery, and current video links.
be-internationalised `lang-dir-and-logical-properties`	pass	high	HTML lang=en is present and hreflang exposes en, es, and x-default variants; no incorrect forced direction was observed.
be-internationalised `locale-aware-data`	pass	high	Article publication is represented by a semantic time element with machine-readable ISO timestamp and human-readable locale form.
be-internationalised `time-zone-correctness`	pass	high	The article time includes EDT in visible text and an explicit -04:00 offset in datetime and JSON-LD.
be-trustworthy `no-dark-patterns`	pass	high	Initial content is available without consent walls; paid content is visibly labeled and public article reading is not forced through login or continuity.
be-trustworthy `humane-error-handling`	pass	high	Search preserves the entered query and provides direct tab/filter and resubmission controls without premature validation blame.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	Not applicable to the audited public news scope.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	Not applicable to the audited public news scope.
be-sustainable `optimised-assets`	issues	high	The image audit found 91 of 100 images without srcset, 94 legacy-format images, and 96 below-fold images without loading=lazy; Lighthouse estimated 613 KiB image-delivery savings. F20 medium: Image delivery is not proportionate for a long listing page.
be-sustainable `no-wasteful-work`	pass	high	Long tasks were finite and no continuously running visible animation was observed under reduced-motion; this check is narrowly passed despite separate resource-budget issues.
be-sustainable `third-party-and-media-budget`	issues	high	HAR measured 5.19 MB total, including 1.94 MB media, 1.77 MB scripts, and 186 third-party requests; two autoplay videos had no controls. F21 high: Background media and third-party code dominate page weight.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	Not applicable to the audited public news scope.
be-agent-ready `on-device-inference`	not-applicable	high	Not applicable to the audited public news scope.
be-memory-efficient `no-leak-under-repeated-interaction`	issues	medium	After ten search open/close cycles, heap self-size rose from 50.46 MB to 60.86 MB and node count from 640,199 to 690,822. Separate-load background variation lowers confidence, but the growth warrants retained-object analysis. F23 medium: Repeated search toggling coincided with substantial retained heap growth.
be-memory-efficient `bounded-footprint`	issues	high	The baseline heap summary contained 640,199 nodes and 50,462,391 self-size bytes for a news listing page. F22 medium: The homepage starts with a large memory footprint.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Neither heap summary listed Detached constructors among the largest retained constructors; closure count changed modestly from 28,047 to 28,550.

Provenance

Canonical report: results/atomic/reports/0490-www_foxnews_com.json
Report SHA-256: f7e6936b7fef55108a696401d5111ac5a9b0ca111973e3a863b3566bcf60f6e4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_foxnews_com/2026-07-21T03-26-40-355Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_foxnews_com/2026-07-21T03-26-40-355Z
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.