Manifest position 677 · CrUX rank bucket 1000
https://m.dcinside.com
Coverage complete
All 58 catalog checks have one conclusive outcome. Five representative surfaces were inspected; authenticated, write/post, comment submission and destructive account actions were not exercised because they require credentials or mutate live community data.
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 theme as the default screenshot; the settings page exposes a separate manual night-mode toggle. F01 medium: Dark preference does not activate the available night theme |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe reported zero active animations under prefers-reduced-motion: reduce. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot retained readable text, controls and boundaries. |
implement-natural-interactionsview-transitions | issues | high | The DOM/CSS probe found zero view-transition usage across the homepage, while gallery navigation performs a full redirect to a different desktop surface. F02 low: Route and state changes use abrupt legacy navigation |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal effect was observed, so there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | issues | high | Rendered DOM includes Swiper and JavaScript-driven menus, while the probe found no scroll-snap or native disclosure primitives. F03 medium: Carousel and disclosure interactions rely on legacy scripted controls |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The 2,456px homepage has no scroll-state query or progress treatment in the DOM/CSS probe. F04 low: Long feeds provide no scroll-state-aware orientation |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned popover was present in the representative unauthenticated surfaces. |
provide-guided-navigationdirects-attention | issues | high | Following a prominent mobile mini-gallery link redirects to a desktop listing rendered as tiny, unreadable content at 390px. F05 high: A primary gallery route breaks mobile visual continuity |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial homepage screenshot and overlay probe show no full-viewport interruption on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The settings DOM contains custom label-based switches and full custom layer popups; the homepage probe found zero dialog, popover, or details elements. F06 medium: Settings and overlays use custom div/label controls instead of semantic primitives |
maximize-content-reduce-noisereduced-chrome | issues | medium | The first mobile viewport contains search, recent-gallery, four primary tabs, ranking controls, four feed tabs, carousel controls and multiple content modules before a stable reading hierarchy emerges. F07 medium: The entry view is dense with competing navigation and feed chrome |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout at 390px reported scrollWidth=clientWidth=390 and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The selected gallery route redirects to gall.dcinside.com and its entire desktop page is shrunk into the 390px capture; the probe found no container-query usage. F08 high: A mobile route falls back to a desktop-width template |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active probe found many 20-38px controls; Lighthouse failed target-size, including 17px-high footer links. Keyboard focus was visible, but touch sizing is not adequate. F09 high: Many mobile controls are below recommended target size |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage first viewport clearly identifies the service and exposes search, gallery navigation and current content. |
support-core-task-successprimary-flow-completion | issues | high | A prominent homepage gallery choice ends on a desktop listing whose content is illegibly scaled at the tested mobile viewport. F10 high: Homepage-to-gallery navigation does not preserve a usable mobile flow |
support-core-task-successclear-system-state-and-recovery | pass | high | The unavailable article state clearly says the page cannot be found and provides Back and Gallery Home actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured 11.0s LCP, 9.4s FCP and 18.0s time to interactive; the independent trace measured 4.11s LCP. Both exceed good-range loading targets. F11 high: Initial loading is slow |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.028, within the good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded only two modest long tasks, 67.7ms maximum and 23ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded seven parser-blocking stylesheets and synchronous parser scripts; six CSS files over 2KB were uncompressed, including 373KB contents.css. F12 high: Render-blocking and uncompressed resources delay content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 787KiB unused CSS and 293KiB unused JavaScript; three separate gtag bundles each transfer about 163-165KB. F13 high: The page ships large amounts of unused CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, frame-title and image-alt; the probe also found one visible unlabeled search input. F14 high: Core controls and content lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured 3.26:1 green ranking text and 2.03-2.14:1 orange tab text where 4.5:1 is required. F15 high: Several text colors fail minimum contrast |
be-inclusivestructure-and-focus | issues | high | Lighthouse found no main landmark and a non-sequential heading order. Focus is visible, but the structural defects impair assistive navigation. F16 medium: Document structure is incomplete and heading order skips levels |
be-inclusivelegible-text | issues | high | The 390px gallery screenshot shows an entire desktop layout compressed into a narrow viewport, making labels and post rows unreadable without zoom. F17 high: Gallery content becomes illegibly small on mobile |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport because maximum-scale is 2 and failed target-size; the DOM confirms the restrictive viewport metadata. F18 high: Zoom is constrained and touch targets are undersized |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 100 images without width/height and Lighthouse enumerated distorted image aspect ratios. F19 medium: Image sizing and aspect-ratio handling are unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported the deprecated Topics API in t1.kakaocdn.net/kas/static/ba.min.js and failed inspector-issues. F20 medium: A third-party script uses a deprecated browser API |
be-discoverabletitle-and-description | pass | high | Rendered DOM contains a descriptive Korean title and meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The raw-vs-rendered check found only 19% content coverage without JavaScript, and the DOM probe counted 944 of 1,162 anchors with empty or javascript-style hrefs. F21 high: Rendered content and links depend heavily on JavaScript |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt is available, but /sitemap.xml returned the site not-found HTML; the mobile canonical points broadly to the desktop homepage instead of preserving the mobile URL relationship. F22 medium: Sitemap/indexing signals are incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph/Twitter metadata exists, but the live probe found zero JSON-LD blocks for the site/organization entity. F23 low: The organization/home entity lacks structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Header inspection found no CSP, HSTS or nosniff; 14 cookies were observed and 14 were flagged insecure, with most lacking Secure and using SameSite=None. F24 high: Transport is HTTPS but defensive headers and cookie attributes are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker inspection found five known tracker domains. HAR attributed 55 of 64 requests and 2.11MB of 2.30MB to non-main origins, including three gtag bundles. F25 high: Tracking and third-party transfer are disproportionate |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login DOM contains code and password fields without autocomplete tokens; no WebAuthn/passkey use was detected. No permission prompt fired on load. F26 medium: Authentication is password-only and lacks modern credential assistance |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no frame protection, Referrer-Policy or Permissions-Policy in addition to missing HSTS/CSP; the page declares an unsafe-url meta referrer policy. F27 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | issues | high | The discoverability primitive found only 19% rendered-content coverage in raw HTML; the crawler screenshot contains placeholders rather than article text. F28 high: Most feed content disappears without JavaScript |
be-resilientresilient-runtime-behaviour | issues | high | The settings DOM uses custom popup layers and JavaScript hrefs, while gallery navigation switches to a desktop template rather than adapting in place. F29 medium: Custom overlays and desktop redirects make runtime behavior brittle |
be-resilientoffline-and-installable | not-applicable | high | This live community/feed service is intrinsically network-dependent; installability/offline app behavior is not part of the observed public intent. |
be-resilientnetwork-and-http-failure-states | pass | medium | Representative screenshots, DOM and active probes directly support this check with no observed divergence. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The audited service is deliberately Korean-language and region-specific; no alternate locale or bidi surface was offered. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public paths did not expose user-selectable locales or locale-sensitive currencies/calendars requiring cross-locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling or cross-time-zone event workflow was present in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Reviewed homepage, settings and login screenshots show no consent wall, disguised ad control, confirmshaming or hidden pricing. |
be-trustworthyhumane-error-handling | issues | high | Login inputs have labels but no required constraints or described error regions in the DOM; custom JavaScript owns submission feedback. F30 medium: The login form does not expose robust native validation semantics |
be-trustworthytrustworthy-input-assistance | issues | high | The login DOM shows code and password inputs with no autocomplete values, preventing reliable credential-manager assistance. F31 medium: Sign-in fields omit autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | pass | high | The observed account entry is clearly labelled, recovery/join links are visible, and login persistence is an explicit checkbox. No checkout/subscription flow was present. |
be-sustainableoptimised-assets | issues | high | The image audit found 17 oversized images, 100 without dimensions and almost no srcset use. F32 medium: Images are not responsively or dimensionally optimized |
be-sustainableno-wasteful-work | issues | high | Three gtag bundles transfer roughly 491KB total; Lighthouse estimated 293KiB unused JS and 787KiB unused CSS. F33 high: Duplicated analytics and unused code create avoidable work |
be-sustainablethird-party-and-media-budget | issues | high | HAR measured 2.11MB third-party transfer out of 2.30MB total and tracker inspection found 12 third-party origins. F34 high: Third-party cost dominates the page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | robots.txt explicitly opts named AI crawlers out, which is strong evidence that agent-facing capabilities are not intended for this site. |
be-agent-readyon-device-inference | not-applicable | high | No agent-facing or on-device inference intent was observed; the site explicitly blocks named AI crawlers in robots.txt. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten menu toggle/scroll cycles, heap self size rose from 25.83MB to 26.05MB (~0.8%) and nodes from 418,426 to 419,747 (~0.3%); no unbounded growth was demonstrated in this bounded test. |
be-memory-efficientbounded-footprint | issues | medium | The heap summary contained about 418k nodes and 25.8MB self size. Repeated menu/scroll interaction grew only ~0.8%, but the baseline object population is substantial. F35 medium: The initial memory footprint is high for a mobile content index |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries showed no Detached* constructor among retained top populations and only negligible bounded growth after repeated interaction. |
Provenance
Canonical report: results/atomic/reports/0677-m_dcinside_com.json
Report SHA-256: 846cb29bc670298ee3dc7ccf6a7f1e9632934acaf6f406aa510c44caf0504841
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_dcinside_com/2026-07-22T08-19-40-534Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_dcinside_com/2026-07-22T08-19-40-534Z
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.