Manifest position 247 · CrUX rank bucket 1000
https://bookmark.xxx
Coverage complete
Atomic coverage complete across 58 checks and representative catalogue, listing, category, search, outbound detail, localized, and error 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 | The dark-condition screenshot is visually identical to the default capture; the probe reports color-scheme: normal and no preference-specific retinting. F01 medium: The page does not respond to the user’s dark-theme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, CSS still contains pervasive 0.3s transitions and repeated menu interaction produced 11 active animations; there is no reduce override. F02 medium: Reduced-motion users still receive the site’s transitions. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors and prefers-contrast capture retained readable headings, controls, images, and navigation with high-contrast system colors. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition-name or @view-transition usage across the category, listing, and outbound detail journey. F03 low: Route and state changes swap abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked animation surface was present, so there is no scroll animation implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-reveal, carousel, or other gesture-driven core interaction was present. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 12,920px home page exposes a scroll-top control, but inspected CSS has no scroll-state container queries or declarative scroll progress treatment. F04 low: Long pages use JS-style static chrome rather than declarative scroll-state cues. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored menu, or edge-sensitive popover requiring anchor positioning appeared in the representative flows. |
provide-guided-navigationdirects-attention | issues | high | Representative category/listing navigation has no directional transition, target highlight, or post-navigation attention cue. F05 low: Navigation does not visibly preserve or direct attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial desktop, mobile, crawler, and high-contrast captures showed content immediately with no blocking interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe found 0 dialog, 0 popover, and 0 details elements while the DOM/CSS contains custom language and report modal implementations. F06 medium: Modal UI is implemented as custom containers rather than platform primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | The first viewport dedicates most space to the category grid; header and navigation are compact and content-led. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout at 360x800 reported scrollWidth 360, clientWidth 360, and 0px horizontal overflow on home and detail routes. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found no @container rules; the stylesheet uses global max-width media queries throughout. F07 low: Reusable card and navigation components depend only on viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | At 360px, 249 interactive elements measured below 24px in at least one dimension; Lighthouse failed target-size, and focused icon buttons commonly compute outline: none. F08 high: Mobile targets and keyboard focus are inadequate. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly identifies popular categories and exposes search plus labelled catalogue navigation. |
support-core-task-successprimary-flow-completion | pass | high | Listing and category routes exposed direct item links; following one reached an external page with a ready media element and play control. |
support-core-task-successclear-system-state-and-recovery | issues | high | A no-result live search rendered a blank result area, while a real 404 says “Something went wrong” and “try again later” rather than identifying a missing page or offering a direct retry/home action. F09 medium: Search and error recovery states are not actionable enough. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 5.2s (performance 0.80), although the warm raw-CDP trace measured 0.854s with no blocking tasks; the cold result remains the safer user-facing signal. F10 high: Cold-load LCP misses the good threshold. |
be-fast-and-stablevisual-stability | issues | high | The images primitive found all 98 images without width/height attributes; Lighthouse failed unsized-images, even though this observed run recorded CLS 0. F11 medium: Images lack intrinsic dimensions, creating avoidable shift risk. |
be-fast-and-stableefficient-main-thread | pass | high | The raw-CDP trace recorded zero long tasks and 0ms total blocking time over 5 seconds. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR transferred 718KB; Lighthouse reported cache savings and image-delivery issues. GTM took 1.25s, while 98 images lacked intrinsic dimensions and many lacked responsive candidates. F12 medium: Resource delivery includes avoidable discovery and caching costs. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 67KiB unused JavaScript, all from the 157KB Google Tag Manager payload, with about 44% waste. F13 medium: Analytics ships substantial unused JavaScript. |
be-inclusivenames-roles-labels | issues | high | The probe found 67 visible unnamed controls; Lighthouse failed button-name, link-name, and image-alt, including search, menu, language, logo, and pin controls. The images primitive found 38 missing alt attributes. F14 high: Core controls lack accessible names and some images lack alternatives. |
be-inclusivesufficient-contrast | pass | high | Lighthouse did not report a contrast failure and the forced-colors screenshot retained readable text and controls. |
be-inclusivestructure-and-focus | issues | high | The home page jumps from h1 to dozens of h4 elements; Lighthouse failed heading-order, and many icon buttons had outline: none when programmatically focused. F15 high: Heading hierarchy and focus visibility are broken. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show consistent type, unclipped headings, and readable card labels; no horizontal overflow was measured. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport is width=device-width, initial-scale=1.0, user-scalable=no; Lighthouse failed meta-viewport and target-size. The reached player exposed video elements with no caption tracks. F16 high: The viewport prevents zoom and the media journey lacks exposed captions. |
follow-best-practicesno-console-errors | pass | high | Lighthouse passed its errors-in-console audit; HAR network failures were recorded separately and did not surface as uncaught console errors. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype and UTF-8 are valid, all 98 images lack explicit dimensions and Lighthouse reports a low-resolution icon. F17 medium: Asset markup is not fully sound. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse recorded three deprecation warnings from Cloudflare challenge code, including Shared Storage and persistent StorageType usage. F18 low: Third-party runtime code triggers deprecated API warnings. |
be-discoverabletitle-and-description | pass | high | Home, listing, and category recon each found a descriptive title; home/category also provide descriptive meta text. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links and a viewport meta are present; robots allows public catalogue routes and raw-HTML discoverability is 100%. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt is reachable, canonical and 36 hreflang links exist, but /sitemap.xml redirects to /en/sitemap.xml which returns an HTML “Something went wrong” page instead of XML. F19 medium: The advertised sitemap endpoint does not return a sitemap. |
be-discoverablestructured-and-shareable-metadata | issues | high | Home recon found zero JSON-LD blocks and no Open Graph tags despite representing a large categorised collection; the outbound player page supplies rich metadata only after leaving the origin. F20 medium: Catalogue pages lack structured and social metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, or nosniff; cookies found four cookies without Secure, including redisulid, and SameSite=None analytics cookies. F21 high: Transport is HTTPS, but header and cookie protections are weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers detected Google Tag Manager and Google Analytics; the HAR attributes 588KB of 718KB to third-party origins and records analytics collection on load. No consent surface appeared in the initial screenshots. F22 high: Analytics and third-party collection run without visible choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The public catalogue exposes no authentication flow and requested no browser permission during load or tested interactions. |
be-private-and-securedefensive-browser-policies | issues | high | No clickjacking defense, Permissions-Policy, or CSP frame-ancestors was present; Referrer-Policy is unsafe-url, which can disclose full paths to outbound sites. F23 medium: Browser-enforced defensive policies are largely absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% raw-HTML content coverage on home and 93% after the outbound detail redirect, with title and h1 preserved without JS. |
be-resilientresilient-runtime-behaviour | pass | high | Mobile menu repetition, responsive category rendering, and representative route loads completed without runtime breakage or overflow. |
be-resilientoffline-and-installable | issues | high | A manifest link exists, but its JSON contains only icons, with no name, start_url, or display; there is no service-worker registration or controller. F24 medium: The app-like bookmark experience is not installable or offline-capable. |
be-resilientnetwork-and-http-failure-states | issues | high | The test route correctly returned HTTP 404, but rendered “Something went wrong” and “try again later,” implying a transient server failure and offering no prominent contextual recovery. F25 medium: Failure states conflate missing content with server errors. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Arabic route sets lang=ar and dir=rtl, computes RTL, uses logical CSS properties, translates the primary heading, and has 0px overflow. |
be-internationalisedlocale-aware-data | not-applicable | high | Representative pages expose category counts and media durations but no dates, currencies, calendars, or user-entered locale-sensitive values requiring Intl formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, schedules, dates, or time-zone-sensitive data are part of the representative site journeys. |
be-trustworthyno-dark-patterns | issues | high | Opening a bookmark.xxx video URL immediately landed on slutr.com with a UTM campaign parameter; catalogue cards do not visibly identify this cross-origin handoff. F26 medium: Content links silently redirect to a different commercial origin. |
be-trustworthyhumane-error-handling | not-applicable | high | The representative public flow has no user-completed validation form; the hidden report form could not be reached without leaving the audited origin. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up fields are present; the only visible field is catalogue search. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, or account-management flow is offered on bookmark.xxx. |
be-sustainableoptimised-assets | issues | high | Images are mostly WebP and not oversized, but 60 of 98 lack srcset, 98 lack dimensions, and 9 below-fold images are not lazy-loaded. F27 medium: Responsive image delivery is incomplete. |
be-sustainableno-wasteful-work | pass | high | The performance trace recorded no long tasks or continuing main-thread blocking; separate third-party byte waste is recorded under the media-budget check. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 588KB of 718KB transferred; GTM alone is 157KB and two known trackers run on initial load. F28 medium: Third-party code is disproportionate to the catalogue shell. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public catalogue has no declared agent-facing task surface; WebMCP absence is treated as an emerging opportunity rather than a failure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the site intent; on-device inference is not applicable merely because the browser exposes the APIs. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 mobile-menu open/close cycles, heap node count decreased from 178,697 to 177,684 and self-size changed only +2,631 bytes (about 0.03%). |
be-memory-efficientbounded-footprint | pass | high | The home page heap was about 10.05MB self-size with 178,697 snapshot nodes, proportionate to an image-heavy 1,834-element catalogue page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated interaction did not increase total heap nodes, and the menu returned to its base class after 10 cycles; no accumulation signal was observed. |
Provenance
Canonical report: results/atomic/reports/0247-bookmark_xxx.json
Report SHA-256: 2af396ac5731e68794f532316b9f2bdff6a2658a5a7fbac79459b74c70e45d42
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/bookmark_xxx/2026-07-19T10-32-12-360Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/bookmark_xxx/2026-07-19T10-32-12-360Z
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.