Manifest position 466 · CrUX rank bucket 1000
https://www.fmkorea.com
Coverage complete
Coverage-complete report-mode audit of six representative public surfaces.
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 is visually the same light page as the default capture, and the CSS feature probe found no prefers-color-scheme rules. F01 medium: The public UI is light-only under the user’s dark preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | No active animations were present under prefers-reduced-motion: reduce, so there was no non-essential motion or auto-advance to suppress. |
respect-user-preferencesrespects-contrast | pass | high | System forced colors preserved visible text, controls, boundaries, and the consent dialog. |
implement-natural-interactionsview-transitions | issues | high | Recon found no view-transition CSS and the site uses traditional abrupt MPA navigation. F02 low: Navigation and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The targeted interaction or content type was absent. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The targeted interaction or content type was absent. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Screenshots and CSS inspection show a static dense header and no scroll-state/container-query or progress treatment on long pages. F03 low: Long listing and article pages provide static rather than scroll-state-aware navigation. |
provide-guided-navigationanchored-positioning | not-applicable | high | The targeted interaction or content type was absent. |
provide-guided-navigationdirects-attention | issues | high | Representative MPA surfaces switch abruptly and the probe found no highlight, transition, or scroll-marker treatment. F04 low: Page changes and in-page navigation do not visibly cue where attention moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Homepage, article, and search captures show a centered modal plus full-page scrim before any user action. F05 high: A first-visit consent interstitial obscures every primary content surface. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Recon found four role=dialog DIVs but zero <dialog>, popover, or details elements. F06 medium: The consent experience is implemented as custom role=dialog divs rather than the native dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile captures show multiple utility rows, a large category bar, ads, controls, and shortcut panels around a narrow content column. F07 medium: Dense global chrome competes with primary community content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport the layout reports no viewport meta and an inner width of 1050 CSS pixels; screenshots show tiny, zoomed-out desktop UI. F08 critical: Mobile visitors receive a scaled desktop canvas instead of a responsive layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS feature probe found no @container rules; components retain desktop geometry when embedded in a mobile viewport. F09 low: Reusable navigation, list, and form components do not adapt at component level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The accessibility probe counted 151 rendered interactive targets with a dimension below 24px; login controls are as small as 13x13 and 22px high. F10 high: Many controls and links are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage clearly identifies the community and surfaces popular posts, category navigation, search, and login actions. |
support-core-task-successprimary-flow-completion | pass | high | Public browsing works through crawlable board/article URLs, search returns results, and account login is reachable without a dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 state clearly says the link was not found and provides a prominent route back to the main page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.4s, FCP 3.7s, Speed Index 4.1s, and TTI 7.1s, despite a faster unthrottled trace. F11 high: Mobile lab loading misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.00013 on the homepage and 0 on the article; audited images include dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded one 83ms long task and 33ms TBT; Lighthouse TBT was 64ms, both within a light blocking-work range. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 16 stylesheets and 20 scripts; Lighthouse estimates 1.28s render-blocking savings and 162KiB cache-lifetime savings. F12 medium: The critical resource chain is broad and cache policy leaves savings. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 151KiB unused JavaScript and 21KiB unused CSS; HAR attributes 826KB transferred to scripts. F13 medium: The homepage ships avoidable unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails label, select-name, and iframe-title; probes found icon-only search controls and login fields without robust names in repeated header forms. F14 high: Interactive controls and form fields lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse fails the color-contrast audit and reports links distinguished only by color. F15 high: Text and essential links fail minimum colour contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse fails heading order and main-landmark checks; the DOM probe shows repeated H1/H2 sequences, while focused submit controls have outline none and no box shadow. F16 high: Heading and landmark structure is inconsistent and focus is not consistently visible. |
be-inclusivelegible-text | issues | high | The 360px homepage and login captures show the entire 1050px desktop UI scaled to roughly one-third size. F17 high: Text becomes too small to read comfortably on narrow screens. |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta is present, the mobile canvas remains 1050px wide, and Lighthouse fails target-size. F18 high: The experience fails mobile reflow and target-size expectations. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report the errors-in-console audit among failing audits or exceptions during representative loads. |
follow-best-practicessound-document-and-assets | pass | high | The document has a doctype/UTF-8 metadata, and image evidence found explicit width/height, correct displayed aspect ratios, and alt text on all 20 images. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports two deprecation warnings, six BFCache failure reasons, Inspector issues, legacy JavaScript, and third-party-cookie usage. F19 medium: Deprecated APIs and multiple browser hygiene issues remain. |
be-discoverabletitle-and-description | pass | high | The homepage has a descriptive Korean title and a content-specific meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The viewport meta tag is absent and Lighthouse fails crawlable-anchors; robots also blocks most paths for generic crawlers. F20 high: The page is not mobile-friendly and some links are not crawlable. |
be-discoverablecanonical-and-indexing-signals | issues | high | The canonical URL exists, but /sitemap.xml returns 404; robots permits major routes for selected search bots while blocking most routes for generic and many AI crawlers. F21 medium: Indexing signals are incomplete and inconsistent across crawlers. |
be-discoverablestructured-and-shareable-metadata | issues | medium | Recon found Open Graph metadata but no evidenced JSON-LD entity model for the organization, board, or representative article. F22 low: Public community entities lack structured data coverage. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS/nosniff are present, but CSP is absent; all five observed cookies lack Secure and the auth-like idntm5 cookie lacks HttpOnly. F23 high: Cookie and XSS transport defenses are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 13 cross-origin hosts and Google ad/analytics trackers; the consent dialog says data may be shared with 210 partners. F24 high: The first load has a large advertising and analytics footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login surface exposes user_id/password controls; recon found no WebAuthn/passkey affordance or credential-management flow. No permission prompt fired on load. F25 medium: Authentication is password-only with no evidenced phishing-resistant option. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no clickjacking protection, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors; HSTS max-age is only 3600 seconds. F26 high: Several browser-enforced defenses are missing. |
be-resilientprogressive-enhancement | issues | high | Discoverability comparison found only 24% rendered-token coverage without JavaScript, although the page is not an empty JS shell and title/H1/description survive. F27 medium: Most rendered content is not present in raw HTML. |
be-resilientresilient-runtime-behaviour | pass | high | The observed consent overlay remains within desktop and scaled-mobile viewports, and real-link MPA navigation avoids fragile client state. |
be-resilientoffline-and-installable | not-applicable | high | The targeted interaction or content type was absent. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing route produces a concise 404 explanation and an actionable link home rather than a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The root document declares lang=ko; Korean is left-to-right and no conflicting dir was present on the representative pages. |
be-internationalisedlocale-aware-data | not-applicable | high | The targeted interaction or content type was absent. |
be-internationalisedtime-zone-correctness | not-applicable | high | The targeted interaction or content type was absent. |
be-trustworthyno-dark-patterns | issues | high | The blocking first screen gives prominent “agree” and “manage options” actions but no equally direct reject-all action, while describing processing by 210 partners. F28 high: The consent decision steers users toward acceptance. |
be-trustworthyhumane-error-handling | issues | high | Login probes show no required/aria-invalid/error-announcement attributes on user ID or password controls and no visible inline recovery guidance before submission. F29 medium: Authentication fields have no evidenced native or accessible validation contract. |
be-trustworthytrustworthy-input-assistance | issues | high | Both header and dedicated login forms report empty autocomplete values for user_id and password. F30 medium: Sign-in inputs omit autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The dedicated login surface contains user ID/password and keep-signed-in controls but no passkey or contextual account recovery action beside the form. F31 medium: The observed account entry flow relies only on a password and does not surface modern reauthentication or recovery assistance. |
be-sustainableoptimised-assets | issues | high | Image audit found 14 legacy-format resources and one image without srcset; custom transparent GIF lazy-loading is used instead of native loading. F32 low: Asset delivery still uses legacy placeholders and lacks responsive source selection. |
be-sustainableno-wasteful-work | issues | high | HAR shows 71 cross-origin requests and roughly 1.03MB cross-origin bytes, including ad/analytics scripts before a consent decision. F33 medium: Optional advertising and analytics work dominates the initial payload. |
be-sustainablethird-party-and-media-budget | issues | high | Scripts account for 826KB of 1.05MB transferred; Google Ads and Tag Manager are among the largest origins while first-party document bytes are small. F34 medium: Third-party scripts are disproportionate for a text-led listing page. |
be-agent-readystructured-agent-capabilities | issues | medium | Lighthouse marks WebMCP tool/form checks not applicable; source/recon found no registered agent tools, while robots explicitly permits several user-invoked AI agents. F35 low: The site exposes public content but no structured agent actions. |
be-agent-readyon-device-inference | not-applicable | high | The targeted interaction or content type was absent. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative search focus/input/blur cycles, same-session heap rose only 0.32MB and DOM nodes rose by two; the separate post summary was 23.8MB. This does not establish unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | The post-interaction V8 self-size was 23.8MB and the live DOM had about 6,474 elements, proportionate to a content listing with consent and advertising integrations. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared among the dominant heap constructors, and repeated interaction added only two live DOM nodes; no accumulating animation population was observed. |
Provenance
Canonical report: results/atomic/reports/0466-www_fmkorea_com.json
Report SHA-256: 4ee95d68173e4e8ad25698c601c8027c1efbd6146c41983018c3c06cae87d91d
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fmkorea_com/2026-07-21T00-05-47-705Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_fmkorea_com/2026-07-21T00-05-47-705Z
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.