Manifest position 253 · CrUX rank bucket 1000

https://m.sports.naver.com

Coverage complete

Coverage-complete audit of four representative public templates plus an invalid-route recovery state. Excludes video playback, comments, prediction submission and Naver identity/account flows because those are separate authenticated/media journeys.

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-condition screenshot remains white and the stylesheet only activates dark variables when an additional html.DARK_THEME class is present. F001 medium: The rendered experience does not follow the system dark preference.
respect-user-preferences `respects-reduced-motion`	issues	high	The reduced-motion probe found Home_animationLiveBadge__qHKcE running with a 1200 ms duration and no reduce override. F002 low: A live badge keeps animating when reduced motion is requested.
respect-user-preferences `respects-contrast`	pass	high	Forced-colors/prefers-contrast screenshot retained visible text, controls, separators and current-state cues across the first viewport.
implement-natural-interactions `view-transitions`	issues	high	Downloaded authored CSS contains no view-transition rules, while navigation is a React-like route-driven experience. F003 low: Route and major state changes do not use View Transitions.
implement-natural-interactions `scroll-driven-animations`	pass	high	No parallax, scroll reveal or other scroll-linked animation was observed; static scrolling therefore avoids a main-thread scroll-animation anti-pattern.
implement-natural-interactions `physical-gestures`	pass	high	The page uses native document/horizontal overflow and overscroll containment; no custom pointer gesture surface was observed in the representative flows.
provide-guided-navigation `scroll-state-aware-chrome`	pass	high	After scrolling 1000 px, the primary and secondary nav remained fixed at top 0 and 45 px while the 137 px header scrolled away, preserving useful context.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No applicable surface was present.
provide-guided-navigation `directs-attention`	pass	high	Screenshots show clear blue current-tab text/underline, selected filter pills and chronological scoreboard markers.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	Load screenshots across home, category, scores and article show content immediately with no blocking interstitial.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The opened-menu probe found a fixed DIV role=dialog and no native dialog or popover elements. F004 low: The global menu uses a custom fixed div with role=dialog instead of the platform dialog/popover primitives.
maximize-content-reduce-noise `reduced-chrome`	pass	high	Mobile and desktop screenshots devote the viewport to live scores, headlines and article content with restrained header chrome.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	All three 390 px layout captures reported scrollWidth=clientWidth=390 and zero horizontal overflow; desktop also uses a centred expanded layout.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	Mobile and desktop screenshots adapt, but the downloaded main stylesheet contains no @container rule and computed container-type is normal. F005 low: Responsive adaptation is viewport-only rather than component-aware.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Lighthouse target-size failed, and the DOM probe counted 61 visible controls below 24 px in at least one dimension; keyboard focus itself remained visible. F006 medium: Numerous interactive targets are too small or tightly spaced on mobile.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The first viewport clearly identifies Sports, exposes sport tabs, live scores and headline cards with descriptive labels.
support-core-task-success `primary-flow-completion`	pass	high	A headline link from home opened the full article directly and scoreboard navigation exposed scores without an account wall.
support-core-task-success `clear-system-state-and-recovery`	pass	high	Live/final inning states are labelled; an invalid route shows a branded not-found explanation plus Back and Sports Home recovery actions.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured FCP 4.2 s, LCP 38.9 s, TBT 660 ms and a performance score of 0.40; the raw CDP trace corroborated a 6.71 s LCP. F007 high: The home page loads too slowly under Lighthouse mobile conditions.
be-fast-and-stable `visual-stability`	pass	high	Observed CLS was 0.079 home, 0.079 baseball, 0.064 scoreboard and 0.0008 article, all below the 0.1 good threshold.
be-fast-and-stable `efficient-main-thread`	issues	high	The trace recorded three long tasks, a longest task of 213 ms and 279 ms total blocking time; Lighthouse reported 4.6 s main-thread work and 660 ms TBT. F008 high: Main-thread JavaScript blocks responsiveness during load.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR recorded 127 requests and 5.58 MB transferred, including 3.94 MB of fonts; Lighthouse flagged render blocking, font display, cache lifetime and document latency. F009 high: Critical resource delivery is excessively heavy and delayed.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 278 KiB unused CSS and 1,389 KiB unused JavaScript, plus 100 KiB legacy JavaScript. F010 medium: Large amounts of unused CSS and JavaScript are shipped.
be-inclusive `names-roles-labels`	issues	high	The images primitive reported 99 of 100 sampled images without alt; the later DOM probe still found 10 missing alt attributes and Lighthouse image-alt failed. F011 high: Feed images lack accessible alternatives.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse found ratios as low as 1.96:1 for blue sub-navigation text and 2.52:1 for muted header text against white. F012 high: Navigation and live-score text fail minimum contrast.
be-inclusive `structure-and-focus`	issues	high	The DOM probe found zero main elements across the home template although headings and visible focus were present. F013 medium: The primary content has no main landmark.
be-inclusive `legible-text`	pass	high	Mobile screenshots show readable Korean body/headline text, clear spacing and no clipping or horizontal overflow.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	Rendered metadata is width=device-width, maximum-scale=1, minimum-scale=1, user-scalable=no; Lighthouse meta-viewport failed. F014 high: The viewport explicitly disables pinch zoom.
follow-best-practices `no-console-errors`	pass	high	Lighthouse errors-in-console scored 1 with no reported items.
follow-best-practices `sound-document-and-assets`	issues	high	Lighthouse reported charset missing or too late, while the rendered probe found an injected UTF-8 meta; the image audit found 10 images without dimensions and 66 oversized images. F015 medium: Document and image asset hygiene is inconsistent.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported three BFCache blockers led by Cache-Control: no-store on the main resource and JavaScript fetches. F016 medium: The page is ineligible for the back/forward cache.
be-discoverable `title-and-description`	issues	high	Both the home probe and article probe returned no meta description; Lighthouse SEO failed meta-description. F017 medium: Public templates omit a meta description.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	Visible navigation and content links use real href values, the viewport meta exists, and robots permits the canonical home path.
be-discoverable `canonical-and-indexing-signals`	issues	high	No canonical was present on home or article, /sitemap.xml returned the branded not-found page, robots.txt disallows all paths except home for generic crawlers and explicitly disallows article routes for Yeti. F018 high: Indexing signals are incomplete and crawler policy hides most content.
be-discoverable `structured-and-shareable-metadata`	issues	high	The article exposes og:title, og:image and og:type but no JSON-LD, canonical, meta description or observed og:url. F019 medium: Article metadata lacks structured data and complete sharing fields.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers found no CSP or X-Content-Type-Options; cookie NACT lacked Secure and all five cookies used SameSite=None. F020 high: The HTTPS response lacks core XSS and MIME defenses and sets a non-secure cookie.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Tracker evidence observed 11 third-party origins, including tivan.naver.com, nam.veta.naver.com and nlog.naver.com; HAR attributed 124 requests and 5.58 MB to non-page origins. F021 medium: The initial page has a broad telemetry and third-party-origin footprint.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	Lighthouse found no notification or geolocation prompt on start; no authentication prompt occurs inside the audited public flows.
be-private-and-secure `defensive-browser-policies`	issues	high	The main response lacks frame protection, Permissions-Policy and CSP frame-ancestors, and sends Referrer-Policy: unsafe-url. F022 high: Defensive browser policies are incomplete and referrer leakage is maximised.
be-resilient `progressive-enhancement`	issues	high	Discoverability fetched 3,095 bytes of raw home HTML with zero content text, an empty #root and 0% rendered-word coverage; the crawler screenshot is blank. F023 high: The home and listing experience is an empty JavaScript shell for non-JS clients.
be-resilient `resilient-runtime-behaviour`	pass	high	The global menu exposes expanded state and a fixed dialog that remains inside the mobile viewport; score/list/article states rendered without cut-off overlays.
be-resilient `offline-and-installable`	not-applicable	high	No applicable surface was present.
be-resilient `network-and-http-failure-states`	pass	high	The invalid-route test rendered an explanatory not-found state with Back and Sports Home recovery controls instead of a blank shell.
be-internationalised `lang-dir-and-logical-properties`	pass	medium	The document declares lang=ko and Korean text and reading order render correctly across mobile and desktop screenshots.
be-internationalised `locale-aware-data`	not-applicable	high	No applicable surface was present.
be-internationalised `time-zone-correctness`	not-applicable	high	No applicable surface was present.
be-trustworthy `no-dark-patterns`	pass	high	No consent nag, disguised advertisement, forced continuity, confirmshaming or hidden commitment appeared in the public paths.
be-trustworthy `humane-error-handling`	not-applicable	high	No applicable surface was present.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No applicable surface was present.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No applicable surface was present.
be-sustainable `optimised-assets`	issues	high	The image audit found 66 oversized images, 36 without srcset, 15 legacy-format assets and no detected modern-format image. F024 high: Image assets are frequently oversized and lack responsive delivery.
be-sustainable `no-wasteful-work`	issues	high	The image audit found 41 below-fold images without loading=lazy, while the trace recorded repeated long tasks during the observation window. F025 medium: Below-fold feed assets and processing are loaded eagerly.
be-sustainable `third-party-and-media-budget`	issues	high	HAR measured 5.58 MB, of which 3.94 MB was five font requests and 5.58 MB was attributed to 124 cross-origin requests; Lighthouse measured a larger 12,076 KiB lab payload. F026 high: The page weight is disproportionate for a score-and-news entry view.
be-agent-ready `structured-agent-capabilities`	issues	high	The home is a 0%-coverage JS shell; article raw coverage is only 37%, raw title/H1 are absent, and robots.txt blocks Yeti from article paths. F027 medium: Public sports content is not reliably machine-readable for agents and AI crawlers.
be-agent-ready `on-device-inference`	not-applicable	high	No applicable surface was present.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten bottom/top feed scroll cycles, heap grew from 52.70 MB to 53.71 MB (about 1.9%) with stable FiberNode count, not unbounded growth.
be-memory-efficient `bounded-footprint`	pass	high	Baseline heap was 52.70 MB for a long React feed with 913,536 nodes in the V8 snapshot, proportionate though sizeable.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Neither heap summary listed Detached constructors among top retained constructors, and the repeated-scroll delta remained small.

Provenance

Canonical report: results/atomic/reports/0253-m_sports_naver_com.json
Report SHA-256: 1d9a44a9e75d167da9b3f97a41e674987ee7218f2bbaa7f501624a1d15bf4ed1
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_sports_naver_com/2026-07-19T11-45-35-266Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_sports_naver_com/2026-07-19T11-45-35-266Z
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.