Manifest position 453 · CrUX rank bucket 1000
https://faq.whatsapp.com
Coverage complete
All 58 catalog checks were judged across five representative public help-center paths.
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 capture is pixel-equivalent to the light capture; the probe reports colorScheme "normal" and the same light rgb(240, 242, 245) body background. F1 medium: The help center ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned an empty array; no auto-advance or nonessential animation was running. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast capture remained fully visible, and Lighthouse color-contrast passed with no failing elements. |
implement-natural-interactionsview-transitions | pass | high | The stylesheet inspection found view-transition rules and the browser exposes document.startViewTransition; no abrupt state-loss issue was observed. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation is present on the sampled help templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The sampled help center exposes ordinary links, search and disclosure controls, not gesture-driven interactions. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The persistent category navigation and article context remain visible while long content scrolls, providing stable orientation without scroll-handler long tasks. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned transient overlay was exposed on the sampled primary paths. |
provide-guided-navigationdirects-attention | pass | high | Article navigation highlights the current article in green, uses a clear H1 and platform tabs, and search results highlight the query term. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | First-load home screenshot contains no modal, consent wall or interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | No modal flow was triggered; the only persistent feedback prompt visibly provides a close control and does not obscure the article body. |
maximize-content-reduce-noisereduced-chrome | issues | high | On article and category mobile captures, the always-visible left navigation occupies about 110 of 360 physical pixels before the content column. F3 medium: Persistent navigation chrome consumes a disproportionate share of the small-screen layout. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 device viewport, layout reports hasViewportMeta:false, innerWidth:980 and scale:0.367. Screenshots show the permanent desktop sidebar and very small content. F2 critical: Mobile browsers receive a desktop 980 CSS-pixel layout scaled down to 360 device pixels. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The live stylesheet probe found multiple size-based @container rules, including editor and component containers. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe focused the Help Center link, language control, all sidebar buttons, search input and article links; every sampled element reported outline:none and boxShadow:none. F5 high: Keyboard focus is programmatically reachable but has no visible focus indicator. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home first viewport clearly asks “How can we help you?” and makes search and popular topics primary. |
support-core-task-successprimary-flow-completion | pass | high | The representative search URL returned 16 relevant backup results with descriptive links, and the sampled result article loaded successfully. |
support-core-task-successclear-system-state-and-recovery | pass | high | The explicit error route explains that the page was not found and offers Help Center Home, back and WhatsApp recovery actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured FCP 13.2s and LCP 17.5s (performance 0.55). A separate trace measured FCP/LCP 2.25s, showing network variability but corroborating that the page is delivery-bound rather than main-thread-bound. F6 high: Cold-load paint performance is far outside the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0 on home and 0.00029 on the article, both in the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace TBT was 17ms with one 67ms task; layout observed no long tasks on home. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 41 requests and 3,150,112 transferred bytes, including two VeryHigh parser-inserted stylesheets. Lighthouse reports render-blocking savings of 1.35s and a 3,063 KiB payload. F7 high: The page ships a long critical delivery chain and multi-megabyte payload for a simple help index. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1,906 KiB unused JavaScript and 306 KiB unused CSS; many individual bundles are over 90% unused. F8 high: Most shipped CSS and JavaScript is unused on the help-center homepage. |
be-inclusivenames-roles-labels | issues | high | Lighthouse reports aria-required-children, list and listitem failures, and an agent accessibility-tree failure. The DOM also exposes core navigation controls as DIV role=button. F4 high: The rendered accessibility structure contains malformed ARIA/list relationships. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passed with no failing elements; the high-contrast emulation remained readable. |
be-inclusivestructure-and-focus | issues | high | The focus probe focused the Help Center link, language control, all sidebar buttons, search input and article links; every sampled element reported outline:none and boxShadow:none. F5 high: Keyboard focus is programmatically reachable but has no visible focus indicator. |
be-inclusivelegible-text | issues | high | The page computes 12px body text inside a 980px layout that Chrome scales to 0.367, producing roughly 4.4 physical-pixel text in the mobile captures. F9 high: Text is physically too small to read comfortably on mobile. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The mobile layout primitive reports hasViewportMeta:false and Chrome emulates a 980px layout scaled down. Lighthouse separately fails meta-viewport. F10 high: The missing viewport declaration defeats mobile reflow and makes apparent target sizes misleading. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with an empty error table. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reports a missing/late charset. The article image audit finds all 16 images missing at least one explicit dimension, 15 below-fold images not lazy-loaded and one missing alt. F11 medium: Document encoding and image sizing hygiene are incomplete. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one deprecated-API warning and four BFCache failure reasons. F12 medium: The page uses deprecated APIs and is not eligible for back/forward cache. |
be-discoverabletitle-and-description | issues | high | The sampled article has a descriptive title but article-probe reports description:null. F13 medium: Article pages lack a page-specific meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | robots.txt and sitemap.xml redirect to the generic error route; Lighthouse reports robots.txt invalid with 73 errors, and the page has no viewport meta. F14 high: Crawler and mobile indexing signals are broken or incomplete. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt and sitemap.xml redirect to the generic error route; Lighthouse reports robots.txt invalid with 73 errors, and the page has no viewport meta. F14 high: Crawler and mobile indexing signals are broken or incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The article metadata probe found no JSON-LD and no Open Graph properties. F15 medium: Help articles expose no structured data or social preview metadata. |
be-private-and-securesecure-transport-and-headers | pass | high | HTTPS, HSTS, CSP, nosniff, X-Frame-Options DENY and Secure/Lax first-party cookies were directly observed. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker scan found no known trackers, cookies found no third-party cookies, and the secrets scan found no credentials. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The public help-center paths request no browser permission and contain no authentication flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers show HSTS, nosniff, X-Frame-Options DENY and a nonce-based script policy, but Referrer-Policy is missing and style-src contains unsafe-inline. F16 medium: The otherwise strong security-header set omits Referrer-Policy and allows inline styles. |
be-resilientprogressive-enhancement | issues | high | Discoverability reports isJsShell:true with only 6% raw/rendered word coverage on home and 3% on the article; crawler screenshots are blank while rendered screenshots contain the content. F17 high: Core help content disappears when JavaScript is unavailable. |
be-resilientresilient-runtime-behaviour | pass | high | Home, category, article, search and error templates loaded without console errors or clipped horizontal overflow in their CSS layout viewport. |
be-resilientoffline-and-installable | not-applicable | high | This public content/reference site is not an installed app; offline installability is contextual and was judged outside its primary browse/search purpose. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent path redirects to a clear error page with three recovery actions rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The article reports html lang=en and dir=ltr; the stylesheet includes 4,289 logical-property rules and the language selector is exposed. |
be-internationalisedlocale-aware-data | not-applicable | high | The sampled English help templates render no dates, currencies, durations or locale-sensitive numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled help templates contain no time or event scheduling data. |
be-trustworthyno-dark-patterns | pass | high | No ads, consent wall, upsell, forced continuity or disguised action appeared in the sampled home/search/article/error journey. |
be-trustworthyhumane-error-handling | not-applicable | high | The sampled public surface has search but no submitted data form with invalid/required-field states. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The only input is article search; address, payment, sign-in and sign-up autofill do not apply. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management transaction is present in the public help-center paths. |
be-sustainableoptimised-assets | issues | high | The image audit reports 8 of 16 images over 2x display width, 15 below-fold images without lazy loading and one legacy PNG. F18 medium: Article imagery is routinely oversized and eagerly loaded. |
be-sustainableno-wasteful-work | issues | high | The 3.15 MB load is 2.52 MB JavaScript; Lighthouse estimates about 1.9 MB of that JavaScript and 306 KiB CSS are unused. F19 high: The resource footprint is disproportionate to a mostly text-and-links help page. |
be-sustainablethird-party-and-media-budget | issues | high | The 3.15 MB load is 2.52 MB JavaScript; Lighthouse estimates about 1.9 MB of that JavaScript and 306 KiB CSS are unused. F19 high: The resource footprint is disproportionate to a mostly text-and-links help page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The sampled surface offers browsable help content, not an agent-executable transaction or tool capability. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation/generation interaction is offered; adding inference is not necessary to complete browse or search tasks. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Ten representative category toggles increased total heap self size by about 2.6% between fresh baseline/post captures, not unbounded growth; confidence is limited by cross-session snapshots. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contains 1,048,981 nodes and 55,025,709 bytes self size; after ten representative navigation toggles the fresh-run snapshot is 56,444,423 bytes. F20 medium: The initial heap footprint is large for a static help index. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared among top retained constructors, and ten toggles did not produce runaway total growth. |
Provenance
Canonical report: results/atomic/reports/0453-faq_whatsapp_com.json
Report SHA-256: 12c3788cc8c02b821568ca0a72335dd34308f02e528923e85f298200c961a04b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/faq_whatsapp_com/2026-07-20T22-36-46-287Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/faq_whatsapp_com/2026-07-20T22-36-46-287Z
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.