Manifest position 887 · CrUX rank bucket 1000
https://pimpbunny.com
Coverage complete
Coverage-complete multi-template audit. The required age-assurance UI obscured screenshots, but rendered DOM and objective probes remained available; no check was omitted.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark/reduced screenshot is visually identical to the light capture; the computed body remains rgb(255,255,255), color-scheme is normal, and CSS inspection found no prefers-color-scheme rule. F01 medium: No user-preference dark theme |
respect-user-preferencesrespects-reduced-motion | pass | medium | CSS inspection found a prefers-reduced-motion rule and the emulated reduced-motion probe reported no active animations. |
respect-user-preferencesrespects-contrast | issues | high | Under prefers-contrast: more, controls retain normal colors and CSS inspection found no prefers-contrast or forced-colors rules; axe also found 16 contrast failures. F02 medium: High-contrast preferences are not handled |
implement-natural-interactionsview-transitions | issues | high | The CSS feature probe found no view-transition rules on this multi-page site. F03 low: Route and state changes lack View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | CSS and animation probes found no scroll-timeline and no observed scroll-linked effect. |
implement-natural-interactionsphysical-gestures | pass | medium | CSS inspection found scroll-snap support and no evidence that the listing requires custom pointer gestures. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage main content is over 10,000px tall, but CSS inspection found no scroll-state queries or progress treatment and the rendered chrome is static. F04 low: Long pages provide no scroll-state guidance |
provide-guided-navigationanchored-positioning | issues | high | The DOM uses data-popover controls while CSS inspection found no anchor-name or position-anchor support. F05 low: Menus use hand-wired positioning rather than anchored primitives |
provide-guided-navigationdirects-attention | issues | high | No View Transition, highlight, or comparable attention-guidance rules were found across listing, search and detail navigation. F06 low: Navigation changes do not cue moved attention |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial screenshot is fully obscured by an age-verification overlay, while page scripts also include popunder and smartpop advertising integrations. Age assurance is necessary, but unrelated popunder behavior is not. F07 high: Third-party interruptions dominate entry |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The active page overlay is a fixed fancybox div and the DOM contains no dialog or popover elements. F08 medium: The age gate and menus are custom overlay structures |
maximize-content-reduce-noisereduced-chrome | issues | high | The rendered homepage includes a premium banner, six affiliate links, multiple live/ad placements and 345 interactive elements before/around a 10,000px content feed. F09 medium: Promotional chrome crowds the content experience |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800, layout metrics report scrollWidth 360, clientWidth 360, and horizontalOverflowPx 0. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules despite card components appearing across homepage, listing, search and detail templates. F10 low: Reusable cards are not container-responsive |
adapt-to-the-form-factorinput-modality-aware | issues | high | The target probe found 106 visible controls below 44px, including three 28x28 header buttons; axe reports the viewport disables user scaling. F11 high: Touch and zoom affordances are restricted |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Title/description clearly identify adult video/model content and the entry state clearly asks the user to start age verification. |
support-core-task-successprimary-flow-completion | pass | medium | Direct walkthroughs loaded listing, populated search results, and a specific video detail URL with title, metadata and player DOM. |
support-core-task-successclear-system-state-and-recovery | pass | medium | A nonexistent URL resolves to a visible PAGE NOT FOUND state with Back to Home and alternative content. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 21.04s, FCP 2.82s and Speed Index 12.31s, producing a 0.59 performance score; the trace corroborates a much faster gate paint, showing the full content load is the expensive state. F12 high: Largest Contentful Paint is extremely slow |
be-fast-and-stablevisual-stability | issues | high | All 90 inspected images lack width/height attributes and mobile observed CLS reached 0.09375. F13 medium: Images do not reserve layout space |
be-fast-and-stableefficient-main-thread | pass | medium | Trace recorded one 51.48ms long task and only 1.48ms total blocking time; Lighthouse TBT was 78.5ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR captured 139 requests and 9.20MB transferred, including 6.25MB images, 2.00MB XHR/media and six parser-blocking stylesheets. F14 high: Initial delivery is excessively heavy |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 338KiB unused JavaScript and 39KiB unused CSS; the HAR records 80 third-party requests and 2.69MB third-party transfer. F15 medium: Unused and third-party code inflate startup |
be-inclusivenames-roles-labels | issues | high | axe found critical unnamed header buttons, 20 unnamed links, one missing image alternative and three untitled frames. F16 high: Many controls and media lack accessible names |
be-inclusivesufficient-contrast | issues | high | axe found 16 serious contrast failures, including 14px navigation links at 3.2:1 where 4.5:1 is required. F17 high: Text contrast fails WCAG AA |
be-inclusivestructure-and-focus | issues | high | axe found content outside landmarks; the homepage content headings precede the age-gate H1, and the detail page has an empty heading followed by promotional model headings. F18 medium: Landmark and page-heading structure is inconsistent |
be-inclusivelegible-text | pass | medium | Desktop/mobile screenshots show readable age-gate typography and the content DOM uses an 18px body size with fluid widths. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport is width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0; axe classifies this as critical. F19 high: Mobile zoom is disabled |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console audit passed with zero items. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 90/90 without explicit dimensions, 40 oversized, 66 without srcset and 43 legacy-format images. F20 medium: Image assets are not soundly dimensioned or modernized |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three BFCache failure reasons centered on Cache-Control: no-store and a JavaScript request receiving no-store. F21 medium: The page is blocked from the back/forward cache |
be-discoverabletitle-and-description | pass | medium | Homepage, listing, search, detail, Spanish and 404 probes each expose descriptive titles; homepage has a descriptive meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found five non-crawlable anchors; the DOM also includes a Go Premium href ending in #. F22 medium: Some navigation targets are not crawlable |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage returned 200, exposes canonical and hreflang, robots permits general/search crawling, and sitemap.xml is present and populated. |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph is present and the detail template has VideoObject JSON-LD, but the homepage contains no JSON-LD describing the site/organization. F23 low: The homepage lacks organization/site structured data |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP is absent; PHPSESSID is not Secure or HttpOnly, and kt_acctoken uses SameSite=None without HttpOnly. F24 high: CSP and cookie protections are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 15 third-party origins including Google Analytics; HAR recorded 80 third-party requests and 2.69MB before gate completion. F25 high: The page sends data across a broad third-party ad/tracking surface |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The site exposes profile/account and subscription controls, but rendered source contains no WebAuthn/passkey integration; Lighthouse confirms no permission prompts on load. F26 medium: Account surfaces do not expose modern phishing-resistant authentication |
be-private-and-securedefensive-browser-policies | issues | high | HSTS, nosniff, SAMEORIGIN and same-origin referrer policy are present, but CSP and Permissions-Policy are absent. F27 medium: Browser policy coverage is incomplete |
be-resilientprogressive-enhancement | pass | medium | Discoverability primitive found 99% raw/rendered content coverage, no empty mount and no JavaScript shell. |
be-resilientresilient-runtime-behaviour | issues | high | Menus use custom data-popover wiring, the age gate is a fixed fancybox overlay, and Lighthouse reports BFCache blocking. F28 medium: Runtime behavior relies on fragile custom overlays and no-store navigation |
be-resilientoffline-and-installable | issues | high | A standalone manifest with icons/start_url exists, but the service-worker controller probe is false. F29 low: The installable manifest is not backed by an offline runtime |
be-resilientnetwork-and-http-failure-states | pass | medium | The exercised unknown URL presents a useful Page Not Found state and Back to Home recovery path. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Spanish route renders Spanish navigation and pricing but html lang remains en; CSS inspection found 329 physical-direction declarations and only one logical-property signal. F30 high: Localized pages declare the wrong document language |
be-internationalisedlocale-aware-data | pass | medium | Spanish route localizes relative dates and subscription prices/decimal formatting and exposes locale-specific hreflang URLs. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling or time-zone-sensitive workflow was present in the representative routes. |
be-trustworthyno-dark-patterns | issues | high | The page loads popunder/smartpop scripts and presents many external affiliate destinations around core navigation before the user clears age assurance. F31 high: Aggressive affiliate and popunder behavior undermines predictable choice |
be-trustworthyhumane-error-handling | pass | medium | The exposed search flow is optional GET input with no required-field trap; a direct query returns clear categorized results. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | DOM form inventory found search text fields and package radios, but no personal-data fields requiring autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | A four-option recurring upgrade form is injected on every audited template, but its DOM labels show price/term only and no nearby cancellation, renewal or reversal information. F32 medium: Subscription commitments lack nearby cancellation context |
be-sustainableoptimised-assets | issues | high | The image audit found 40 oversized images, 43 legacy-format images, 66 without responsive sources and no modern-format images. F33 high: Media assets are substantially over-delivered |
be-sustainableno-wasteful-work | issues | high | HAR captured 62 XHR/fetch requests and about 2MB, largely live HLS segments, while an age gate obscured the page. F34 high: Heavy media work starts before the user reaches content |
be-sustainablethird-party-and-media-budget | issues | high | The HAR records 80 third-party requests/2.69MB; detail DOM contains four video elements, two autoplaying muted, with no tracks. F35 high: Third-party and autoplay media cost is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | robots.txt disallows GPTBot, ChatGPT-User, ClaudeBot and other AI agents; no WebMCP capability was observed. |
be-agent-readyon-device-inference | not-applicable | high | DOM and script capability probes expose no built-in language-model or summarizer surface. |
be-memory-efficientno-leak-under-repeated-interaction | issues | low | After ten open/close cycles, heap summary size rose from 18.61MB/281,093 nodes to 22.22MB/315,989 nodes (about 19%/12%); separate browser sessions make this a low-confidence risk signal, not proof of a leak. F36 medium: Repeated menu interaction shows retained-growth risk |
be-memory-efficientbounded-footprint | pass | medium | Baseline summary is 18.61MB for the media-heavy page; the live DOM contains about 2,482 elements and runtime JS heap is about 18.26MB, proportionate though worth monitoring. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Heap summaries list no Detached* constructor among leading populations; after ten menu cycles the menu returns to opened=false and live DOM remains 2,479 elements. |
Provenance
Canonical report: results/atomic/reports/0887-pimpbunny_com.json
Report SHA-256: 8bcc9ccdab8644973a07c9fad8b15b202f4f25933cf973b7b44be81102a6e4a2
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pimpbunny_com/2026-07-28T10-44-08-023Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pimpbunny_com/2026-07-28T10-44-08-023Z
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.