Manifest position 139 · CrUX rank bucket 1000
https://discord.com
Coverage complete
Coverage complete. Public marketing templates were audited; authenticated in-app chat and post-login account settings were not covered because no credentials were provided. The public login entry point itself was exercised and failed visibly.
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 | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-001 medium: Public surfaces do not consistently adapt to the user’s colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The preference matched and document.getAnimations() returned no running animations. |
respect-user-preferencesrespects-contrast | pass | medium | The high-contrast capture retained visible text, navigation, calls to action, and consent controls. |
implement-natural-interactionsview-transitions | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-002 low: Route and major state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-003 low: The long, animated marketing page does not use declarative scroll timelines. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited public pages expose scrolling, links, buttons, and a menu, but no swipe, drag, carousel, or pull gesture that needs a custom physical interaction. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Navigation remains available and the page provides clear scroll progression through distinct content sections without obscuring the content. |
provide-guided-navigationanchored-positioning | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-004 low: Navigation dropdowns use custom structures without CSS anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Strong headings, contrasting primary actions, and consistent navigation make the current location and next action clear. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-005 high: The cookie banner obscures a large share of the primary mobile content on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-006 medium: Rich navigation relies on ad-hoc links and role-based overlays instead of native overlay primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The site itself is visually content-led, but the on-load consent chrome covers 253.8px of an 800px mobile viewport. DISCORD-005 high: The cookie banner obscures a large share of the primary mobile content on first load. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | scrollWidth, clientWidth, and innerWidth were all 360px with zero horizontal overflow; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-007 low: Responsive behavior is viewport-driven rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | pass | medium | The skip link received a visible 2px solid outline and primary mobile buttons are large, full-width targets. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each template has a descriptive H1 and an obvious next action or content purpose. |
support-core-task-successprimary-flow-completion | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-008 high: The primary login journey rendered as a blank page in the audited browser. |
support-core-task-successclear-system-state-and-recovery | issues | medium | The route remained blank with no loading, error, retry, or recovery state. DISCORD-008 high: The primary login journey rendered as a blank page in the audited browser. |
be-fast-and-stablegood-core-web-vitals | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-009 high: Cold-load performance is well outside the good Core Web Vitals experience. |
be-fast-and-stablevisual-stability | pass | high | The layout observer reported CLS 0.0209 and Lighthouse reported 0.075, both within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 630ms TBT and 4.6s main-thread work; the desktop trace still recorded three long tasks and 145ms TBT. DISCORD-009 high: Cold-load performance is well outside the good Core Web Vitals experience. |
be-fast-and-stableefficient-resource-delivery | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-010 high: The homepage transfers 17.5 MB and has expensive render-blocking and cache behavior. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-011 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-013 medium: The visible privacy-link text is absent from its accessible name. |
be-inclusivesufficient-contrast | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-012 medium: The cookie notice privacy link fails text contrast. |
be-inclusivestructure-and-focus | issues | high | Landmarks and skip link exist, but opening the mobile menu leaves aria-expanded absent and focus on the fixed cookie banner rather than the invoked menu. DISCORD-013 medium: The visible privacy-link text is absent from its accessible name. |
be-inclusivelegible-text | pass | high | Headings and body text remain readable, well spaced, and unclipped on the tested viewports. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | The main viewport does not disable scaling, mobile reflow has no overflow, and primary targets are comfortably sized. |
follow-best-practicesno-console-errors | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-014 medium: The homepage logs browser and network errors during load. |
follow-best-practicessound-document-and-assets | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-015 medium: Many image elements lack stable intrinsic dimensions and several are distorted. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-016 low: The load includes deprecated browser APIs and missing source maps. |
be-discoverabletitle-and-description | pass | high | The homepage has a descriptive title and meta description and both survive in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Primary links use hrefs, viewport metadata is present, public marketing routes are not blocked, and Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | pass | high | The page returned 200, canonical points to https://discord.com/, robots permits public content and declares route-specific sitemap indexes. |
be-discoverablestructured-and-shareable-metadata | pass | high | Open Graph title, description, image, and type match the visible Discord homepage; three JSON-LD blocks are present. |
be-private-and-securesecure-transport-and-headers | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-017 medium: Cookie and header policy has avoidable security gaps. |
be-private-and-securedata-minimisation-and-third-parties | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-018 medium: The public landing page has a broad third-party and tracking footprint before consent. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appeared on load, and login configuration declares a WebAuthn origin, indicating phishing-resistant authentication support is wired into the app. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS, nosniff, X-Frame-Options and Permissions-Policy exist, but Referrer-Policy is absent and CSP/cookie posture has gaps. DISCORD-017 medium: Cookie and header policy has avoidable security gaps. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 88% rendered-word coverage; the page is not a JS shell and title and description survive. |
be-resilientresilient-runtime-behaviour | issues | medium | The fixed consent banner overlaps the menu experience and retains focus, weakening overlay sequencing and runtime robustness. DISCORD-005 high: The cookie banner obscures a large share of the primary mobile content on first load. |
be-resilientoffline-and-installable | not-applicable | high | Discord is an intrinsically online real-time communication service; no offline content promise is evident, so offline/installability is not required for this public marketing audit. |
be-resilientnetwork-and-http-failure-states | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-019 high: The login route has no useful recovery state when its client runtime does not initialise. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The page declares en-GB, exposes a language selector, and loads localization support; reading order is correct in the tested locale. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited views do not present locale-sensitive data requiring Intl formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event times, recurring schedules, or time-zone-sensitive values appear in the audited public templates. |
be-trustworthyno-dark-patterns | pass | high | Consent presents equally prominent Reject All and Accept All actions, and Nitro states that it is a subscription without confirmshaming. |
be-trustworthyhumane-error-handling | issues | medium | The login route rendered no form or error UI, so users in this failure condition receive no humane validation or recovery assistance. DISCORD-020 high: The account entry point provides no visible, reversible, or assistive flow in the audited condition. |
be-trustworthytrustworthy-input-assistance | issues | medium | No inputs rendered, so sign-in autocomplete, labels, and input assistance were unavailable in the tested primary account flow. DISCORD-020 high: The account entry point provides no visible, reversible, or assistive flow in the audited condition. |
be-trustworthysafe-commercial-and-account-flows | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-020 high: The account entry point provides no visible, reversible, or assistive flow in the audited condition. |
be-sustainableoptimised-assets | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-022 medium: Several decorative assets are oversized or delivered in inefficient formats. |
be-sustainableno-wasteful-work | issues | high | The page eagerly transfers many media files, performs 4.6s main-thread work, and ships more than 1MB estimated unused CSS/JS. DISCORD-021 high: Media and third-party transfer is disproportionate for a marketing landing page. DISCORD-011 medium: The page ships substantial unused CSS and JavaScript. |
be-sustainablethird-party-and-media-budget | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-021 high: Media and third-party transfer is disproportionate for a marketing landing page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing capability is declared, and this emerging surface was not part of the public marketing page’s stated intent. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or other inference feature is offered on these pages, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Self size rose 1.6% from 68.0MB to 69.1MB while object and closure counts stayed flat or fell; no unbounded retained-growth signal appeared in this bounded run. |
be-memory-efficientbounded-footprint | issues | medium | Direct evidence across the selected templates showed the expected behavior with no observed divergence. DISCORD-023 medium: The marketing homepage has a large baseline heap and DOM footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Top constructors showed no Detached population and closure count fell from 23,494 to 23,475; no listener/closure accumulation signal appeared. |
Provenance
Canonical report: results/atomic/reports/0139-discord_com.json
Report SHA-256: 7835f198a300be411121cd21c7bb249370ef004078b2f7e2ea4bec7f16269fbe
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/discord_com/2026-07-18T16-55-22-946Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/discord_com/2026-07-18T16-55-22-946Z
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.