Manifest position 142 · CrUX rank bucket 1000
https://www.naver.com
Coverage complete
Coverage-complete audit across homepage, search, news listing and unauthenticated sign-in. Shopping, mail, maps, checkout, authenticated account settings and credentialed completion were excluded because they are separate products or require credentials.
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 a white surface and the probe reports color-scheme normal. F01 medium: Dark preference does not retint the homepage |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found two running 500 ms AutoRolling animations while the media query matched reduce. F02 medium: Auto-rolling motion continues under reduced-motion |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse reported a color-contrast failure; homepage CSS reports color-scheme normal with no forced-color adaptation signal. F03 medium: High-contrast resilience is not established and baseline contrast already fails |
implement-natural-interactionsview-transitions | issues | high | The CSS/DOM probe found no view-transition declarations across a navigation-heavy portal. F04 low: Route and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal was observed on the representative paths, so there is no scroll-linked implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-refresh, draggable or gesture-specific interaction was present in the audited desktop web journeys. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The probe found no scroll timeline/container-query implementation and the 3,608 px homepage has static chrome. F05 low: Long portal pages provide no scroll-state-aware chrome |
provide-guided-navigationanchored-positioning | issues | high | The homepage exposes autocomplete and banner overlays but the CSS probe found no anchor-positioning/container-query usage. F06 low: Transient overlays are manually positioned rather than anchored |
provide-guided-navigationdirects-attention | pass | medium | DOM recon found explicit skip links to search, news, shopping, feed, account and settings, and labelled tab/navigation roles guide movement. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial desktop screenshot shows a Whale update card covering the main promotional and news region. F07 high: Browser promotion obscures primary homepage content on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe counted no dialog, popover or details elements despite visible promotional and autocomplete overlays. F08 medium: Overlay-rich UI does not use semantic dialog/popover primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | Homepage screenshots show multiple promotional banners, a floating update card, dense tabs and side widgets before core news/feed content. F09 medium: Dense chrome and promotions compete with content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360 px the homepage uses a 1,340 CSS-pixel layout; search uses 1,160 px and reports no viewport meta. Screenshots show miniature desktop columns. F10 high: Desktop layouts are scaled down instead of reflowing at narrow widths |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries, while narrow screenshots preserve desktop cards and columns at reduced scale. F11 medium: Components do not adapt at container level |
adapt-to-the-form-factorinput-modality-aware | issues | high | The homepage probe found 51 of 161 visible interactive elements below 24 px in at least one dimension; Lighthouse also failed target-size. F12 medium: Many controls are undersized for touch |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The homepage screenshot gives the search field dominant placement and clearly labelled service destinations. |
support-core-task-successprimary-flow-completion | pass | medium | The primary search journey reached a populated results page for 웹 접근성 with clear result links and 99% no-JS content coverage. |
support-core-task-successclear-system-state-and-recovery | pass | medium | Homepage DOM includes retry/help/close controls for dynamic recommendation states, and the login surface exposes recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured 18.2 s LCP, 4.7 s FCP and performance 0.55; the independent trace measured 6.33 s LCP. F13 critical: Homepage LCP is far outside the good range |
be-fast-and-stablevisual-stability | issues | high | The layout observer measured CLS 0.783, including a 0.724 shift around 6.16 s; 25 images lack dimensions. F14 high: Homepage has severe observed layout shift in a narrow condition |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded two long tasks up to 138 ms; news recorded a 421 ms task and search recorded 204 ms and 237 ms tasks. F15 medium: Long tasks delay rendering on primary templates |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 170 requests and 5.86 MB transferred, including 2.86 MB images and 2.00 MB scripts. F16 high: Homepage delivery is heavy and delays the main content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR records 52 scripts transferring 2.00 MB across 18 origins; Lighthouse performance remains 0.55. F17 medium: JavaScript and third-party delivery dominate the load |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-required-children, image-alt and link-name; the image probe found 39 images without alt and the search input had no programmatic label. F18 high: Accessible names and role relationships fail |
be-inclusivesufficient-contrast | issues | high | Lighthouse explicitly failed the color-contrast audit on the mobile homepage. F19 high: Text contrast fails the accessibility baseline |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order and landmark-one-main; the homepage uses role=main on a div rather than a native main landmark. F20 medium: Landmark and heading structure is inconsistent |
be-inclusivelegible-text | issues | high | The 360/390 px screenshots show entire desktop multi-column layouts shrunk to fit, making body text difficult to read. F21 high: Narrow views render desktop text at miniature scale |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport and target-size; the homepage declares width=1190 and 51 controls are below 24 px. F22 high: Viewport policy and touch targets obstruct zoom/reflow |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console on the mobile homepage. F23 medium: Browser errors occur during load |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse failed image-aspect-ratio; 25 images lack dimensions and 4 are oversized. F24 medium: Image sizing and aspect-ratio hygiene is weak |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three BFCache failure reasons. F25 medium: The homepage is not eligible for reliable BFCache restoration |
be-discoverabletitle-and-description | pass | medium | Homepage probe found title NAVER and a Korean meta description; search has a query-specific title. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | robots.txt disallows all paths except the root, the page emits index,nofollow, has 52 hash-only links, and uses viewport width=1190. F26 high: Homepage crawl and mobile signals conflict with a public portal |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage returned 200, declares canonical https://www.naver.com/, and robots.txt explicitly allows the root. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Homepage has four Open Graph tags; search and news content are descriptive in server HTML. No mismatched entity metadata was observed. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS and DENY framing are present, but CSP and nosniff are missing; 7 cookies were flagged insecure and several use SameSite=None. F27 high: Security headers and cookie flags are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence recorded 18 origins, 17 outside www.naver.com; the HAR transferred 5.86 MB and long-lived 400-day cookies were set. F28 medium: The homepage has a broad third-party/subdomain footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found no passkey text or WebAuthn signal; only password, QR and federated methods were visible. F29 medium: Sign-in does not expose phishing-resistant passkeys |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack CSP, Permissions-Policy and nosniff; Referrer-Policy is unsafe-url. HSTS and X-Frame-Options are present. F30 high: Defensive browser policy is incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 5% raw/rendered word coverage, an empty #root, and a blank crawler screenshot, while search and news retained 99–100%. F31 high: Homepage core content disappears without JavaScript |
be-resilientresilient-runtime-behaviour | pass | medium | Desktop screenshot shows the promotional overlay remains fully visible with an explicit close control; representative pages loaded to stable usable states. |
be-resilientoffline-and-installable | issues | high | The homepage probe found no manifest and no controlling service worker despite the portal behaving as a long-lived app surface. F32 low: App-like portal has no manifest, service worker or offline entry state |
be-resilientnetwork-and-http-failure-states | pass | medium | Homepage DOM exposes 재시도 (retry), help and close controls for failed recommendation states rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | Homepage declares lang=ko and the login flow declares lang=en with a visible language selector; layouts remained ordered in both audited locales. |
be-internationalisedlocale-aware-data | pass | medium | Weather, date, finance and Korean news content are rendered with locale-appropriate Korean formatting; the login route switches to English labels. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative portal, search, news and unauthenticated sign-in states exposed no cross-time-zone scheduling or editable time concepts. |
be-trustworthyno-dark-patterns | issues | high | A Whale promotion spans the top and a second floating update prompt obscures content on initial load. F33 medium: Persistent browser promotion creates a nagging default experience |
be-trustworthyhumane-error-handling | pass | medium | The login DOM contains nine live/alert regions and labels visible fields, providing programmatic channels for validation feedback. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe found empty autocomplete values for the username and password fields. F34 medium: Sign-in fields omit autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The unauthenticated sign-in entry clearly separates password, QR, federated sign-in, recovery and sign-up; no hidden commitment or continuity was present. |
be-sustainableoptimised-assets | issues | high | Of 69 images, 32 use legacy formats, none use AVIF/WebP, 40 lack srcset, 31 below-fold images are not lazy and 4 are oversized. F35 high: Image delivery is not resolution- or format-efficient |
be-sustainableno-wasteful-work | issues | high | The homepage loads 52 scripts and 170 requests across 18 origins before user interaction. F36 medium: Large script/origin footprint performs avoidable background work |
be-sustainablethird-party-and-media-budget | issues | high | The first load transfers 5.86 MB, including 2.86 MB images, and contacts 17 non-www origins. F37 high: Third-party and media budget is disproportionate for a portal entry page |
be-agent-readystructured-agent-capabilities | issues | high | The homepage is a 5%-coverage JS shell and the probe found no structured agent capability; agents must scrape dynamic UI. F38 low: Core homepage capabilities are not exposed in a structured agent-readable form |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative task was part of the representative search, news-listing or sign-in journeys, so on-device inference was not necessary. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | In one session, ten bottom/top scroll cycles increased used JS heap only from 26.08 MB to 26.42 MB and DOM nodes stayed at 914. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap summary was 28.44 MB for the content-rich homepage; same-session metrics reported 914 DOM elements, proportionate to the portal surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | DOM node count stayed exactly 914 across ten repeated scroll cycles, and the heap summary did not surface Detached* constructors among dominant allocations. |
Provenance
Canonical report: results/atomic/reports/0142-www_naver_com.json
Report SHA-256: 76825333fa5d6bebf56a023f998c92e35afd15864b59879a74afbe3377127b7b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_naver_com/2026-07-18T17-32-10-887Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_naver_com/2026-07-18T17-32-10-887Z
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.