Manifest position 582 · CrUX rank bucket 1000
https://www.mlb.com
Coverage complete
Coverage-complete representative audit. Excluded transaction submission, authenticated account interiors, video playback, search (robots-disallowed), and team microsites to avoid side effects and duplicate 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 | Dark emulation left color-scheme normal and body light; screenshot did not retint. F01 medium: The main MLB homepage ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations and no reduced-motion CSS was needed for the settled state. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot retained visible navigation, score text, controls and consent actions; focused skip control had a dual-ring box shadow. |
implement-natural-interactionsview-transitions | issues | high | No view-transition usage was found in rendered source; route changes remain document swaps. F02 low: Route and major state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked reveal interaction was observed on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | Rendered CSS contains scroll-snap and overscroll-behavior, and horizontal score navigation retains native scrolling controls. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | On the long homepage, static promotional/nav/score chrome consumes substantial initial space and no scroll-state query was found. F04 medium: Promotional and navigation chrome displaces the primary homepage content. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-sensitive anchored popover was present in the representative first-load and primary-flow states; the main overlay is a modal consent surface. |
provide-guided-navigationdirects-attention | pass | high | Active section labels, score controls, article hierarchy, and subscription plan toggle provide clear directional and current-state cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Consent overlays obscure roughly one third of multiple mobile first viewports. F03 high: The cookie banner obscures primary content on first visit across key mobile templates. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | The consent implementation exposes DIALOG and role=dialog/aria-modal surfaces with visible close/settings controls. |
maximize-content-reduce-noisereduced-chrome | issues | high | Promotional banner, global nav and score rail delay the lead content on narrow home view. F04 medium: Promotional and navigation chrome displaces the primary homepage content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five tested content templates reported scrollWidth=clientWidth=360, viewport meta present, and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Rendered CSS contained @container/container-type usage and components visibly reorganized into narrow cards/tables. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Visible keyboard focus is present, but Lighthouse target-size failed on the homepage. F05 medium: Some controls and links are too small or too tightly spaced for touch. |
support-core-task-successclear-purpose-and-primary-action | issues | high | Scores/news purpose is clear, but first-visit consent obscures the next useful content/action on primary mobile templates. F03 high: The cookie banner obscures primary content on first visit across key mobile templates. |
support-core-task-successprimary-flow-completion | pass | high | Scores expose preview/tickets/story actions, the article content renders, and subscription pricing/BUY NOW/cancellation terms are visible without dead ends before purchase. |
support-core-task-successclear-system-state-and-recovery | pass | high | The deliberate invalid route renders a clear 404 heading, retry guidance and Customer Support link rather than a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse home LCP 32.1s/FCP 6.7s/TBT 1.73s and article LCP 21.8s; trace LCP 17.6s. F06 critical: Primary pages load far too slowly under Lighthouse mobile conditions. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS remained below 0.1 on all five templates: home 0.077, article 0.040, stats 0.019, standings 0.017, scores 0.001. |
be-fast-and-stableefficient-main-thread | issues | high | Trace found seven long tasks and 649ms TBT; layout observer caught a 1,516ms homepage task. F07 high: Heavy JavaScript blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | 505 requests/15.24MB with multiple parser-inserted VeryHigh styles and large script/image chains. F08 high: The homepage ships an excessive request and byte load before core content settles. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | 128 scripts transferred 7.13MB and Lighthouse reported unused JS/CSS opportunities. F08 high: The homepage ships an excessive request and byte load before core content settles. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found invalid ARIA, unnamed links/images, label-name mismatch and article images without alt. F09 high: Key templates contain broken ARIA relationships and missing image alternatives. |
be-inclusivesufficient-contrast | issues | high | Measured failures include 3.54:1 score records, 2.87:1 signup text and 4.01:1 consent links. F10 medium: Small score, signup, and consent text fails WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Homepage has no h1; article heading/list audits failed; tab panels have prohibited ARIA. F11 medium: Heading and ARIA structure is inconsistent across templates. |
be-inclusivelegible-text | pass | high | Representative mobile screenshots show readable line lengths, unclipped headlines and clear data alignment; no horizontal overflow was measured. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Article restricts user scaling and homepage has undersized targets; mobile layout itself reflows without horizontal overflow. F12 high: The article viewport restricts user scaling. |
follow-best-practicesno-console-errors | issues | high | Console contains login, CORS, MIME, invalid-date and React hydration errors. F13 medium: Homepage and article loads emit application, network, CORS, MIME, and hydration errors. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but 31 images lack dimensions, 70 are oversized and aspect-ratio audit failed. F14 medium: Image dimensions and aspect ratios are unreliable. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Deprecated unload/Topics/Shared Storage APIs, BFCache blockers and inspector issues were reported. F15 medium: Deprecated APIs and BFCache blockers remain in first- and third-party code. |
be-discoverabletitle-and-description | pass | high | All discoverability captures reported title and meta description present in raw HTML; home metadata is descriptive. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Links are real hrefs and robots permits audited routes, but article viewport prevents normal scaling and Lighthouse found non-descriptive link text. F12 high: The article viewport restricts user scaling. |
be-discoverablecanonical-and-indexing-signals | pass | high | Audited routes returned 200, canonical metadata exists, robots permits them, sitemap declarations are published, and en/es hreflang is present. |
be-discoverablestructured-and-shareable-metadata | issues | high | The editorial article has Open Graph metadata but no JSON-LD Article/NewsArticle block. F16 medium: The audited news article has social tags but no structured article data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff/frame protection are present, but CSP and Permissions-Policy are absent and 52 cookies were flagged insecure. F17 high: Security policy and cookie configuration are weak despite HTTPS. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | 80 third-party origins, 17 known tracker hosts, 495 third-party requests and 15.01MB third-party transfer occurred during undecided consent. F18 critical: Tracking and third-party collection begin before meaningful consent and dominate the page. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but the login entry offers email continuation without a passkey option. F19 medium: The entry sign-in experience exposes no passkey option. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and X-Frame-Options exist, but CSP/frame-ancestors via CSP and Permissions-Policy are absent; Referrer-Policy is only no-referrer-when-downgrade. F17 high: Security policy and cookie configuration are weak despite HTTPS. |
be-resilientprogressive-enhancement | pass | high | All five raw responses contain meaningful content and are not JS shells; no-JS coverage ranged 46–80%, including article text and standings/scores data. |
be-resilientresilient-runtime-behaviour | issues | high | The consent overlay blocks content and runtime logs include hydration/date/login failures, reducing robustness. F03 high: The cookie banner obscures primary content on first visit across key mobile templates. F13 medium: Homepage and article loads emit application, network, CORS, MIME, and hydration errors. |
be-resilientoffline-and-installable | not-applicable | high | MLB.com is a live scores/news/streaming service whose core value depends on current network data; no project intent declares the website itself an offline installable app, and a separate official app is promoted. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberate 404 route provides a visible error, retry guidance and Customer Support recovery link. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Spanish lang and hreflang are correct, but CSS inspection found 429 physical-direction rules and only 4 logical-property rules. F20 medium: The localized site relies overwhelmingly on physical-direction CSS. |
be-internationalisedlocale-aware-data | pass | high | The Spanish route localizes navigation and content, preserves explicit date/time labels, and exposes en/es alternates. |
be-internationalisedtime-zone-correctness | pass | high | Game times are explicitly labeled ET rather than presented as ambiguous local times; source data includes named venue time-zone identifiers. |
be-trustworthyno-dark-patterns | issues | high | The first-layer consent panel presents Accept & Continue and settings but no equally direct reject action, while tracker traffic/cookies already occur. F18 critical: Tracking and third-party collection begin before meaningful consent and dominate the page. |
be-trustworthyhumane-error-handling | issues | high | Submitting the empty newsletter form produced no invalid field and no visible/announced form error. F21 medium: The article newsletter form accepts an empty submission without a visible field error. |
be-trustworthytrustworthy-input-assistance | issues | high | Newsletter email controls have an accessible aria-label but no autocomplete token and are not marked required. F21 medium: The article newsletter form accepts an empty submission without a visible field error. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Subscription page clearly shows $94.99/season and $59.99/year, renewal dates, blackout terms, BUY NOW actions and online/email cancellation terms. |
be-sustainableoptimised-assets | issues | high | 70/100 homepage images are oversized and image transfer totals 6.92MB, despite all inspected formats being modern. F22 high: Many images are materially oversized for their rendered slots. |
be-sustainableno-wasteful-work | issues | high | 505 requests, 128 scripts and extensive pre-consent analytics/ad work are disproportionate to first-view content. F18 critical: Tracking and third-party collection begin before meaningful consent and dominate the page. F08 high: The homepage ships an excessive request and byte load before core content settles. |
be-sustainablethird-party-and-media-budget | issues | high | 495 third-party requests and 15.01MB third-party transfer dominate the load; one video is autoplaying muted on home. F18 critical: Tracking and third-party collection begin before meaningful consent and dominate the page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent indicates MLB.com currently wants to expose transactional WebMCP/agentic tools; public content remains available as SSR HTML, so this emerging capability is treated as an opportunity rather than a failure. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited news, scores, stats, subscription or localized surfaces requires on-device language-model or summarizer inference; absence is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 menu open/close cycles, GC-normalized heap changed from 159.7MB/2,578,233 nodes to 163.7MB/2,587,441 nodes; top constructors remained broadly stable, with no clear unbounded interaction leak in this bounded run. |
be-memory-efficientbounded-footprint | issues | high | GC-normalized baseline is 159.7MB self size with 2.58M nodes, disproportionate for a content homepage. F23 high: The homepage has a very large steady-state heap footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached* constructor entered the top retained constructor list after repeated menu interaction; Promise/Map/Set populations remained near baseline. |
Provenance
Canonical report: results/atomic/reports/0582-www_mlb_com.json
Report SHA-256: 89d5e6d8b06a1ce02f2f37960316693f2d0285e816b92fbfd654914e87c2d999
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_mlb_com/2026-07-21T17-39-00-996Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_mlb_com/2026-07-21T17-39-00-996Z
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.