Manifest position 731 · CrUX rank bucket 1000
https://manhwaweb.com
Coverage complete
Coverage-complete report-mode audit across five representative public paths. Excluded: registration submission, authenticated profile/library state, uploads, forum posting, payments, destructive account actions, and exhaustive chapter/title sampling because they require credentials, mutate state, leave the primary domain, or reuse audited templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | DOM computed styles report color-scheme: normal, no relevant preference CSS was found, and normal/dark screenshots are byte-identical. F01 medium: The fixed dark palette is not connected to the user’s colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched and runtime/CSS probe found zero active animations, so no non-essential motion remained to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast screenshot retains visible text, navigation, controls and content imagery. |
implement-natural-interactionsview-transitions | issues | high | CSS/runtime probe found no view-transition rules while the audited journey crosses SPA routes from listing to detail to reader. F02 low: Route changes swap abruptly without a transition. |
implement-natural-interactionsscroll-driven-animations | pass | high | Runtime/CSS probe found no scroll listeners or scroll-linked effects; the site uses native scrolling rather than main-thread parallax. |
implement-natural-interactionsphysical-gestures | pass | high | Representative catalogue and reader rely on native scrolling and ordinary links/buttons; no custom pointer/gesture handler fights platform behaviour. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 4,632px homepage and long reader retain static chrome; CSS probe found no scroll-state query, scroll progress, or scroll timeline. F03 low: Long pages provide no scroll-position-aware navigation feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or anchored overlay exists on the representative surfaces. |
provide-guided-navigationdirects-attention | pass | high | Library current navigation is visibly highlighted, title cards lead directly to detail, and reader exposes prominent chapter controls. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile homepage starts with a large migration promotion and external banner; reader starts with two ad blocks before the first chapter panel. F04 high: Promotions and ads displace the primary content at the start of key journeys. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The library “Filtros” disclosure is a styled div and the mobile menu button has no accessible name or aria-expanded state; no dialog/details/popover primitives were found. F05 medium: Custom interactive disclosures lack semantic state. |
maximize-content-reduce-noisereduced-chrome | issues | high | Screenshots show radio chrome, migration artwork and advertising occupying most or all of the first viewport before catalogue/chapter content. F06 high: Non-content chrome overwhelms the catalogue and reader. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout observer measured scrollWidth=clientWidth=360 with zero horizontal overflow across a usable mobile layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries or container-type despite cards and controls appearing in multiple grid widths. F07 low: Reusable card/filter components only respond to viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probe found visible controls as small as 17–26px high; the mobile menu and search submit buttons have no accessible text, and Lighthouse button-name failed. F08 medium: Several controls have weak touch and keyboard affordances. |
support-core-task-successclear-purpose-and-primary-action | issues | high | There is no h1 or main landmark; the first mobile viewport is dominated by radio and migration imagery rather than a clear catalogue heading or read/browse action. F09 high: The homepage delays and weakens the primary browse/read task. |
support-core-task-successprimary-flow-completion | pass | high | The representative journey completed from catalogue to title detail to a readable chapter with real href navigation and visible next controls. |
support-core-task-successclear-system-state-and-recovery | issues | high | HAR records multiple net::ERR_BLOCKED_BY_ORB image failures, while the UI shows broken/blank media without retry or explanatory fallback. F10 medium: Failed media has no useful recovery state. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.5s and CLS 0.417 (performance 0.49); the independent layout run measured CLS 0.350. F11 high: Loading performance and stability miss Core Web Vitals targets. |
be-fast-and-stablevisual-stability | issues | high | All 65 inspected images lack width/height attributes and layout observer recorded two shifts totalling 0.350. F12 high: Images and late content cause large layout shifts. |
be-fast-and-stableefficient-main-thread | pass | high | Trace measured zero long tasks and 0ms total blocking time; Lighthouse TBT was 20ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 108 requests and 8.47MB transferred, including 8.11MB images, 102 third-party requests and many 301/302 image redirects; LCP was 8.5s. F13 high: The homepage transfers an excessive image payload through redirect-heavy third parties. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 167KiB unused JavaScript and 10KiB unused CSS. F14 medium: The page ships avoidable JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | Lighthouse button-name failed; the mobile menu/search buttons have no name, home recon found numerous empty-text anchors, and image audit found 8 missing alt values. F15 high: Important controls and links lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse contrast audit failed, including red “4TA actualizacion” at 3.03:1 and white category labels as low as 2.14:1. F16 high: Text labels fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Homepage and library have no h1; DOM inspection found no main element, and headings begin at h3. F17 medium: Pages lack a logical heading and landmark structure. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable body copy and labels without clipping; reflow has no horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Focus/target probe measured visible links and buttons at 17–26px high, below the recommended 44px touch target, although mobile reflow itself had no overflow. F18 medium: Small controls reduce usability under touch and zoom. |
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 | Image audit found 65/65 images without width/height, 43 oversized and 27 legacy-format images; Lighthouse unsized-images failed. F19 high: Image dimensions and aspect-ratio reservations are missing. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 0.96, no permission prompt fired on load, and no runtime deprecation/console failure was observed. |
be-discoverabletitle-and-description | pass | high | Homepage, library, title detail and reader expose route-specific descriptive titles; homepage/detail have descriptive meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Reader DOM contains javascript: navigation/vote links and numerous anchors with empty accessible text; Lighthouse crawlable-anchors failed. F20 high: Some links are not crawlable or descriptive. |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical URL was found, and /sitemap.xml returns the generic application HTML rather than an XML sitemap. F21 high: Canonical and sitemap signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | Representative title detail has no JSON-LD or Open Graph metadata despite representing a named creative work. F22 medium: Content pages lack structured data and social previews. |
be-private-and-securesecure-transport-and-headers | issues | high | Header audit found no CSP response header, HSTS or nosniff; both analytics cookies were non-Secure and SameSite=None. F23 high: HTTPS is present but baseline security headers and cookie flags are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker audit found 7 third-party origins including Google Analytics; HAR found 102 third-party requests, and 400-day analytics cookies are set without an observed consent control. F24 high: Third-party and analytics exposure is disproportionate. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login exposes email/password and Google sign-in but no passkey/WebAuthn affordance; password/email inputs also omit autocomplete tokens. No permission prompt fired on load. F25 medium: Authentication lacks modern credential support. |
be-private-and-securedefensive-browser-policies | issues | high | Header audit found no clickjacking control, Referrer-Policy or Permissions-Policy, alongside absent HSTS/CSP. F26 high: Browser-enforced defensive policies are missing. |
be-resilientprogressive-enhancement | issues | high | Discoverability runs report 1% raw/rendered word coverage and an empty #root; both homepage and title detail are JS shells, and the crawler screenshots are blank. F27 high: Core content disappears without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Representative menus, cards, detail and reader rendered without clipped overlays or broken route state at mobile width. |
be-resilientoffline-and-installable | not-applicable | high | This public content catalogue is not presented as an installable app; offline installation is contextual, while no-JS resilience is assessed separately. |
be-resilientnetwork-and-http-failure-states | issues | high | HAR records ORB-blocked images and aborted requests; screenshots/DOM offer no retry or useful fallback for those failures. F28 medium: Network and asset failures degrade to broken content. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The site is deliberately Spanish-only and no alternate language or writing-mode surface was found. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public flow has no currency, locale selector or user-entered locale-sensitive data; relative Spanish timestamps are content copy. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled event, booking, calendar or cross-time-zone workflow exists in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Ads on the reader are visibly labelled AD; no consent wall, confirmshaming, forced continuity or disguised purchase was observed. |
be-trustworthyhumane-error-handling | pass | high | Login fields use native required constraints and an empty submit was safely blocked without data loss. |
be-trustworthytrustworthy-input-assistance | issues | high | Login email/password fields and search inputs report empty autocomplete attributes. F32 medium: Login and search inputs omit autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The observed login offers a clear first-party form and Google alternative with registration link; no checkout/subscription commitment exists in scope. |
be-sustainableoptimised-assets | issues | high | Image audit found 43 oversized images, 37 without srcset and 27 legacy formats; a single promotional PNG transferred 2.55MB. F29 high: Images are oversized and insufficiently responsive. |
be-sustainableno-wasteful-work | issues | high | HAR records 100 image requests and 8.11MB of images, while 36 below-fold images are not lazy loaded. F30 high: The homepage eagerly fetches substantially more media than the first view needs. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party requests account for 8.21MB of 8.47MB transferred and 102/108 requests; large banners and radio chrome precede core content. F31 high: Third-party media dominates the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent exists; this emerging capability is optional for the audited reader catalogue. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited scope requires on-device inference; this emerging capability is optional. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 20 mobile-menu toggles, heap self-size changed only from 9,220,825 to 9,272,343 bytes (+0.56%) and node count by +0.61%, with no monotonic leak signal. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap summary was 9.22MB self size for the media-rich catalogue, proportionate to the rendered page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after summaries show closures 7,846→7,864 and no Detached* constructor among top retained constructors after 20 toggles; no unbounded accumulation was observed. |
Provenance
Canonical report: results/atomic/reports/0731-manhwaweb_com.json
Report SHA-256: c659a3ffce43baaac467c199e4001751f3efd35d219bf926127faa86300149e5
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/manhwaweb_com/2026-07-22T17-27-30-908Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/manhwaweb_com/2026-07-22T17-27-30-908Z
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.