Manifest position 441 · CrUX rank bucket 1000
https://m.naver.com
Coverage complete
Coverage-complete audit of five representative public paths. Excluded: authenticated account/payment flows and individual external news/article templates because they leave the m.naver.com portal template.
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 | The dark-condition screenshot remains light grey/white, while the DOM reports color-scheme: normal. F01 medium: Dark preference leaves the homepage in a light-only palette |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce, the probe found running weather animations (1.5–2.4s) and repeated 1s search-placeholder animations; the video also retains smooth scrolling. F02 high: Reduced-motion preference is ignored |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast screenshot retained visible text, controls and card boundaries; Lighthouse separately identified ordinary contrast defects under the inclusive check. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition rules on the hash-routed multi-panel homepage. F03 low: Route and panel swaps do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal feature was observed; there is no scroll-linked motion to implement. |
implement-natural-interactionsphysical-gestures | issues | high | DOM CSS exposes .flick-container/.flick-panel and user-select suppression, but no scroll-snap/overscroll declarative gesture primitives were observed. F04 medium: Carousel/gesture behavior relies on a custom flick implementation |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The scrolled reduced-motion video shows header/navigation chrome changing position while content remains orientable. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or edge-positioned menu was present in the audited representative states. |
provide-guided-navigationdirects-attention | pass | high | Hash navigation exposes a selected content panel and persistent labeled section tabs in screenshots. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show no modal or interstitial obscuring content; app promotion and advertising remain in-flow. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The homepage contains search suggestion/close layers but the probe found 0 popovers, 0 dialogs and 0 details elements. F05 low: Transient search UI is implemented without native overlay primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile screenshot devotes roughly the top 350px to header/search, whitespace, an app prompt and an advertisement before the first content card. F06 medium: Promotional chrome dominates the first viewport |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout at 390x844 reports scrollWidth=clientWidth=390 and 0px horizontal overflow with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Across 3,156 elements the computed-style probe found zero non-normal container types; layout adaptation appears viewport-only. F07 low: Reusable cards do not expose component-level responsiveness |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused first link computed to outline-style:none; Lighthouse also found 4 target-size failures and the probe found many 20–22px-high links. F08 high: Keyboard focus and target sizing are insufficient |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly exposes Naver search and labeled portal destinations. |
support-core-task-successprimary-flow-completion | pass | high | The search form action produced a complete results page for “web standards” without an account wall or dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid route displays a clear not-found explanation plus Back and Naver Home recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse scored 0.40 with FCP 7.45s, LCP 17.08s and TBT 628ms; the lighter trace still measured LCP 4.45s. CLS was good at about 0.014. F09 high: Cold-load performance misses the Core Web Vitals bar |
be-fast-and-stablevisual-stability | pass | high | Layout measured CLS 0.0135 and Lighthouse measured 0.0143, both in the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded 3 long tasks and 136.5ms TBT; Lighthouse measured 3.85s main-thread work and 628ms TBT. F10 high: Startup scripting blocks the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 109 requests and 5.55MB transferred, including 1.61MB script, 774KB fonts, 2.82MB images and parser-inserted high-priority CSS/script candidates. F11 high: The critical network path is heavy |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 443,572 bytes of unused JavaScript; the largest vendor bundle alone transferred 914KB. F12 medium: A large JavaScript payload is unused on initial load |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 0.72, finding 9 images without alt, 14 links without discernible names and an ARIA required-children failure; the image primitive counted 49 missing alt values. F13 high: Feed media and links lack accessible alternatives |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 5 contrast failures, including blue text at 3.12:1 and 3.62:1 against white where 4.5:1 is required. F14 high: Text contrast fails WCAG minimums |
be-inclusivestructure-and-focus | issues | high | Lighthouse found no main landmark and a skipped heading level; the focus probe found no visible outline on the first focusable link. F15 high: Landmark, heading and focus structure is incomplete |
be-inclusivelegible-text | pass | high | Mobile and search screenshots show readable body sizing, spacing and wrapping without clipping at 390px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The meta viewport sets maximum-scale=1 and user-scalable=no; Lighthouse failed meta-viewport and 4 touch-target checks. F16 high: The viewport prevents user zoom |
follow-best-practicesno-console-errors | issues | high | Lighthouse recorded a 401 resource error from ngage-msg-sender.io.naver.com/api/v1/session/connection. F17 low: A background connection logs a load error |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse found 4 incorrect-aspect-ratio images; the image audit also found 16 images without both dimensions. F18 medium: Several images render with incorrect geometry |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 0.92; no permission prompt, deprecated-API failure or paste prevention was observed. |
be-discoverabletitle-and-description | pass | high | DOM probe found title “NAVER” and a Korean meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The page uses 17 placeholder/# anchors, Lighthouse found 2 non-descriptive links, and robots meta is index,nofollow. F19 high: Homepage links and crawler directives impede discovery |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt allows only / while disallowing all other paths, /sitemap.xml returns 404, the canonical points to www.naver.com, and OG URL uses insecure http://m.naver.com/. F20 medium: Indexing signals are inconsistent and incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | The page has Open Graph metadata but the probe found zero JSON-LD blocks despite representing a WebSite/Organization with search. F21 low: The portal homepage has no structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Two first-party cookies were set without Secure and all six used SameSite=None; CSP only declares frame-ancestors, nosniff is missing, and Referrer-Policy is unsafe-url. F22 high: Cookie and header defaults are weaker than the HTTPS transport |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 17 cross-origin hosts; HAR classified 104 of 109 requests and 5.47MB as cross-origin, including logging, ads and messaging endpoints. F23 medium: The homepage creates a broad background-request footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load; authentication was not required for the public search journey. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include HSTS and frame protections, but Permissions-Policy and nosniff are absent, Referrer-Policy is unsafe-url, and CSP is limited to frame-ancestors. F24 high: Defensive browser policy coverage is incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 6% rendered-word coverage in raw HTML; crawler and rendered screenshots materially differ even though the raw response is large. F25 high: Most homepage content disappears without JavaScript |
be-resilientresilient-runtime-behaviour | pass | high | Home, hash panel, services and search states rendered without clipped overlays or broken shells in captured narrow states. |
be-resilientoffline-and-installable | not-applicable | high | The public portal is a network-dependent content/search site rather than an installable application; no offline product intent was found. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested missing route returns a localized explanation with back/home recovery controls rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Korean document declares html lang="ko" and rendered reading order is left-to-right as expected for this locale. |
be-internationalisedlocale-aware-data | pass | high | Visible weather, market and date/time labels are formatted in Korean conventions on the Korean locale surface. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited Korean portal surfaces did not expose user-entered events or cross-time-zone scheduling. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, forced continuity or disguised primary action appeared on the signed-out paths. |
be-trustworthyhumane-error-handling | not-applicable | high | The primary search form has no invalid state or required user data; there was no applicable validation error flow. |
be-trustworthytrustworthy-input-assistance | pass | high | Search uses type=search and provides a visible custom suggestion/autocomplete experience despite autocomplete="off". |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription and authenticated account-management flows were outside the public, signed-out representative journey. |
be-sustainableoptimised-assets | issues | high | Image audit found 19 oversized images, 25 without srcset, 28 legacy-format images and no modern-format images; HAR transferred 2.82MB of images. F26 high: Image delivery wastes bytes |
be-sustainableno-wasteful-work | issues | high | The page makes 109 requests and runs messaging, logging, ad and feed work before interaction; Lighthouse reports 3.85s main-thread work. F27 medium: Initial load performs disproportionate background work |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributes 5.47MB of 5.55MB to cross-origin hosts, including 774KB fonts, 2.82MB images and 1.61MB scripts. F28 high: Third-party, font and media costs dominate the page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | WebMCP is emerging and this public portal does not declare an agent-facing capability surface; absence is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No product intent for on-device inference was evident in the audited paths; the AI entry point is not enough to require a built-in-model implementation. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten down/up scroll cycles, heap summary grew 5.7% (42.9MB to 45.4MB); this bounded single run does not show unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary was 42.9MB at baseline with about 3,150 live DOM elements, proportionate to a dense portal though relatively large. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary listed Detached* constructors among the largest retained constructors; the modest post-scroll delta provides no direct leak signal. |
Provenance
Canonical report: results/atomic/reports/0441-m_naver_com.json
Report SHA-256: 1fcb43a19441cd9e3d63079cf390c56f8cb86fc4dc76eb547325e04d991e6b91
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_naver_com/2026-07-20T20-58-53-822Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_naver_com/2026-07-20T20-58-53-822Z
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.