Manifest position 524 · CrUX rank bucket 1000
https://www.deviantart.com
Partial after retries
Partial audit: 40/58 checks judged; 18 blocked by intermittent CloudFront 403 responses across representative routes. No score generated.
Attempts
3 / 3
Judged checks
40 / 58
Blocked
18
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 | Both light and dark emulation rendered body background rgb(6,7,13), text rgb(242,242,242), and computed color-scheme normal; the system preference did not change the theme. F01 medium: Theme ignores the system color-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | The media query matched and getAnimations() returned no running animations, compared with one 6000ms running animation in the default probe. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast:more screenshot remained readable and Lighthouse color-contrast passed. |
implement-natural-interactionsview-transitions | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry/exit reveal, or other scroll-linked motion was observed on the reachable home or login surfaces. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven component requiring pull, swipe, overscroll, or snap behaviour was present on the reachable surfaces. |
provide-guided-navigationscroll-state-aware-chrome | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
provide-guided-navigationanchored-positioning | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
provide-guided-navigationdirects-attention | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A fixed join/log-in strip covers the full bottom edge of the artwork feed on first load and has no visible dismiss control. F02 medium: Persistent sign-up strip obscures gallery content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The user menu is an absolutely positioned div role=dialog; there are zero native dialog, details, or popover elements, and no accessible dialog name was found. F03 low: User menu uses a custom unnamed dialog container |
maximize-content-reduce-noisereduced-chrome | pass | high | The dark gallery keeps artwork dominant and the login page has one focused form card with restrained chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The narrow capture reported no viewport meta and a 1024 CSS-pixel layout scaled into 360/780 device widths instead of a true narrow responsive layout. F04 high: Narrow screens receive a scaled desktop layout |
adapt-to-the-form-factorcomponent-level-responsiveness | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Several focusable user-menu controls, links, and buttons had outline:none and no replacement box shadow; the narrow UI also scales desktop controls rather than adapting them. F05 high: Keyboard focus is invisible on several controls |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home clearly presents art discovery plus Submit, Create AI Art, Try Video Creator, Log In, and Join; login clearly presents the username-first sign-in action. |
support-core-task-successprimary-flow-completion | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
support-core-task-successclear-system-state-and-recovery | issues | high | Tag, artwork detail, profile, and shop attempts returned a generic CloudFront 403 with no site navigation, retry control, or preserved context. F06 high: Core public routes fail with an unrecoverable edge error |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 14.5s, CLS 0.641, TBT 200ms, and performance 0.40; the unthrottled trace still found three long tasks and 221ms TBT. F07 high: Mobile Core Web Vitals are poor |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.641, far above the 0.1 good threshold, and identified layout-shift culprits. F08 high: The feed shifts substantially during load |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded three long tasks, the longest 219ms, totalling 221ms blocking time; Lighthouse measured 200ms TBT. F09 medium: Long main-thread tasks delay responsiveness |
be-fast-and-stableefficient-resource-delivery | issues | high | The successful load transferred 2.49MB across 89 requests; a parser-inserted VeryHigh-priority stylesheet and a 420KB JS file were leading critical-path/weight signals. F10 medium: Initial resource delivery is heavy |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Seven scripts transferred 748KB; the largest bundle was about 420KB, and Lighthouse performance was 0.40 with missing source maps limiting diagnosis. F11 medium: Large JavaScript dominates the first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found focusable descendants inside aria-hidden content and an accessible-name/visible-label mismatch; the DOM probe also found an unnamed role=dialog. F12 high: Hidden controls remain exposed to assistive technology |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passed and primary text/control contrast was visibly clear in the high-contrast capture. |
be-inclusivestructure-and-focus | issues | high | Hidden menu content remained focusable, and several focused controls computed to outline:none with no replacement focus indicator. F13 high: Focus management breaks in the hidden user menu |
be-inclusivelegible-text | pass | high | Body and control text is crisp, aligned, and readable on the reachable surfaces, with no observed clipping in the content columns. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The runtime reported no viewport meta and rendered a 1024px CSS layout scaled down to the narrow screen, reducing text and target sizes rather than reflowing. F14 high: Mobile reflow relies on page scaling |
follow-best-practicesno-console-errors | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
follow-best-practicessound-document-and-assets | pass | high | The successful home document had HTML5 doctype, UTF-8 charset, valid title/description, and Lighthouse passed image-alt, contrast, and best-practices overall. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found a large first-party JavaScript file without a source map and multiple referenced source maps returning 403. F15 low: Production JavaScript source maps are unavailable |
be-discoverabletitle-and-description | pass | high | Home has a descriptive unique title and a descriptive meta description; Lighthouse passed both audits. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Anchors were crawlable, but Lighthouse found one generic “Learn more” link and the successful layout probes found no viewport meta, producing desktop-scale rendering on narrow screens. F16 medium: Mobile/search crawl signals are inconsistent |
be-discoverablecanonical-and-indexing-signals | issues | high | Home exposes a canonical and permissive robots policy, but /sitemap.xml returned HTTP 404 for a very large public content site. F17 medium: No sitemap is available at the conventional endpoint |
be-discoverablestructured-and-shareable-metadata | pass | high | Home exposes Organization JSON-LD plus Open Graph and Twitter title, description, image, and canonical URL matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff, framing protection, and CSP are present, but CSP permits unsafe-eval/unsafe-inline and two first-party cookies, including userinfo, lacked Secure. F18 medium: Cookie and CSP hardening is incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacted five third-party origins; 87 of 89 requests and 2.33MB were cross-origin, including frog.wix.com telemetry, although no built-in known-tracker match fired. F19 medium: The initial page has a broad cross-origin footprint |
be-private-and-securein-context-permissions-and-modern-auth | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
be-private-and-securedefensive-browser-policies | issues | high | Permissions-Policy was absent and CSP permits unsafe-eval/unsafe-inline; HSTS, X-Frame-Options, nosniff, and Referrer-Policy were present. F20 medium: Permissions-Policy is absent |
be-resilientprogressive-enhancement | blocked | high | ['evidence/discoverability.json', 'evidence/discoverability-crawler.png'] |
be-resilientresilient-runtime-behaviour | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
be-resilientoffline-and-installable | blocked | high | ['evidence/comprehensive-probe.json'] |
be-resilientnetwork-and-http-failure-states | issues | high | Four representative public routes rendered a generic CloudFront 403 instead of a branded recoverable failure state. F06 high: Core public routes fail with an unrecoverable edge error |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=en and exposes a visible language control; no conflicting direction was observed on the reachable English UI. |
be-internationalisedlocale-aware-data | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
be-internationalisedtime-zone-correctness | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
be-trustworthyno-dark-patterns | pass | high | The reachable login presents terms/privacy links, an unchecked-to-continue-free flow, clear social sign-in labels, and no confirmshaming or disguised advertising was observed. |
be-trustworthyhumane-error-handling | blocked | high | ['evidence/login-invalid-probe.json'] |
be-trustworthytrustworthy-input-assistance | issues | high | The username field had a visible label but no autocomplete token; the home search field explicitly used autocomplete=off. F21 medium: Sign-in fields omit autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | blocked | high | The representative-path attempt was externally blocked by intermittent CloudFront 403 responses; tag, artwork detail, profile, and shop probes all returned the generic edge error. |
be-sustainableoptimised-assets | pass | high | Artwork URLs request explicit fitted/fill dimensions and quality parameters, and the 48-image gallery transferred about 966KB rather than original-resolution media. |
be-sustainableno-wasteful-work | issues | high | The initial surface transferred 2.49MB over 89 requests and executed three long tasks, including 221ms total blocking time, before user interaction. F22 medium: Initial background and script work is wasteful |
be-sustainablethird-party-and-media-budget | issues | high | Cross-origin CDNs and services accounted for 2.33MB; scripts alone were 748KB and fonts 113KB on the initial art feed. F23 medium: Cross-origin script and font budget is high |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capability exposure is emerging and no declared WebMCP/agentic surface was visible; absence is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the reachable public surfaces required on-device inference, so built-in AI use is not applicable to this audit scope. |
be-memory-efficientno-leak-under-repeated-interaction | blocked | high | ['evidence/heap-baseline.json', 'evidence/heap-post-scroll.json'] |
be-memory-efficientbounded-footprint | blocked | high | ['evidence/heap-baseline.json'] |
be-memory-efficientno-detached-dom-or-unbounded-listeners | blocked | high | ['evidence/heap-baseline.json', 'evidence/heap-post-scroll.json'] |
Provenance
Canonical report: results/atomic/reports/0524-www_deviantart_com.json
Report SHA-256: dc8f6230ebb747431100f8f61fc67633be4dba7523588e5c49770c2466fa3011
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_deviantart_com/2026-07-28T01-42-32-801Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_deviantart_com/2026-07-28T01-42-32-801Z
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.