Manifest position 575 · CrUX rank bucket 1000
https://m.daum.net
Coverage complete
Coverage-complete agentic audit across five representative paths/conditions. Dynamic content and ad inventory may vary by run.
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 | pass | high | Light and dark captures show coordinated surface, text, icon, and illustration changes driven by prefers-color-scheme. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched prefers-reduced-motion: reduce but found a 1,400 ms fade animation still running and no prefers-reduced-motion CSS rules. F01 medium: Motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse measured repeated 14 px metadata at 4.36:1 and blue labels at 3.75:1 against #2c2e33; the high-contrast capture did not expose a distinct higher-contrast theme. F02 medium: Some dark-theme text remains below WCAG contrast minimums. |
implement-natural-interactionsview-transitions | issues | high | The CSS/DOM probe found no view-transition usage while the homepage exposes many dynamic category tabs and separate settings/search routes. F03 low: Major state and route changes are abrupt. |
implement-natural-interactionsscroll-driven-animations | pass | high | The inspected homepage uses native scroll-snap for horizontal carousels and the CSS probe found no scroll-timeline or scroll-linked animation surface requiring main-thread scroll handlers. |
implement-natural-interactionsphysical-gestures | pass | high | Horizontal modules use CSS scroll-snap; the settings editor exposes keyboard-focusable move buttons rather than requiring pointer-only drag gestures. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage layout is 14,746 px tall, while CSS inspection found no scroll-state container behavior or progress affordance and the navigation is not retained in long scrolled states. F04 low: The 14,746 px feed has no scroll-state-aware orientation aid. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored menu, or edge-positioned transient overlay was present in the representative paths; the observed interruption is a centered modal, not an anchored surface. |
provide-guided-navigationdirects-attention | pass | high | Selected homepage/search tabs have visible underline/color state, descriptive labels, and settings changes expose an aria-live region. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Both light and dark first-viewport screenshots show a large centered “다음 커뮤니티 오픈!” app promotion covering headlines and feed content. F05 high: An app-promotion modal obscures the main content on arrival. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The screenshot shows a modal, but the DOM probe found zero dialog, popover, or role=dialog elements, so modal semantics and platform dismissal are absent. F06 medium: The on-load modal is not exposed through a semantic top-layer primitive. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the identified acquisition modal, the portal uses edge-to-edge content sections and a compact header; article and search templates prioritize content rather than decorative application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Article layout reported inner/scroll width 1,184 px and 794 px horizontal overflow; the screenshot clips the headline and lead image far beyond the right edge. F07 high: The representative article template renders as a desktop-width page on a 390 px phone. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS inspection across the dense, reused homepage card/tab surface found no @container rules or container-type declarations. F08 low: Reusable feed components depend on global layout rather than container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The homepage viewport declares user-scalable=no and maximum-scale=1.0; Lighthouse also found overlapping/insufficient safe target space in the main tab strip. F09 high: Zoom and several touch interactions are constrained. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly exposes Daum search and labeled content categories; the search-results page immediately identifies the query and result types. |
support-core-task-successprimary-flow-completion | pass | high | The primary search journey completes from the homepage search model to a populated results template with filters and destination links; settings controls are keyboard-focusable. |
support-core-task-successclear-system-state-and-recovery | pass | high | The low-relevance query still returns labeled, usable results and support links; explicit 404 documents are branded and explain that the page was not found rather than rendering a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 14.4 s, CLS 0.159, and TBT 240 ms (performance 0.46); the independent layout observer measured CLS 0.260. F10 critical: The homepage misses the Core Web Vitals loading and stability bars. |
be-fast-and-stablevisual-stability | issues | high | The layout observer recorded four shifts totaling CLS 0.260, including two roughly 0.09–0.10 shifts after 8.7 s; 94 of 100 images lacked both dimensions. F11 high: Late content causes substantial layout movement. |
be-fast-and-stableefficient-main-thread | issues | high | The trace found two long tasks, longest 153 ms and 114 ms TBT; Lighthouse attributed 5.1 s to main-thread work and 1.5 s to script bootup. F12 medium: Main-thread work delays interactivity. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 195 requests and 3.07 MB; parser-inserted CSS and a synchronous head analytics script were high-priority candidates. Lighthouse estimated 1.23 s render-blocking savings and 1.76 MB cache savings. F13 high: The critical delivery chain is large and render-blocking. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 698 KiB unused JavaScript, 80 KiB unused CSS, and 132 KiB legacy JavaScript; HAR shows 1.24 MB across 22 scripts. F14 high: The page ships substantial unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an unnamed Daum-logo link, ad iframes without titles, and tab roles without required tablist parents; the image audit reported 80 images without alt. F15 high: Several controls and embedded frames lack complete accessible semantics. |
be-inclusivesufficient-contrast | issues | high | Lighthouse identified repeated 14 px metadata at 4.36:1 and blue labels at 3.75:1, both below 4.5:1. F16 medium: Text contrast fails in dark mode. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reported multiple role=tab links whose required role=tablist parent is missing. Native focus was visible, but incomplete relationships impair assistive navigation. F17 medium: ARIA tab structure is incomplete. |
be-inclusivelegible-text | issues | high | At 390 px, the 1,184 px article canvas clips the headline, metadata, and image; users must pan horizontally. F18 high: The article cannot be read comfortably at the audited phone width. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport because user-scalable=no disables zoom; article layout has 794 px overflow at a 390 px visual viewport. F19 high: The homepage prevents zoom and the article fails mobile reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse console evidence and HAR both recorded a 404 for noimg_224_150.gif. F20 low: A shipped fallback image returns 404. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 94/100 images without both dimensions; Lighthouse showed thumbnails declared width="100%" with a 0.57 displayed ratio versus 1.80 intrinsic ratio. F21 medium: Image markup is frequently unsized and sometimes uses incorrect aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found an unload listener, deprecated Topics API usage, BFCache blockers, broken/missing source maps, and inspector issues. F22 medium: Deprecated APIs and platform hygiene issues remain. |
be-discoverabletitle-and-description | issues | high | The article recon returned a descriptive title but an empty meta description, while the homepage had both. F23 medium: The article has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Recon found app/search controls with href="javascript:;" and category tabs with href="#none"; these are neither semantic buttons nor crawlable destinations. F24 medium: Many navigation controls are implemented as non-crawlable links. |
be-discoverablecanonical-and-indexing-signals | issues | high | The homepage probe found no canonical URL; both /robots.txt and /sitemap.xml returned branded 404 documents. F25 medium: Homepage indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage has four Open Graph tags but zero JSON-LD blocks; the article template does provide DiscussionForumPosting JSON-LD and rich OG tags. F26 low: The portal homepage lacks structured WebSite metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence shows no CSP or X-Content-Type-Options. Cookie evidence found four non-Secure cookies and all six with SameSite=None. F27 high: Transport is HTTPS, but CSP and cookie protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 20 third-party origins and known DoubleClick/Google ad trackers; HAR recorded 190 third-party requests and 2.66 MB attributed outside the exact m.daum.net origin. F28 high: The homepage has a broad tracking and advertising footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission request was observed on load and the service-worker/permission probe found no permission-triggering resources. Authentication is an external optional journey, not required for homepage search/content use. |
be-private-and-securedefensive-browser-policies | issues | high | The main response has HSTS and X-Frame-Options but lacks CSP, Referrer-Policy, Permissions-Policy, and X-Content-Type-Options. F29 medium: Several browser-enforced defenses are absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 7% raw/rendered content overlap; the no-JS screenshot preserves header chrome but leaves the feed blank although raw HTML is 2.5 MB. F30 high: Most homepage content disappears without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The acquisition modal remains within the mobile viewport with a visible close control; search, settings controls, and dynamic category surfaces rendered stable actionable states. |
be-resilientoffline-and-installable | not-applicable | high | This current-events/search portal depends on live, changing network data; no offline/installability intent is declared, so an offline PWA is not required for the audited public content task. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested low-relevance search remained useful, and missing robots/sitemap endpoints returned a branded page-not-found document with explanatory text instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | The DOM correctly declares lang="ko", while CSS inspection found no logical inline/block properties across the representative homepage styles. F31 low: Language is declared, but layout CSS is not writing-mode resilient. |
be-internationalisedlocale-aware-data | pass | high | The Korean locale is declared and visible dates, temperatures, counts, and Korean date notation are consistently localized across homepage, search, and article templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, recurring-event, cross-time-zone, or user-entered date/time flow appears in the representative portal, search, article, or settings paths. |
be-trustworthyno-dark-patterns | issues | high | The promotion appears immediately above the portal content and makes the app CTA dominant; dismissal exists but the interruption precedes any expressed intent. F32 medium: The app promotion uses a nagging, content-blocking acquisition pattern. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited first-party form is unconstrained search with no invalid state; no checkout, signup, or required-field form exists on the representative paths. |
be-trustworthytrustworthy-input-assistance | pass | high | The primary field uses native input type=search and presents explicit clear/search controls; address, payment, and credential autocomplete tokens are not relevant to this search-only form. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, or first-party account-management flow is part of the audited public portal paths; optional login redirects to a separate account host. |
be-sustainableoptimised-assets | issues | high | Image audit found 79 below-fold images without lazy loading, 31 oversized images, 70 without srcset, and 27 legacy-format images; Lighthouse estimated 422 KiB image savings. F33 high: Image delivery wastes bytes and misses responsive optimization. |
be-sustainableno-wasteful-work | issues | high | The page performs 195 requests, including 20 ad API requests and 15 analytics-origin requests, while Lighthouse reports 5.1 s of main-thread work. F34 medium: Substantial advertising and feed work runs during initial load. |
be-sustainablethird-party-and-media-budget | issues | high | HAR totals 3.07 MB, with 2.66 MB and 190 requests classified outside the exact homepage origin; images and scripts each transfer about 1.25 MB. F35 high: Third-party and media cost is disproportionate in the first load. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transaction capability was found; this emerging check is not imposed on the public news/search portal. |
be-agent-readyon-device-inference | not-applicable | high | No experience in the representative paths calls for local language-model or summarization inference; absence is not a failure for this emerging contextual check. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten representative tab activations, heap self-size rose from 46.27 MB to 58.75 MB (+27%), objects from 55,184 to 88,938, and closures from 39,133 to 59,177. Separate fresh sessions and dynamic feed variance lower certainty, but the retained delta warrants investigation. F36 medium: Repeated category switching retains substantially more heap in the post-interaction snapshot. |
be-memory-efficientbounded-footprint | issues | medium | The baseline heap summary contains 687,161 nodes and 46.27 MB self size before deliberate interaction; the page also renders a 14,746 px feed and ships 22 scripts. F37 medium: The initial JavaScript heap graph is large for a mobile portal entry state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary surfaced Detached* constructors among the largest retained constructors; native node count fell after the repeated-tab run (201,961 to 183,726), providing no direct detached-DOM growth signal. Listener/timer retention was not asserted beyond this evidence. |
Provenance
Canonical report: results/atomic/reports/0575-m_daum_net.json
Report SHA-256: 3849fcc146250d5a62ea9496b5ea5261c5f48e0545e4a6b6d5649112facfc7fd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_daum_net/2026-07-21T16-33-40-575Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_daum_net/2026-07-21T16-33-40-575Z
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.