Manifest position 534 · CrUX rank bucket 1000
https://mangafire.to
Coverage complete
Coverage-complete model-driven audit across home, detail, reader, preferences, and failure-state archetypes.
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 | Under emulated prefers-color-scheme: light the page remained rgb(14, 19, 27); color-scheme was normal and the loaded CSS contained no prefers-color-scheme rule. F-002 high: The fixed dark palette ignores the user’s color-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | Emulated reduced motion reported zero active animations; the loaded CSS had no motion rules that continued against the preference. |
respect-user-preferencesrespects-contrast | issues | high | axe found 49 serious color-contrast failures and Lighthouse found 44 affected nodes, including active tabs, metadata, buttons and card timestamps. No prefers-contrast or forced-colors CSS was found. F-003 high: Low-contrast text and controls fail WCAG AA |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found zero view-transition declarations and the document reported no active animations or view transition names. F-004 medium: Route and state changes have no View Transition treatment |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found no main-thread scroll-animation anti-pattern and no scroll-linked decorative motion on the inspected routes. |
implement-natural-interactionsphysical-gestures | pass | high | Loaded CSS contains seven scroll-snap declarations and the reader uses native scrolling without horizontal overflow. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The reader exposes an aria-valuenow/valuemax page progress rail and persistent chapter position. |
provide-guided-navigationanchored-positioning | issues | high | The loaded CSS contained zero anchor-name, position-anchor or position-try declarations despite multiple menu-like buttons with aria-haspopup. F-005 medium: Menus and transient controls do not use resilient anchored positioning |
provide-guided-navigationdirects-attention | pass | high | Reader page progress, chapter count, and explicit Previous/Next/Series/Home controls clearly preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | DOM and elementFromPoint probes on the home and reader routes found an unnamed fixed <a target="_blank" href="#"> at z-index 9,999,999 covering 100% of the viewport. It blocks the visible controls and disguises the click target. F-001 critical: A transparent full-viewport link intercepts the entire experience |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM contains many menu controls but no evidence of dialog/popover primitives, while an ad-hoc fixed anchor is used as a page-wide overlay. F-006 high: Custom overlay patterns replace semantic dismissible primitives |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots show content-led manga cards and a reader that devotes most of the viewport to the page image. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 layout measured exactly 360px scroll/client width with 0px horizontal overflow; the reader probe also reported zero overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The complete loaded stylesheet contained zero @container rules even though cards, toolbars and reader controls are reused in materially different widths. F-007 medium: Components rely on viewport styling rather than container responsiveness |
adapt-to-the-form-factorinput-modality-aware | issues | high | The homepage viewport sets maximum-scale=1,user-scalable=no; Lighthouse marks this critical and the interaction probe found an 18px-high sync link. Focus styling itself was visible. F-008 high: Zoom is disabled and at least one target is too short |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, detail, and reader screenshots communicate browse, Start reading, and page/chapter progression clearly. |
support-core-task-successprimary-flow-completion | issues | high | The reader loaded 62 pages and responsive controls, but elementFromPoint at the viewport center returns the transparent z-index 9,999,999 anchor rather than the reader; the same blocker exists on browse and detail pages. F-009 critical: The primary browse-to-read flow is visually present but click-blocked |
support-core-task-successclear-system-state-and-recovery | issues | high | A fabricated path returned HTTP 200 and rendered the normal homepage with no not-found message, search recovery, or route correction. F-010 high: Unknown routes return the homepage with HTTP 200 instead of a recovery state |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.7s and FCP 3.2s (performance 0.72), although TBT was only 10ms and CLS 0.042. The local trace corroborated a lighter warm-path LCP of 1.20s. F-011 high: Mobile LCP is well outside the good threshold |
be-fast-and-stablevisual-stability | pass | high | Lighthouse CLS was 0.042 and layout observation was 0.0067, both within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse TBT was 10ms; trace TBT was 11.32ms with one 61ms task. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 60 requests and 1,754,011 transferred bytes; Lighthouse estimated 887 KiB image savings, found render-blocking requests and poor LCP discovery, while 62/62 homepage images lacked dimensions. F-012 high: Image and critical-resource delivery is inefficient |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 112 KiB unused JavaScript and 16 KiB unused CSS on the homepage. F-013 medium: The initial route ships avoidable unused code |
be-inclusivenames-roles-labels | issues | high | axe and Lighthouse both report one serious unnamed link; it is the full-viewport target=_blank overlay. The page also had one input without a programmatic label. F-014 high: An interactive full-page link has no accessible name |
be-inclusivesufficient-contrast | issues | high | axe found 49 serious color-contrast failures and Lighthouse found 44 affected nodes, including active tabs, metadata, buttons and card timestamps. No prefers-contrast or forced-colors CSS was found. F-003 high: Low-contrast text and controls fail WCAG AA |
be-inclusivestructure-and-focus | issues | high | axe found nested/duplicate main landmarks; the DOM probe found two MAIN elements and no h1 on the homepage. Visible keyboard focus did pass. F-015 medium: Homepage landmarks and heading structure are invalid |
be-inclusivelegible-text | pass | high | Desktop and mobile screenshots show readable type sizing, unclipped titles, and stable card/detail layouts. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The homepage meta viewport uses maximum-scale=1,user-scalable=no; both axe and Lighthouse classify this as a failure. F-016 high: The viewport prevents user zoom |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with zero items. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reported three deprecated API warnings and unsized images; the image primitive found all 62 homepage images lacked width/height attributes. Doctype and charset were valid. F-017 medium: Deprecated APIs and unsized assets remain |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three deprecated API warnings and unsized images; the image primitive found all 62 homepage images lacked width/height attributes. Doctype and charset were valid. F-017 medium: Deprecated APIs and unsized assets remain |
be-discoverabletitle-and-description | pass | high | Homepage, detail, and reader DOM each expose descriptive titles and a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability measured 1% raw/rendered word coverage and a JS shell; direct robots.txt and sitemap.xml requests returned 403, and the only unnamed rendered link is the overlay. F-018 high: Crawler-facing navigation is effectively absent without JavaScript |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical link was present, robots/sitemap returned 403 to a plain client, and a nonexistent URL returned a soft-404 HTTP 200 homepage. F-019 medium: Canonical and error indexing signals are unreliable |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail DOM had no JSON-LD; its og:title remained “MangaFire - Read Manga Online Free” rather than the visible title “All-Class Awakening: God Slayer”. F-020 medium: Detail pages lack entity metadata and use generic social previews |
be-private-and-securesecure-transport-and-headers | issues | high | The page uses HTTPS, but headers found no CSP, HSTS, nosniff, frame defense, Referrer-Policy or Permissions-Policy; the session cookie lacked Secure. F-021 critical: Core browser security headers and a Secure session cookie are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe saw six third-party origins, including whos.amung.us and count-server.sharethis.com; 51 of 60 HAR requests and 1.72 MB were classified third party. F-022 medium: Tracking/share requests are made without a clear need or disclosure |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse found no geolocation or notification request on load; the audited public reading flow requests no permission or authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Header evidence found no clickjacking defense, CSP/Trusted Types policy, HSTS, Referrer-Policy, Permissions-Policy or nosniff protection. F-023 high: No defensive browser policies are configured |
be-resilientprogressive-enhancement | issues | high | Raw HTML contained only five content tokens versus 263 rendered tokens; discoverability classified the response as a JS shell with 1% coverage. F-024 high: Core content disappears when JavaScript is unavailable |
be-resilientresilient-runtime-behaviour | issues | high | DOM and elementFromPoint probes on the home and reader routes found an unnamed fixed <a target="_blank" href="#"> at z-index 9,999,999 covering 100% of the viewport. It blocks the visible controls and disguises the click target. F-001 critical: A transparent full-viewport link intercepts the entire experience |
be-resilientoffline-and-installable | issues | high | The platform probe found neither a manifest nor an active service worker on this app-like reader. F-025 medium: The reading app has no manifest, service worker or offline fallback |
be-resilientnetwork-and-http-failure-states | issues | high | A fabricated path returned HTTP 200 and rendered the normal homepage with no not-found message, search recovery, or route correction. F-010 high: Unknown routes return the homepage with HTTP 200 instead of a recovery state |
be-internationalisedlang-dir-and-logical-properties | issues | high | The detail page exposes titles in many scripts, but html is fixed lang=en with implicit direction; CSS inspection found 140 physical left/right declarations versus four logical-property uses. F-026 medium: Multilingual content is wrapped in an English, physically positioned UI |
be-internationalisedlocale-aware-data | pass | high | Observed relative chapter times use human-readable localized English units and no malformed number/currency/date output was present on representative routes. |
be-internationalisedtime-zone-correctness | not-applicable | high | No absolute times, appointments, schedules, or user-entered temporal data appear in the representative catalog, detail, preferences, or reader surfaces. |
be-trustworthyno-dark-patterns | issues | high | DOM and elementFromPoint probes on the home and reader routes found an unnamed fixed <a target="_blank" href="#"> at z-index 9,999,999 covering 100% of the viewport. It blocks the visible controls and disguises the click target. F-001 critical: A transparent full-viewport link intercepts the entire experience |
be-trustworthyhumane-error-handling | not-applicable | high | The representative public routes contain search/filter inputs but no submitted validation form; account forms could not be entered without changing account state. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-up, or other personal-data form appears in the representative public routes; the simple title search does not need autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | DOM and elementFromPoint probes on the home and reader routes found an unnamed fixed <a target="_blank" href="#"> at z-index 9,999,999 covering 100% of the viewport. It blocks the visible controls and disguises the click target. F-001 critical: A transparent full-viewport link intercepts the entire experience |
be-sustainableoptimised-assets | issues | high | The image audit found 62 legacy-format images, 30 without srcset, 15 oversized, and no modern-format image; HAR attributed 1.37 MB to images. F-027 high: Image assets are not delivered sustainably |
be-sustainableno-wasteful-work | issues | high | The initial view makes 60 requests and transfers 1.75 MB, while Lighthouse identifies unused JS/CSS and hundreds of KiB of avoidable image transfer. F-028 medium: The homepage performs disproportionate initial work |
be-sustainablethird-party-and-media-budget | issues | high | HAR classified 51 requests and 1,724,576 bytes as third party, including external image/CDN, font, counter and sharing origins. F-029 medium: Third-party transfer dominates the page budget |
be-agent-readystructured-agent-capabilities | issues | high | Discoverability reports a 1% JS-shell response, Lighthouse agentic browsing scored 0.33 with malformed accessibility-tree and llms.txt signals, and no structured entity data was found. F-030 high: Public catalog content is not reliably available to agents |
be-agent-readyon-device-inference | not-applicable | high | Summarisation or local model inference is not necessary to browse and read the supplied manga content, so adding it would not clearly improve this experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, DOM nodes stayed at 1,165 and JS heap rose only 30,376 bytes (0.35%); snapshot self-size rose 32,072 bytes (0.25%). |
be-memory-efficientbounded-footprint | pass | high | Homepage baseline heap was 12.63MB with 193,437 nodes in the heap graph; live DOM was 1,165 nodes, proportionate to 62 content images. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Across ten repeated scroll cycles, live DOM remained exactly 1,165 nodes and heap stayed effectively flat, with no accumulating rendered elements. |
Provenance
Canonical report: results/atomic/reports/0534-mangafire_to.json
Report SHA-256: 52db316ebc1982882e375b21874a608a30a96a02fe3e0abeab8567bc2cf8a33b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/mangafire_to/2026-07-21T10-15-57-797Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/mangafire_to/2026-07-21T10-15-57-797Z
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.