Manifest position 385 · CrUX rank bucket 1000
https://gall.dcinside.com
Coverage complete
Coverage-complete report-mode audit of four representative public templates. Authentication on sign.dcinside.com, posting real content, restricted galleries, and other dcinside subdomains were not covered.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The prefers-color-scheme: dark screenshot remains the same white desktop canvas as the default capture, while the page exposes a separate manual night-mode control. F01 medium: System dark preference does not automatically produce a dark surface. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion evaluate probe reports a running gradient2 animation with a 250 ms duration while matchMedia(prefers-reduced-motion: reduce) is true. F02 medium: Motion continues under reduced-motion preference. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast screenshot preserves visible text, controls, and boundaries in a black/yellow/white system palette. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across home, listing and detail found no view-transition CSS; navigation and carousel state are instant in the captured surfaces. F03 low: State changes use abrupt legacy swaps rather than view transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the representative templates. |
implement-natural-interactionsphysical-gestures | pass | high | Representative templates rely on native scrolling and standard link activation rather than custom pointermove gesture handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile listing/detail captures render desktop-width, very long pages with static header chrome; DOM/CSS inspection found no scroll-state query or progress indicator. F04 medium: Long pages provide little position-aware navigation. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip/popover placement task was present on the representative public paths. |
provide-guided-navigationdirects-attention | pass | high | Gallery titles, current section labels, article title, list/detail links and skip links provide visible orientation between audited paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh-load screenshots on home, listing, detail and composer show no content-obscuring modal or interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Lighthouse inspector-issues failed, while DOM probes counted 63 javascript: links on home and 11 on the listing; these controls are fragile and not naturally crawlable/actionable. F17 medium: Browser inspector issues and legacy patterns remain. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile screenshots show dense boxed navigation, rankings, side modules, and hundreds of small links; the home probe counted 3,257 interactive elements, 907 under 24 px in one dimension. F05 high: Dense chrome and tiny repeated controls compete with core content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport there is no viewport meta. Home renders a 1,101 CSS-pixel layout at scale 0.327; listing/detail render 1,440 CSS pixels at scale 0.25 and report 75 px horizontal overflow. F06 critical: The desktop site is not usable as a true narrow layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a requested 360x800 viewport there is no viewport meta. Home renders a 1,101 CSS-pixel layout at scale 0.327; listing/detail render 1,440 CSS pixels at scale 0.25 and report 75 px horizontal overflow. F06 critical: The desktop site is not usable as a true narrow layout. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home probe counted 907 of 3,257 interactive elements below 24 px in at least one dimension; listing/detail probes counted 227/501 and 271/614 respectively. Lighthouse also failed target-size. F07 high: Touch targets are extensively undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home search/navigation, gallery listing title/write action, and article title/comment actions are visible in first rendered states. |
support-core-task-successprimary-flow-completion | pass | high | The representative browse flow completed from home to gallery listing to article detail, and the public composer opened without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | After activating Register with an empty composer, the evaluate probe found no :invalid controls, no role=alert/error text, and focus remained on an anonymous DIV; the screenshot was visually unchanged. F08 high: Empty composer submission provides no clear, accessible recovery state. |
be-fast-and-stablegood-core-web-vitals | issues | high | The raw-CDP trace recorded FCP/LCP at 5.254 s and loadEventEnd at 7.043 s; Lighthouse corroboration reported a poor performance score and an even slower mobile-path LCP. F09 high: Initial content is slow to become visible. |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0.000006 home, 0.039 listing and 0.006 detail, all within the good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | Trace measured three long tasks, 110.52 ms total blocking, and 130.32 ms longest; Lighthouse corroborated low TBT despite slow paints. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 85 requests and 2.94 MB transferred, including 907 KB CSS and 1.65 MB JS. Eight parser-inserted stylesheets were VeryHigh priority and multiple 100-401 KB CSS/JS files lacked content encoding. F10 high: Critical delivery is burdened by large uncompressed blocking resources. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 425 KiB unused JavaScript and 375 KiB unused CSS; HAR shows 37 scripts and eight stylesheets. F11 high: Large amounts of unused JavaScript and CSS ship on load. |
be-inclusivenames-roles-labels | issues | high | axe found critical button-name/label/link-name failures on home and, on the composer, an unnamed role=textbox editor, unnamed image/link, and multiple unlabeled inputs. F12 high: Core controls and composer fields lack accessible names or labels. |
be-inclusivesufficient-contrast | issues | high | axe reported 1.93:1 white-on-green text and 3.9:1 ranking badges on home, plus 2.84:1 composer placeholder text; Lighthouse reported 42 low-contrast nodes. F13 high: Text contrast fails WCAG AA. |
be-inclusivestructure-and-focus | issues | high | The DOM has an empty H1 and many empty headings; axe reports invalid heading order, content outside landmarks, and skip links whose targets do not exist. F14 medium: Heading, landmark, and skip-link structure is unreliable. |
be-inclusivelegible-text | issues | high | The 360x800 screenshots shrink fixed desktop layouts to 25-33% scale, making labels, metadata, and controls unreadable without zoom. F15 high: Text becomes illegibly small on narrow screens. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a requested 360x800 viewport there is no viewport meta. Home renders a 1,101 CSS-pixel layout at scale 0.327; listing/detail render 1,440 CSS pixels at scale 0.25 and report 75 px horizontal overflow. The home probe counted 907 of 3,257 interactive elements below 24 px in at least one dimension; listing/detail probes counted 227/501 and 271/614 respectively. Lighthouse also failed target-size. F06 critical: The desktop site is not usable as a true narrow layout. F07 high: Touch targets are extensively undersized. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console audit passed with zero items on the loaded site experience. |
follow-best-practicessound-document-and-assets | issues | high | Images audit found all three homepage images lacked explicit dimensions; Lighthouse found two image aspect-ratio failures, while the page otherwise has a valid doctype and UTF-8 charset. F16 medium: Image/document asset hygiene has defects. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse inspector-issues failed, while DOM probes counted 63 javascript: links on home and 11 on the listing; these controls are fragile and not naturally crawlable/actionable. F17 medium: Browser inspector issues and legacy patterns remain. |
be-discoverabletitle-and-description | pass | high | Home, listing and detail have descriptive unique titles; home and detail metadata include descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | At a requested 360x800 viewport there is no viewport meta. Home renders a 1,101 CSS-pixel layout at scale 0.327; listing/detail render 1,440 CSS pixels at scale 0.25 and report 75 px horizontal overflow. F06 critical: The desktop site is not usable as a true narrow layout. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical and robots signals are present and raw HTML is crawlable, but /sitemap.xml returns 404 on a site with roughly 96,000 galleries. F28 low: Indexing infrastructure is incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph/Twitter metadata is present, but the DOM probe found zero JSON-LD blocks on home and the audited article detail, despite clear Organization/WebSite and DiscussionForumPosting entities. F29 low: Entity pages lack structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirms HTTPS but no CSP, HSTS, X-Content-Type-Options, X-Frame-Options/frame-ancestors, Referrer-Policy, or Permissions-Policy. The cookie audit found 20 cookies marked SameSite=None and 19 without Secure, including PHPSESSID without Secure; several analytics cookies persist 400 days. F18 high: Baseline security headers are absent. F19 high: Cookies are not protected with modern transport and SameSite defaults. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture observed 17 third-party origins and five known tracker domains, including Google Analytics, Tag Manager, DoubleClick, and Google ad services; HAR transferred 2.94 MB. F20 high: The page has a broad tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission request occurs on load; authentication is owned by sign.dcinside.com, outside this host audit. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no clickjacking protection, Referrer-Policy, Permissions-Policy, CSP/Trusted Types enforcement, or HSTS; page metadata also declares referrer=unsafe-url. F21 medium: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 100% home and 87% detail rendered content represented in raw server HTML, not JS shells. |
be-resilientresilient-runtime-behaviour | pass | medium | Listing, detail and composer rendered complete server-backed states; observed controls and pages did not blank or lose their visible state during inspection. |
be-resilientoffline-and-installable | issues | high | The linked manifest contains only a legacy gcm_sender_id comment/config and no name, icons, start_url, display, or scope; no offline fallback was exposed. F22 medium: The app-like community has no valid install/offline surface. |
be-resilientnetwork-and-http-failure-states | issues | high | After activating Register with an empty composer, the evaluate probe found no :invalid controls, no role=alert/error text, and focus remained on an anonymous DIV; the screenshot was visually unchanged. F08 high: Empty composer submission provides no clear, accessible recovery state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | DOM reports html lang=ko, but rendered CSS excerpts and legacy templates use extensive left/right/top pixel positioning and no container-query/logical-layout evidence. F23 low: The Korean locale is declared, but layout CSS is dominated by physical positioning. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public community templates are deliberately Korean-only and expose no currency or locale-switching data flow. |
be-internationalisedtime-zone-correctness | not-applicable | high | No cross-time-zone scheduling or event flow exists on the representative templates. |
be-trustworthyno-dark-patterns | pass | high | Fresh-load and composer screenshots show no consent wall, confirmshaming, forced continuity, hidden pricing, or disguised account commitment. |
be-trustworthyhumane-error-handling | issues | high | Empty submission produced no visible error, no native invalid state, no aria-invalid, no alert, and no focus movement to a field. F24 medium: Composer validation does not prevent and recover from mistakes humanely. |
be-trustworthytrustworthy-input-assistance | issues | high | Composer probe shows unlabeled nickname/editor fields and most text inputs have empty autocomplete; axe confirms labels are missing on several inputs. F25 medium: Input assistance is incomplete on core forms. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or same-host account-management flow exists on the representative gall.dcinside.com paths. |
be-sustainableoptimised-assets | issues | high | HAR transferred 2.94 MB for the home page, including 907 KB CSS and 274 KB image resources; Lighthouse found a 503 KB ad image among the largest resources. F26 medium: Resource weight is disproportionate for a mostly text directory page. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 425 KiB unused JavaScript and 375 KiB unused CSS; HAR shows 37 scripts and eight stylesheets. Tracker capture observed 17 third-party origins and five known tracker domains, including Google Analytics, Tag Manager, DoubleClick, and Google ad services; HAR transferred 2.94 MB. F11 high: Large amounts of unused JavaScript and CSS ship on load. F20 high: The page has a broad tracking and third-party footprint. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 37 script requests and 1.65 MB transferred as scripts; tracker evidence lists 17 third-party origins and repeated analytics/tag-manager endpoints. F27 medium: Third-party scripts and analytics consume a large share of the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | robots.txt explicitly blocks GPTBot, ClaudeBot, Google-Extended and other AI agents, demonstrating that agent-facing capability is intentionally out of scope. |
be-agent-readyon-device-inference | not-applicable | high | The directory/forum templates expose no summarisation or inference task and robots policy explicitly opts away from AI-agent access. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten night-mode toggles, retained self-size rose only 44,053 bytes (0.13%) and nodes by 461 versus baseline, with stable major constructor counts. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 34.49 MB self-size and 610,495 nodes for a content-dense page; post-interaction remained 34.53 MB. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries show no Detached* constructor among top populations and stable closures (27,023 to 27,045) after ten toggles. |
Provenance
Canonical report: results/atomic/reports/0385-gall_dcinside_com.json
Report SHA-256: 19dd4d8edceba08550896f0e4c53a435624083d4396333d8fc1d668ce5dbca65
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/gall_dcinside_com/2026-07-20T09-42-23-247Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/gall_dcinside_com/2026-07-20T09-42-23-247Z
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.