Manifest position 342 · CrUX rank bucket 1000
https://www.whatsapp.com
Coverage complete
Coverage-complete report-only audit of seven representative paths. External blog/FAQ/business properties and the web.whatsapp.com authenticated product were excluded because they are separate origins/products.
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-mode screenshot is visually identical to the light capture; the dark-condition probe reports body background rgb(255,255,255), colorScheme "normal", while matchMedia confirms the emulated dark preference. WA-001 medium: The public site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulated preference matched and getAnimations() returned no active animation; scroll-behavior was auto. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast:more capture preserved readable controls/text and Lighthouse color-contrast scored 1. |
implement-natural-interactionsview-transitions | issues | high | The live CSS feature probe found zero view-transition declarations and the DOM probe found no view-transition use across the navigation-heavy MPA. WA-002 low: Route and state changes do not opt into View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation surface was present, the CSS contained zero scroll/view timeline declarations, and sampled scrolling produced no long tasks. |
implement-natural-interactionsphysical-gestures | pass | high | No custom drag, swipe, pull-to-refresh, parallax, or carousel gesture surface was present; normal platform scrolling remained usable. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The compact header does not remain as obstructive chrome during the long scroll; navigation remains clear at entry without a JS-driven scroll effect. |
provide-guided-navigationanchored-positioning | pass | high | The tested header does not expose viewport-edge tooltip/popover content requiring anchored positioning; no detached visible menu was found after the attempted Features activation. |
provide-guided-navigationdirects-attention | pass | high | Prominent headings, Download CTAs, real route links, and the dedicated 404 Return home action give clear destination and focus cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No consent wall, pop-up, interstitial, or content-obscuring banner appeared on load in any representative template. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | No modal flow or transient blocking overlay appeared in the audited journeys; inputs and native selects remained directly operable. |
maximize-content-reduce-noisereduced-chrome | pass | high | The first viewport prioritizes the product message and one primary CTA; chrome is compact and no interruption obscures content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Homepage, download, calling, privacy, contact, support form, and Arabic samples all reported 0 px horizontal overflow with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The live CSS probe found zero @container rules even though card, feature, header, and download components are reused in materially different widths; mobile layout itself does reflow successfully. WA-003 low: Responsive behavior is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size and identified the 45×15 px Sitemap target with only 17.2 px safe clickable space; the live probe counted 24 visible controls below 24 px in at least one dimension. WA-004 medium: Some interactive targets are too small for reliable touch input. |
support-core-task-successclear-purpose-and-primary-action | pass | high | “Message privately” and Download are immediately prominent; download, calling, privacy, and support pages have descriptive H1s and clear next actions. |
support-core-task-successprimary-flow-completion | pass | high | Homepage Download reaches the device hub; support selection reaches a detailed staged contact flow; no account wall or upsell interrupts these public journeys. |
support-core-task-successclear-system-state-and-recovery | pass | high | Empty support progression announces “Please enter your phone number,” marks controls aria-invalid, and the 404 page explains the state with Return home and feature links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 4.2 s and FCP 3.3 s (performance 0.78). A separate desktop trace measured LCP 2.23 s and 0 ms blocking, showing the mobile/load condition is the principal risk rather than main-thread contention. WA-005 high: The homepage’s lab LCP is outside the good range. |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer recorded CLS 0.18085 from one shift at about 2460 ms, above the 0.1 good threshold; other sampled templates were stable. WA-006 high: The download page shifts substantially during mobile load. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and Lighthouse both measured 0 ms blocking; homepage layout had no long tasks and the support sample recorded one borderline 50 ms task. |
be-fast-and-stableefficient-resource-delivery | issues | high | The image primitive found all 22 img elements without explicit width/height, 10 below-fold images loaded eagerly, and 12 without srcset. Lighthouse independently failed unsized-images; HAR transferred about 383 kB of images. WA-007 medium: Image delivery leaves avoidable layout and transfer work. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 184 KiB unused JavaScript across six bundles and 14 KiB unused CSS (about 89% of the flagged stylesheet). HAR recorded 364 kB script transfer across 10 requests. WA-008 medium: The homepage ships substantial code unused during the audited load. |
be-inclusivenames-roles-labels | pass | high | Lighthouse image-alt passed; 83 interactive elements had computed names in the live probe; support inputs expose ARIA names and radio labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passed and the high-contrast preference capture retained visible text and controls. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed landmark-one-main and heading-order, identifying footer H4 headings after H2 content. The live landmark probe found only HEADER and FOOTER; keyboard focus itself remained visible. WA-009 medium: The homepage omits a main landmark and skips heading levels. |
be-inclusivelegible-text | pass | high | Body copy uses comfortable measure and spacing, remains unclipped at 360 px, and Arabic copy reflows without horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Representative-path evidence directly supports “The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling.” with no divergence observed. |
follow-best-practicesno-console-errors | pass | high | Lighthouse found no browser errors logged during the page load. |
follow-best-practicessound-document-and-assets | pass | high | Representative-path evidence directly supports “Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.)” with no divergence observed. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse’s BFCache audit found an actionable unload handler in the main frame, plus no-store policies that prevent restoration. WA-012 low: The homepage cannot use the back/forward cache. |
be-discoverabletitle-and-description | pass | high | Homepage, download, contact, and localized routes expose descriptive titles and meta descriptions; crawler captures retain title/H1/description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed descriptive link text and listed five Learn more links to calling, privacy, community, messaging, and business pages. Links are real hrefs and remain crawler-visible, but their labels are ambiguous out of context. WA-010 medium: Repeated “Learn more” labels hide destination meaning. |
be-discoverablecanonical-and-indexing-signals | pass | high | Representative pages returned 200, expose canonical and 61 hreflang signals; robots points to a populated sitemap and permits ordinary public crawling. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found Open Graph title but zero application/ld+json blocks on the WhatsApp organization/product homepage. WA-013 low: The organization homepage has social metadata but no structured entity data. |
be-private-and-securesecure-transport-and-headers | pass | high | HTTPS, HSTS, CSP, nosniff, X-Frame-Options, Permissions-Policy, secure SameSite cookies, no mixed-content errors, and no exposed secrets were observed; the narrower policy gap is recorded under defensive-browser-policies. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | No known tracker origins or third-party cookies were found; network origins were WhatsApp-owned and only three first-party cookies were set. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The audited www.whatsapp.com marketing and support surfaces do not perform authentication or request browser permissions; web.whatsapp.com is a separate product origin outside this host audit. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no Referrer-Policy and a CSP style-src containing unsafe-inline. HTTPS, HSTS, nosniff, X-Frame-Options DENY, Permissions-Policy, secure SameSite cookies, and a nonce-based script policy were present. WA-011 low: Browser policy coverage has two avoidable gaps. |
be-resilientprogressive-enhancement | pass | high | Raw HTML contains 100% of rendered homepage content tokens and 93% on download; both retain title, H1, and description without JavaScript and are not JS shells. |
be-resilientresilient-runtime-behaviour | pass | high | Five templates and the staged support page rendered without clipping or horizontal overflow; no blank shell or stuck overlay appeared. |
be-resilientoffline-and-installable | not-applicable | high | The audited host is a server-rendered public marketing/support site, not the WhatsApp messaging web app; installability/offline app behavior is not a core journey here. |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route renders a clear “404. This page doesn’t exist,” offers Return home, and lists useful feature recovery links rather than a broken shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Arabic probe reported lang="ar" but an empty documentElement.dir. The mobile screenshot does visually render RTL and the route has no overflow, so the issue is semantic robustness rather than a visible break today. WA-014 low: The Arabic document does not expose an explicit dir attribute. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public pages contain no user-facing dates, prices, currencies, or numeric data requiring locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages contain no scheduled events or time-zone-sensitive values. |
be-trustworthyno-dark-patterns | pass | high | No consent nag, disguised ad, forced continuity, confirmshaming, pricing ambiguity, or obstructive cancellation pattern appeared in the public download/support journeys. |
be-trustworthyhumane-error-handling | pass | high | After Next Step with empty values, the page announces the phone error through an alert and applies aria-invalid/aria-describedby to the required controls. |
be-trustworthytrustworthy-input-assistance | issues | high | The live support-form probe found phone and email controls outside a form element, both email fields use type=text, and all eight input controls have empty autocomplete values. The fields do have ARIA names and empty submission produces an announced phone-number error. WA-015 medium: The support form does not provide browser autofill semantics. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | The audited host has no checkout, subscription, consent purchase, or account-management flow; Log in hands off to web.whatsapp.com outside this host audit. |
be-sustainableoptimised-assets | pass | high | Representative-path evidence directly supports “Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized.” with no divergence observed. |
be-sustainableno-wasteful-work | pass | high | The trace reported no long tasks or continuing media work and HAR recorded 38 bounded load requests; the separate unused-code finding captures the observed shipping waste. |
be-sustainablethird-party-and-media-budget | pass | high | The page loaded no video/audio, no known tracker, and 1.11 MB total transfer from WhatsApp-owned origins; no autoplay/background media continued work. |
be-agent-readystructured-agent-capabilities | not-applicable | high | WhatsApp’s public marketing site does not declare an agent-facing task surface; its robots policy explicitly opts major AI crawlers out, so WebMCP capability exposure is not inferred as intended. |
be-agent-readyon-device-inference | not-applicable | high | No page feature in the representative public marketing/support set calls for on-device inference; absence is not a user-facing failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top scroll cycles, heap snapshot self size changed from 10,225,653 to 10,353,127 bytes (+1.25%) and DOM count stayed 1229; no unbounded pattern was observed in this bounded run. |
be-memory-efficientbounded-footprint | pass | high | The content-heavy page baseline snapshot was about 10.2 MB self size with 195,213 heap graph nodes; live JS used about 6.9 MB before interaction, proportionate to the sampled page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated scrolling left the live DOM exactly at 1229 nodes and increased snapshot graph nodes only 1.35%; no growing detached/listener symptom was observed, though constructor-level leak tracing was not available. |
Provenance
Canonical report: results/atomic/reports/0342-www_whatsapp_com.json
Report SHA-256: 553981d8012b10cef7dae9175530a28ea34df61953fc6eb019e890fef55665ab
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_whatsapp_com/2026-07-20T02-13-55-618Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_whatsapp_com/2026-07-20T02-13-55-618Z
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.