Manifest position 917 · CrUX rank bucket 1000

https://e621.net

Partial after retries

57 of 58 checks were conclusively judged. Authentication/passkey inspection was blocked by a Cloudflare 403 challenge on /session/new.

Attempts

3 / 3

Judged checks

57 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The preference probe matched prefers-color-scheme: dark, but found color-scheme: normal and no prefers-color-scheme rules; the light and dark captures use the same palette. F-01 medium: The fixed dark palette is not connected to the user’s color-scheme preference.
respect-user-preferences `respects-reduced-motion`	pass	high	No active animations were reported under prefers-reduced-motion: reduce; the representative gate and listing remained static.
respect-user-preferences `respects-contrast`	pass	high	Lighthouse found a contrast defect under the separate inclusive contrast check, but controls and text remained visible in the tested dark surface and no forced-colors-breaking styling was observed.
implement-natural-interactions `view-transitions`	issues	high	The rendered listing probe found no view-transition CSS, and the listing navigation video shows an abrupt full-document swap. F-02 low: Route and major state changes do not use View Transitions.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked parallax, scrollytelling, carousel animation, or entry/exit reveal was present on the representative routes.
implement-natural-interactions `physical-gestures`	not-applicable	high	No gesture-driven or swipe/pull interaction was present; standard scrolling and links use platform behavior.
provide-guided-navigation `scroll-state-aware-chrome`	issues	medium	The desktop and mobile listing captures show fixed-height navigation/news chrome, and CSS inspection found no scroll-driven timeline or scroll-state behavior. F-03 low: Navigation chrome does not react to scroll position.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, popover, or floating menu that requires viewport-edge anchoring was observed on the tested public surfaces.
provide-guided-navigation `directs-attention`	pass	high	Desktop and mobile captures show an active Posts context, clearly separated primary/secondary navigation, and a focused single-column mobile progression.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	The only load-time full-screen interruption is the necessary 18+ Terms gate, with explicit Decline and disabled-until-confirmed Accept actions; no marketing interstitial obscured content.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	DOM evidence shows <form id="tos-form" role="dialog" aria-modal="true">; Lighthouse reports its ARIA role is inappropriate for the element. F-04 medium: The mandatory Terms gate is a form with role="dialog" rather than a native modal dialog.
maximize-content-reduce-noise `reduced-chrome`	pass	high	The desktop listing allocates most width to the media grid and the mobile layout removes the sidebar/navigation rows behind a menu.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Layout primitives at 360×800 reported 0px horizontal overflow for both the gate and accepted listing; mobile screenshots show reflow rather than clipping.
adapt-to-the-form-factor `component-level-responsiveness`	pass	high	CSS inspection found container-query rules, and the same gallery changes from a five-column desktop grid to a three-column narrow layout.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The rendered listing probe measured toolbar buttons at 32×20px and multiple links at 15–20px high, below a comfortable 44×44 CSS pixel target, although keyboard focus remains visible. F-05 medium: Several controls and links have undersized touch targets.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The entry gate states the access requirement; after acceptance the listing labels the search field “Posts” and makes tag search the dominant action.
support-core-task-success `primary-flow-completion`	pass	high	Acceptance followed by /posts and a query URL returned successful SSR listing/search pages; representative browsing did not dead-end.
support-core-task-success `clear-system-state-and-recovery`	pass	high	An empty search reports “0 results”, “Nobody here but us chickens!” and “Go back”; an unknown route returns HTTP 404 and “Not found.”
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured 3.8s LCP on the entry surface; the accepted-listing trace measured 5.13s LCP. CLS was 0.004 and TBT was effectively zero. F-06 high: Largest Contentful Paint is outside the good range.
be-fast-and-stable `visual-stability`	pass	high	Lighthouse CLS was 0.0039 and both layout captures observed no shifts.
be-fast-and-stable `efficient-main-thread`	pass	high	Listing trace found zero long tasks and 0ms TBT; Lighthouse TBT was 2ms.
be-fast-and-stable `efficient-resource-delivery`	issues	high	Lighthouse measured 2.31s root response time and identified the 46.5KB stylesheet as render blocking with about 170ms potential savings. F-07 medium: Slow document response and render-blocking CSS delay first render.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 43.4KB of 46.4KB CSS (93.5%) was unused on the entry surface. F-08 low: The entry surface ships mostly unused CSS.
be-inclusive `names-roles-labels`	issues	high	Lighthouse flags the form-as-dialog role; the listing DOM probe found visible post editor textareas/buttons with no label or aria-label. F-10 medium: The dialog role and several editor controls lack robust accessible semantics.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse/axe measured 3.55:1 for green tag text on #1f3c67 (4.5:1 required) and 1.73:1 differentiation between an inline link and surrounding text, with no underline. F-09 high: Some tag and inline-link colors fail WCAG contrast requirements.
be-inclusive `structure-and-focus`	issues	high	The rendered listing probe found NAV/NAV/FOOTER but no MAIN; its only H1 is “Edit”, while the visible primary section is “Posts”. Focus itself has a dotted outline. F-11 medium: The listing lacks a main landmark and has a misleading heading outline.
be-inclusive `legible-text`	pass	high	Desktop and mobile screenshots show readable text scaling and line wrapping without clipping; the long Terms copy remains scrollable.
be-inclusive `zoom-reflow-targets-and-media`	pass	high	Mobile reflow and viewport scaling are allowed, but the undersized-target issue is recorded under input-modality-aware; no essential timed media was present.
follow-best-practices `no-console-errors`	pass	high	Lighthouse best-practices scored 100 and the runtime probes completed without an uncaught page exception.
follow-best-practices `sound-document-and-assets`	issues	high	The rendered listing probe counted 76 images, 75 without width and height attributes. Current measured CLS was low, but intrinsic reservation is absent in authored markup. F-12 medium: Most listing images omit intrinsic width and height attributes.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse best-practices scored 100; no permission prompt appeared, positive tabindex count was zero, and no deprecated/paste-blocking behavior was observed.
be-discoverable `title-and-description`	issues	high	The entry page title is only “e621”; listing meta description is only “e621”. The listing title is descriptive, but the description does not explain the page. F-13 medium: Entry-page metadata is too generic to describe the site.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Lighthouse SEO flags the /static/site_map link text “More”; viewport metadata and real href links otherwise pass. F-14 low: At least one global navigation label is not descriptive.
be-discoverable `canonical-and-indexing-signals`	pass	high	Public pages returned successful status and canonical URLs; robots.txt advertises a sitemap and allows ordinary crawlers while deliberately excluding AI training crawlers. Dynamic listings intentionally use noindex.
be-discoverable `structured-and-shareable-metadata`	issues	high	The listing probe found og:title set to “ - e621” and og:description to “e621”, despite two JSON-LD blocks. F-15 low: Listing share metadata is malformed or generic.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers show Strict-Transport-Security: max-age=0, which disables HSTS; CSP allows unsafe-inline styles, Permissions-Policy is absent, and the nosniff header is malformed/duplicated in the capture. F-16 high: HSTS is effectively disabled and the header policy has avoidable gaps.
be-private-and-secure `data-minimisation-and-third-parties`	pass	high	Tracker capture found one third-party origin (op.dragonfru.it), no known tracker domains, no third-party cookies, and no exposed secrets.
be-private-and-secure `in-context-permissions-and-modern-auth`	blocked	high	The public site made no permission request on load, but /session/new returned a Cloudflare 403 challenge to the audit browser, so passkey/password implementation could not be inspected.
be-private-and-secure `defensive-browser-policies`	pass	high	CSP includes frame-ancestors none, X-Frame-Options, and strict-origin-when-cross-origin; remaining header gaps are linked to the secure transport finding.
be-resilient `progressive-enhancement`	pass	high	Discoverability found 100% raw/rendered content coverage and no JS shell; fetched listing/help/detail HTML contains core content before JavaScript.
be-resilient `resilient-runtime-behaviour`	pass	high	Advanced/listing controls rendered within both desktop and mobile viewports and the representative panel open/close interaction completed repeatedly.
be-resilient `offline-and-installable`	issues	high	manifest.json provides name, icons, standalone display and start_url, but the service-worker probe found zero registrations and no controlling worker. F-17 low: The app-like gallery advertises installability but has no offline worker.
be-resilient `network-and-http-failure-states`	pass	high	Unknown routes return HTTP 404 with “Not found”; empty search provides a clear zero state and Go back action.
be-internationalised `lang-dir-and-logical-properties`	issues	high	The listing correctly declares lang="en", but CSS inspection counted 499 physical-side declarations and no logical margin/padding/border declarations; dir is not explicitly declared. F-18 medium: The stylesheet is not writing-mode resilient.
be-internationalised `locale-aware-data`	pass	high	Post timestamps are stored as unambiguous ISO 8601 values with offsets; no locale-formatted currency or numeric input was present in the tested public task.
be-internationalised `time-zone-correctness`	pass	high	Sample post timestamps include explicit -04:00 offsets, avoiding ambiguous stored local times; no scheduling or recurring event surface was present.
be-trustworthy `no-dark-patterns`	pass	high	The age/Terms gate uses neutral confirmation labels, explicit Decline, disabled Accept until both acknowledgements, and no confirmshaming or forced continuity.
be-trustworthy `humane-error-handling`	pass	high	The public search has no required fields; its empty state explains the result and offers Go back rather than blaming the user.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	The tested public task uses tag search rather than identity, address, payment, or account inputs where autofill tokens apply.
be-trustworthy `safe-commercial-and-account-flows`	pass	high	No checkout, subscription, or paid continuity flow was present on public pages; account authentication itself is covered by the blocked auth check.
be-sustainable `optimised-assets`	issues	high	Lighthouse estimated 18.9KB savings by serving the 64.5KB PNG mascot in a modern compressed format. F-19 low: The homepage mascot image can be delivered more efficiently.
be-sustainable `no-wasteful-work`	pass	high	The accepted listing transferred 441KB total, scripts were about 100KB, the trace showed no long tasks, and no continuous background media was observed.
be-sustainable `third-party-and-media-budget`	pass	high	HAR recorded a modest 441KB load with about 135KB fonts, no media resources, and only one third-party origin; visible previews are value-bearing content.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	The site explicitly disallows major AI crawlers in robots.txt and exposes no stated agent-facing intent; emerging WebMCP capabilities are therefore out of scope.
be-agent-ready `on-device-inference`	not-applicable	high	No user task on the representative public gallery requires built-in on-device inference, and no agent-facing intent is declared.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten open/close cycles of Advanced Search, heap grew only 11,881 bytes and 56 nodes versus baseline, with no detached constructor in the summaries.
be-memory-efficient `bounded-footprint`	pass	high	Accepted listing baseline heap was 10.68MB across 148,794 nodes, proportionate to a 76-image interactive gallery.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Before/after heap summaries exposed no Detached* constructors and only a 0.04% node-count increase after ten panel cycles.

Provenance

Canonical report: results/atomic/reports/0917-e621_net.json
Report SHA-256: 964c3a4e50d1c66044bcf908a1a75dc599a641293df5c7497fc8628743fa8f1e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/e621_net/2026-07-28T11-50-36-938Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/e621_net/2026-07-28T11-50-36-938Z
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.