Manifest position 935 · CrUX rank bucket 1000
https://comix.to
Coverage complete
Coverage complete. The site rendered in Lighthouse but repeatedly remained blank in raw-CDP fresh sessions, an evidence conflict treated as a serious resilience defect rather than a blocker.
Attempts
2 / 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 light-preference probe matched prefers-color-scheme: light but computed body colors remained rgb(24,26,28) on rgb(212,212,212); the static scan found no prefers-color-scheme rule. F005 medium: The site forces its dark palette even when the OS requests light mode. |
respect-user-preferencesrespects-reduced-motion | issues | high | The static CSS/JS scan found no prefers-reduced-motion handling. The page contains carousels and motion-capable UI in the successful Lighthouse render. F006 medium: No reduced-motion adaptation is implemented in shipped CSS. |
respect-user-preferencesrespects-contrast | issues | high | The static scan found no prefers-contrast or forced-colors rules, and Lighthouse separately found contrast failures in the rendered UI. F007 medium: No high-contrast or forced-colors adaptation is present. |
implement-natural-interactionsview-transitions | issues | high | The shipped application assets contained no startViewTransition usage, despite a route-heavy browse, detail and reader experience. F008 low: Route and state swaps do not use the View Transitions API. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry/exit reveal or other scroll-linked motion was observed; scroll-snap is used for the carousel. |
implement-natural-interactionsphysical-gestures | pass | high | Static asset scan found nine scroll-snap declarations and four overscroll-behavior declarations, providing platform-native carousel/gesture behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The static scan found scroll-snap but no scroll-driven timeline or scroll-state/container-query implementation; the successful screenshot shows a dense scroll surface with fixed top navigation. F009 low: The long listing UI lacks declarative scroll-state-aware navigation treatment. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or edge-positioned transient menu was available in the audited public states. |
provide-guided-navigationdirects-attention | pass | high | The successful Lighthouse screenshot shows a clear top navigation and section hierarchy, while carousel paging controls visually cue horizontal movement. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | The successful first viewport contains an announcement card and content, with no full-screen interstitial or consent wall obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal or disclosure flow appeared on initial load; the failed-load state had no overlay to assess. |
maximize-content-reduce-noisereduced-chrome | pass | high | The successful screenshot gives most of the viewport below a compact header to announcement and comic content, with restrained borders. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, layout measured scrollWidth=clientWidth=360 with zero horizontal overflow and a viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The shipped CSS contained no @container or container-type despite reusable comic-card/carousel components. F010 low: Components rely on global layout rules rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Static CSS scan found seven focus-visible rules and the successful mobile layout exposes compact but distinct controls; Lighthouse did not flag target sizing. |
support-core-task-successclear-purpose-and-primary-action | pass | high | When rendering succeeds, the logo, announcement, Most Recent Popular heading, comic cards and Log In control clearly identify the reading/browsing purpose. |
support-core-task-successprimary-flow-completion | issues | high | Six raw-CDP captures across home, title, chapter and collection stayed at a uniform #181a1c background after 12 seconds; the 12-second probe found 26 nodes, zero links, zero controls and no body text. Lighthouse did render the homepage in a separate run, proving an intermittent/runtime-dependent boot failure rather than intentional emptiness. F001 critical: Fresh browser sessions can remain a blank shell, blocking discovery and reading. |
support-core-task-successclear-system-state-and-recovery | issues | high | The persistent blank captures and content probe show no status text or interactive control after 12 seconds. F002 critical: The failed bootstrap presents no loading, error, retry or recovery state. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.1 seconds (score 0.05), FCP 2.9 seconds and time to interactive 7.2 seconds. F011 high: Largest Contentful Paint is far outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Lighthouse measured CLS 0.032, within the good range; the layout capture observed zero shifts in its blank failure state. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse measured about 100 ms TBT; the raw-CDP trace recorded zero long tasks and zero total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified four very-high-priority parser-inserted stylesheets plus the application script as candidates; Lighthouse estimated 900 ms render-blocking savings and the document itself took about 995 ms. DOM confirms stylesheets are in the head and the main script has no async/defer/module attribute. F012 medium: Render-blocking styles and dependency chains delay useful content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 44 KiB unused CSS and 117 KiB unused JavaScript; HAR transferred 248,355 bytes of scripts before the core UI reliably appeared. F013 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name and label-content-name-mismatch; its accessibility score was 0.87. F014 high: Rendered controls include links without names and visible labels that do not match accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed the color-contrast audit in the rendered homepage. F015 high: Some foreground/background pairs fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order on the rendered homepage; raw-CDP failure states provide no focusable recovery control at all. F016 medium: Heading hierarchy is not sequential. |
be-inclusivelegible-text | pass | high | The successful screenshot uses readable type sizing and short announcement lines; no clipping is visible at the mobile viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The live viewport meta is width=device-width, initial-scale=1, user-scalable=no; Lighthouse failed meta-viewport. F017 high: The viewport explicitly disables user zoom. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no recorded console errors. |
follow-best-practicessound-document-and-assets | pass | high | Raw HTML has HTML5 doctype and UTF-8 charset; images on the successful render preserve plausible card aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three deprecation warnings from /cdn-cgi/challenge-platform/scripts/jsd/main.js, including deprecated Shared Storage, persistent storage and Protected Audience APIs. F018 low: Cloudflare challenge code invokes deprecated browser APIs. |
be-discoverabletitle-and-description | pass | high | Home and representative title pages each returned unique descriptive title and meta description values in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | HTTP status is 200, viewport meta is present, robots.txt is valid, and server data contains real href-style route URLs. |
be-discoverablecanonical-and-indexing-signals | issues | high | Raw homepage and title HTML contain no rel=canonical; /sitemap.xml returns an HTML 404 page. Robots is syntactically valid but includes multiple bot-specific Disallow rules. F019 medium: Public pages omit canonical URLs and expose no sitemap at /sitemap.xml. |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative title HTML has a descriptive title/meta description but no JSON-LD, canonical or hreflang. F020 medium: Comic detail pages lack structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirmed HTTPS but found no CSP, HSTS or X-Content-Type-Options. F021 high: Core security response headers are missing. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker capture found no known trackers, only one third-party origin (Google Fonts), and the HAR recorded just two third-party requests/2,338 bytes. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission request or authentication form was present in the representative public journey; /login returned 404. |
be-private-and-securedefensive-browser-policies | issues | high | No CSP frame-ancestors, X-Frame-Options, Referrer-Policy or Permissions-Policy was present. F022 high: Clickjacking, referrer and permissions defenses are not configured. |
be-resilientprogressive-enhancement | issues | high | Discoverability fetched 393,664 bytes of raw homepage HTML but extracted only 35 text characters and five content tokens; title raw HTML likewise exposed 39 text characters/five tokens. Both crawler screenshots are blank, while data is serialized inside scripts. F003 high: Core content is not available without successful JavaScript execution. |
be-resilientresilient-runtime-behaviour | issues | high | Raw-CDP sessions repeatedly rendered no UI, while Lighthouse rendered the homepage and recorded content. This session-dependent result indicates fragile initialization or bot/challenge interaction. F004 high: Runtime behavior is inconsistent across clean Chrome sessions. |
be-resilientoffline-and-installable | issues | high | The manifest declares standalone display/start_url, but navigator.serviceWorker.getRegistrations() returned an empty list. F023 medium: The install manifest has no active service worker/offline fallback. |
be-resilientnetwork-and-http-failure-states | issues | high | Repeated fresh sessions are direct network/runtime failure-state evidence: no spinner, timeout, error copy, retry or fallback links appear by 12 seconds. F024 high: A failed client load degrades to an unlabelled blank screen. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The audited service presented itself as deliberately English-only and exposed no locale or writing-mode variants. |
be-internationalisedlocale-aware-data | not-applicable | high | No locale-sensitive currency, date input or translated variant was present in the representative public surfaces. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling or user-visible time-zone-sensitive workflow was present. |
be-trustworthyno-dark-patterns | pass | high | The successful first viewport shows no consent wall, disguised advertising, confirmshaming or forced-continuity prompt. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-input form was available in the audited public routes; /login returned 404. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in or sign-up input flow was available in the audited public routes. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or account-management flow was exposed in the representative unauthenticated scope. |
be-sustainableoptimised-assets | issues | high | Lighthouse estimated 671 KiB image-delivery savings on the successfully rendered homepage. F025 medium: Image delivery wastes bytes relative to displayed size. |
be-sustainableno-wasteful-work | pass | high | Trace observed no long tasks/background processing in the capture window, and the HAR contained only 18 requests. |
be-sustainablethird-party-and-media-budget | pass | high | HAR recorded only 2,338 third-party bytes, no media resource category, and no known tracker origins. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional agent tool surface was found; this emerging capability is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model experience was offered, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The raw-CDP sessions exposed no representative UI interaction to repeat because the client remained blank; fabricating one would not test a real flow. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap contained 125,749 nodes and 7,521,500 bytes self size, proportionate to the loaded application shell. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The audited failure state had only 26 live DOM elements, zero animations and no repeatable interaction; the baseline heap showed no evidence of an already-unbounded footprint. |
Provenance
Canonical report: results/atomic/reports/0935-comix_to.json
Report SHA-256: 6bd168106318e386d37d1c23ea9b8f0d0d2af73ab5f08bf6ed88ba971115c47a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/comix_to/2026-07-27T05-38-32-152Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/comix_to/2026-07-27T05-38-32-152Z
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.