Manifest position 411 · CrUX rank bucket 1000
https://litnet.com
Coverage complete
Coverage-complete remote audit across five representative public paths. Authentication, checkout completion, and private account states were not entered; relevant unobserved form checks are explicitly not-applicable rather than inferred.
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 | Dark emulation screenshot stayed on the same white surfaces as the default capture; no color-scheme feature was found in captured CSS. F01 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, 155 animations were still running with 1200 ms duration. F02 high: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/prefers-contrast capture retained visible white text, controls, focus boundaries, and yellow links against black surfaces. |
implement-natural-interactionsview-transitions | issues | medium | Rendered DOM/CSS contained no view-transition usage; navigation crosses visibly different Angular and legacy templates without a shared transition treatment. F03 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, or entry/exit reveal was observed on the sampled templates, so there is no scroll-linked effect to implement declaratively. |
implement-natural-interactionsphysical-gestures | pass | medium | Captured CSS contains overscroll-behavior and the horizontal carousels use native scrolling rather than an observed pointermove-driven gesture layer. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long 5,774 px home page retained static navigation chrome and captured CSS had no scroll-state query or scroll timeline. F04 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, contextual popover, or edge-positioned menu was present in the sampled states. |
provide-guided-navigationdirects-attention | issues | medium | The sampled home/list/detail transitions provide no directional transition, progress marker, current-location trail, or post-navigation attention cue. F05 low: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile load screenshots show a cookie/recommendation banner obscuring a substantial portion of content before interaction. F06 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probe found zero dialog, popover, and details elements while the on-load consent overlay is implemented as custom chrome. F07 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Outside the consent interruption, listing and author screenshots devote the large majority of the viewport to books and author content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport the book-detail page forced a 970 CSS-pixel viewport and rendered a tiny desktop layout; meta viewport is width=970. F08 critical: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Captured CSS reported zero container-query rules; reused book/card components rely on template/viewport treatment rather than container-level adaptation. F09 low: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found six target-size failures, seven unnamed buttons, and seven unnamed links; the DOM probe also found 24x24 and 34x36 controls. F10 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, listing, book, and author captures clearly present books, genres, prices, and reading/purchase context. |
support-core-task-successprimary-flow-completion | issues | high | The representative browse-to-book path lands on a 970 px legacy detail template at mobile width, making the reading/purchase interface extremely small and difficult to operate. F11 critical: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid route returned a real HTTP 404 and a Russian “Страница не найдена” document with site navigation. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured home LCP 16.47 s and TBT 672 ms; book LCP 10.87 s, CLS 0.187, and TBT 313.5 ms. F12 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | Mobile layout observer measured home CLS 0.388 and book CLS 0.116; 17 images lacked explicit dimensions. F13 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 672 ms TBT on home; trace recorded five long tasks and 97.88 ms TBT in its separate capture. F14 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 154 requests and 6.58 MB transferred, with several parser-inserted scripts and missing cache/compression signals. F15 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 778,059 bytes of unused JavaScript and HAR recorded 41 script requests totalling 1.98 MB. F16 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found seven unnamed buttons and seven unnamed links on home; book probe found 34 images without alt text. F17 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 27 color-contrast failures on the home page. F18 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Home has no h1 or main landmark and starts at h3; book has no main landmark and Lighthouse flagged heading order. F19 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | The 360 px book capture is a 970 px desktop page scaled down, producing text and controls too small for comfortable reading. F20 critical: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Home viewport sets maximum-scale=1; book uses width=970, and Lighthouse failed meta-viewport and target-size checks. F21 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit recorded zero console errors. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype/UTF-8 are valid, 17 images lack dimensions, six are oversized, and 23 use legacy raster formats. F22 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found deprecated API use, missing source maps, DevTools inspector issues, a BFCache blocker on book detail, and third-party cookie issues. F23 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | Home and book probes found descriptive titles and meta descriptions; raw no-JS HTML preserves them. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found a non-crawlable anchor and unnamed links; book detail uses a fixed width=970 viewport instead of a mobile-friendly viewport. F24 medium: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and book return HTTP 200, expose canonicals, robots permits public content, and robots points to a valid sitemap index. |
be-discoverablestructured-and-shareable-metadata | pass | high | Book detail includes Book JSON-LD and matching Open Graph title/image metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP and X-Content-Type-Options are absent and 24 of 31 observed cookies lack Secure. F25 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 20 third-party origins and four known tracker domains; HAR shows 73 third-party requests and 5.89 MB. F26 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | low | No permission prompt appeared on load, but the public login affordance had no WebAuthn/passkey capability visible in loaded scripts or sampled auth entry points. F27 low: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lacked frame protection, Referrer-Policy, Permissions-Policy, CSP/frame-ancestors, and X-Content-Type-Options. F28 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 75% home and 83% book content coverage in raw no-JS HTML; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Sampled home, listing, book, and author templates rendered their primary content without blank shells or cut-off overlays. |
be-resilientoffline-and-installable | issues | medium | The app-like reading service links a web manifest, but the loaded home page had no active service-worker controller or demonstrated offline fallback. F29 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route returned HTTP 404 with a dedicated Russian not-found page rather than a blank shell or false 200. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Home declares lang=ru and book declares lang=ru-RU; sampled Russian reading order is correct. |
be-internationalisedlocale-aware-data | pass | medium | Dates and prices are rendered in Russian locale forms such as “20 Июл” and “159 ₽/RUB”. |
be-internationalisedtime-zone-correctness | not-applicable | high | Sampled public pages show publication dates but no appointments, recurring events, or user-entered times whose cross-zone/DST behavior can be meaningfully exercised. |
be-trustworthyno-dark-patterns | issues | high | The on-load consent banner offers only “Принять”; it states continued use constitutes agreement and provides no equally visible reject choice. F30 high: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | not-applicable | high | No editable form or invalid-submission state was present in the sampled unauthenticated public journey. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up input was entered in the sampled public browse/read journey. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Book purchase content is rendered through the fixed 970 px mobile template, while consent is one-sided; clear, proportionate mobile commercial interaction is not achieved. F31 high: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | HAR transferred 4.48 MB of images; three hero JPGs are 0.84–0.97 MB each, six images are oversized, and 23 use legacy formats. F32 high: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The page starts 41 scripts and 73 third-party requests on load, including multiple analytics/tag-manager stacks; Lighthouse estimates 778 KB unused JS. F33 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 5.89 MB from third-party origins and trackers reported 20 third-party origins, disproportionate for a book-listing first view. F34 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | WebMCP/tool exposure is emerging and no declared agent-facing transaction surface was found; raw content is already substantially machine-readable. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing summarisation or inference feature was present whose on-device implementation could be judged. |
be-memory-efficientno-leak-under-repeated-interaction | issues | low | After ten bottom/top scroll cycles, heap summary grew from 45.30 MB/784,915 nodes to 50.23 MB/839,991 nodes (about 10.9% bytes and 7.0% nodes); separate-session variance lowers confidence. F35 medium: Repeating a representative interaction (open/close a modal, navigate a route and back, infinite-scroll a list) about 10 times does not grow retained heap without bound; what is allocated during the interaction is released when it ends. |
be-memory-efficientbounded-footprint | pass | medium | Baseline retained self size was 45.30 MB for an image-rich Angular catalogue; large but proportionate, with no single constructor dominating abnormally. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Heap summaries contained no Detached* constructor among retained populations; the repeated test did not directly reveal detached-DOM accumulation. |
Provenance
Canonical report: results/atomic/reports/0411-litnet_com.json
Report SHA-256: 20a6789b76694a72abf6e48d8503895a5cb9d16b053fd3ecd32a30914685a84a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/litnet_com/2026-07-20T15-02-28-259Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/litnet_com/2026-07-20T15-02-28-259Z
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.