Manifest position 533 · CrUX rank bucket 1000
https://manhwaread.com
Coverage complete
Atomic coverage complete across 58 checks and six representative paths.
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 | Light- and dark-preference screenshots are byte-identical (1,088,820 bytes) and both render the hard-coded dark theme; the page offers only a manual theme toggle. F01 medium: The visual theme does not follow the system color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulation probe matched reduced motion and found zero running animations; no auto-advance or essential motion was observed. |
respect-user-preferencesrespects-contrast | pass | high | Controls and text remained visible; primary targets retained native focus outlines and Lighthouse accessibility/contrast audits passed. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found View Transitions supported by the browser but no view-transition CSS usage; navigation is conventional abrupt document replacement. F02 medium: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No authored scroll-linked animation or parallax effect exists; there is no scroll event animation implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | The chapter reader uses native vertical scrolling and fixed labelled Previous/Next controls; no custom pointermove gesture layer was found. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The chapter mobile layout is 69,269px tall, while the screenshot shows only a fixed chapter bar; the CSS probe found no scroll-state query or declarative progress treatment. F03 medium: The 69,269px chapter reader gives no meaningful scroll progress. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or viewport-edge popover is part of the representative core paths; authentication uses modal dialogs instead. |
provide-guided-navigationdirects-attention | pass | high | Active Home styling, clear Read First/Read Last actions, chapter title, back control and labelled Previous/Next controls preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The 360x800 search screenshot shows a large sexual ad fixed over the Artists/Authors controls, interrupting the core search task. F04 high: An explicit ad obscures the advanced search controls on mobile. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found four div role=dialog containers and zero <dialog> or popover elements; dismissal and modality are hand-wired. F05 medium: Authentication overlays are custom div dialogs instead of native dialog elements. |
maximize-content-reduce-noisereduced-chrome | pass | high | The chapter template devotes nearly the entire viewport to the comic, with compact top and translucent bottom navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Home, listing, detail and chapter all reported scrollWidth=clientWidth=360 and zero horizontal overflow with viewport metadata present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS platform probe found no @container usage, even though cards are reused in materially different-width carousels and grids. F06 low: Reusable cards and controls rely on viewport styling rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active probe measured the Index dropdown toggle at 24x24 CSS px and the search input/button with outline-style none; other primary targets were 40-48px. F07 medium: Some controls have undersized targets or suppress visible focus styling. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The search first viewport contains filters only, while the DOM text enumerates 1,643 tags before results; no result or direct path to results appears in the mobile screenshot. F08 high: Search results are buried beneath an enormous advanced-filter surface and an overlay ad. |
support-core-task-successprimary-flow-completion | pass | high | Read Last links directly to Chapter 345, which loaded successfully with visible comic pages and labelled chapter navigation. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid route shows a clear 404, plain-language message and GO HOME recovery link; forms use required constraints. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP at 3.9s (score 0.53); it identified the above-fold Queen Bee cover as loading=lazy without fetchpriority=high. F09 high: The homepage LCP is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout captures reported CLS 0 across templates; Lighthouse measured CLS 0.004 and all images have dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 63ms task and 13ms TBT; Lighthouse TBT was 10ms, with no sustained blocking on listing/chapter. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR and Lighthouse both identify axios.min.js as a high-priority parser-inserted render-blocking request; Lighthouse reports a 593ms longest dependency chain. F10 medium: A parser-inserted Axios script blocks the critical path. |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | high | Only 35.9KiB of script transferred on home and 47.6KiB on chapter; no large duplicate/unused application bundle dominated the load. |
be-inclusivenames-roles-labels | issues | high | DOM inspection found username, email and password fields with no associated label or aria-label, using placeholders alone; several submit buttons also expose no innerText in the DOM probe. F11 high: Authentication form controls lack persistent accessible labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 1.0 and the high-contrast probe retained visible text/control colors. |
be-inclusivestructure-and-focus | issues | high | The homepage has two H1 elements (ManhwaRead and Home Page), several empty H2s, and the focused search controls report outline-style none. F12 medium: Heading and focus structure has avoidable defects. |
be-inclusivelegible-text | pass | high | Card titles, chapter labels and body UI remain readable at 360px without clipping or cramped horizontal wrapping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The target probe measured the Index disclosure control at 24x24 CSS px, below the commonly usable 44px target, although narrow layouts otherwise reflow without overflow. F13 medium: Not all controls meet a robust target-size baseline. |
follow-best-practicesno-console-errors | pass | high | The errors-in-console audit passed and no uncaught exception was reported during the representative load. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found five oversized homepage images; the 297x289 PNG logo is rendered at 40px and Lighthouse estimates 151KiB total image savings. F14 medium: Several images are materially oversized for their rendered dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse recorded three deprecation warnings, including Shared Storage and StorageType.persistent, from the Cloudflare challenge script. F15 low: A Cloudflare challenge script triggers deprecated API warnings. |
be-discoverabletitle-and-description | pass | high | All three templates expose descriptive, template-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Navigation uses real href links, robots permits public content, and all tested templates include viewport metadata and fit 360px. |
be-discoverablecanonical-and-indexing-signals | issues | high | Lighthouse canonical audit scored 0 even though the rendered DOM resolves a canonical URL; this suggests malformed, conflicting or non-absolute source markup that should be normalised. F16 medium: The homepage canonical signal fails Lighthouse validation. |
be-discoverablestructured-and-shareable-metadata | pass | high | Detail and chapter pages include JSON-LD plus Open Graph title, description and image matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirmed HTTPS and HSTS but reported Content-Security-Policy absent. F17 high: The main document has no Content-Security-Policy. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | No known tracker domain or exposed secret was found; one secure HttpOnly first-party Cloudflare cookie was set, and third parties were primarily content/font/CDN origins. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The auth DOM contains username/password forms with no WebAuthn/passkey affordance and empty autocomplete attributes; no permission prompts fired on load. F19 medium: Account sign-in is password-only and lacks modern credential hints. |
be-private-and-securedefensive-browser-policies | issues | high | The headers probe reports no CSP and does not reliably expose X-Content-Type-Options as present, while frame and referrer protections are configured. F18 medium: Browser-enforced defenses are incomplete. |
be-resilientprogressive-enhancement | pass | high | Homepage, detail and chapter each had 100% rendered-content coverage in raw HTML and were not JS shells. |
be-resilientresilient-runtime-behaviour | pass | high | Menus, detail actions and reader controls remained within narrow viewports; the core detail-to-reader journey completed without a broken shell. |
be-resilientoffline-and-installable | not-applicable | high | This content website is not presented as an installable app; offline installability is contextual, while no-JS content resilience was assessed separately. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing route renders a stable 404 with explanatory copy and a GO HOME action rather than a blank shell or spinner. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares en-US; content order and mobile reflow remain coherent in the tested left-to-right locale. |
be-internationalisedlocale-aware-data | issues | high | Homepage cards render dates such as 14/01/2025 while html lang is en-US, a conflicting locale convention; no machine-readable time elements were found on the detail page. F20 medium: Visible dates are fixed-format strings rather than locale-aware output. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative pages show publication dates but no events, appointments, recurrence or user-facing times that cross time zones. |
be-trustworthyno-dark-patterns | issues | high | The ad overlays core controls, uses sexual clickbait and a dominant VIEW MORE action, while the user is trying to filter search results. F21 medium: The mobile search journey uses an obstructive promotional ad pattern. |
be-trustworthyhumane-error-handling | pass | high | Login, registration and reset fields use native required constraints, preserving browser validation and preventing empty submission. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found empty autocomplete values on username, email, current password and new-password fields. F22 medium: Sign-in, registration and reset fields omit autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Only password login/register/reset controls are present; no passkey/WebAuthn path or reauthentication affordance was found. F23 medium: The account flow does not offer phishing-resistant authentication. |
be-sustainableoptimised-assets | issues | high | Lighthouse estimates 151KiB homepage image savings; the chapter loads JPEG pages through XHR/blob URLs and the image audit reports no responsive sources for 28 chapter images. F24 medium: Image delivery leaves meaningful avoidable byte savings. |
be-sustainableno-wasteful-work | pass | high | TBT was 10-13ms, script transfer stayed below 48KiB per sampled template, and no autoplay video/audio or known analytics tracker was found. |
be-sustainablethird-party-and-media-budget | issues | high | The homepage transfers 778,223 of 1,093,750 bytes from third parties; the sampled chapter transfers 807,474 of 1,104,616 bytes third-party, including 215KiB fonts. F25 medium: Third-party media and fonts dominate transferred bytes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No transactional or productivity capability is intended for agent invocation; public content is already fully available in raw HTML. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model feature is part of the reader experience, so on-device inference would not currently replace a server inference task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 open/close and sidebar toggle cycles, nodes fell 162,749 to 161,354 and self size fell 10,469,886 to 10,462,434 bytes after GC. |
be-memory-efficientbounded-footprint | pass | high | The homepage retained about 10.46MB self size after GC; this is proportionate to a media catalog and did not grow in the repeated interaction sample. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The post-interaction summary showed no growing Detached* constructor population and total nodes decreased after repeated UI cycles. |
Provenance
Canonical report: results/atomic/reports/0533-manhwaread_com.json
Report SHA-256: 1f1d72193b0683fcba27421553ec178224ba94c4499c29a063bc16566f839e46
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/manhwaread_com/2026-07-21T10-04-54-651Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/manhwaread_com/2026-07-21T10-04-54-651Z
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.