Manifest position 138 · CrUX rank bucket 1000
https://support.google.com
Coverage complete
Atomic coverage complete across 58 checks and four representative public-help 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 | Desktop captures under default and prefers-color-scheme: dark are pixel-identical (55,668 bytes each); the computed color-scheme is normal and the page remains white. The article offers a manual dark-mode button, but does not honour the system signal. F01 medium: System dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, the probe still found 0.218s to 0.4s transitions on the header, links, controls and radio affordances. F02 low: Reduced-motion preference leaves transitions active |
respect-user-preferencesrespects-contrast | pass | medium | Forced-colors/prefers-contrast screenshot preserves readable text, controls, borders and focus affordances. |
implement-natural-interactionsview-transitions | issues | high | The authored CSS/HTML probe found no @view-transition, ::view-transition, view-transition-name declaration, or startViewTransition call on the product/article template. F03 low: Page and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | No scroll-linked animation or scrollytelling surface exists on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | The audited help, search and article journeys expose no gesture-driven control that requires a custom physical gesture treatment. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | The article probe shows the fixed header changes class after scrolling 900px while remaining positioned at top:0. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip, contextual menu, or edge-positioned transient overlay was needed in the exercised paths. |
provide-guided-navigationdirects-attention | pass | medium | Product/article templates provide descriptive tabs, headings, topic links and clear related/next-step navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The article and 404 screenshots show an “Ask Google Help” floating panel covering the lower-right of the reading surface on load, with no visible dismiss control. F05 medium: Persistent assistant control obscures article content |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | medium | No modal or transient rich-control flow was opened in the tested core journey; native links, buttons, inputs and selects carry the interactions observed. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Screenshots show content-first layouts with a compact header and generous reading space; no full-page interstitial appears. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | All three representative templates report scrollWidth=clientWidth=360 with viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The rendered stylesheet probe found no @container rules on either the portal or article template, although cards, search, and article modules are reused at different widths. F04 low: Responsive components rely only on viewport-level techniques |
adapt-to-the-form-factorinput-modality-aware | pass | medium | Focus probe shows 40–58px key targets and visible browser/CSS outlines on the core menu, product links and search controls; Lighthouse accessibility scored 1.0. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | First viewports clearly ask how help is needed and expose search/product selection; article title and instructions are immediately clear. |
support-core-task-successprimary-flow-completion | pass | medium | Search for “install” returned a relevant “Use web apps” result and the linked install article provides platform-specific steps without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | medium | A real 404 returns HTTP 404 and presents an explicit explanation plus “Get Google Chrome Help” and “Search on Google” recovery actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 4.30s and FCP at 2.82s on the portal. A separate trace measured LCP at 2.07s, so load performance is variable and at least one controlled run is outside the 2.5s good range. F06 high: Cold-load LCP exceeds the good threshold |
be-fast-and-stablevisual-stability | issues | high | The 360x800 layout observer measured CLS 0.2346 on the article; one shift at 1.84s contributed 0.2236, above the 0.1 good threshold. F07 high: Article template has a large mobile layout shift |
be-fast-and-stableefficient-main-thread | pass | medium | Trace recorded zero long tasks and 0ms total blocking time; Lighthouse TBT was about 100ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse flagged inefficient cache lifetimes (about 51 KiB potential saving), font-display delay (about 150ms), and a problematic network dependency tree; the HAR recorded 72 requests including 19 font requests. F08 medium: Caching and font delivery leave avoidable load delay |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 363 KiB of unused JavaScript. The inline document shipped about 158 KiB unused, two tag-manager bundles about 132 KiB unused together, and supporting scripts added more waste. F09 medium: Large amounts of JavaScript are unused on initial load |
be-inclusivenames-roles-labels | pass | medium | Lighthouse accessibility score was 1.0; the search input has matching visible/ARIA labelling and product links include accessible text. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse accessibility/contrast audits passed and the forced-colors capture remains legible. |
be-inclusivestructure-and-focus | pass | medium | The DOM has one descriptive H1 followed by logical H2/H3 sections, a skip link, and visible focus evidence; Lighthouse accessibility passed. |
be-inclusivelegible-text | pass | medium | Desktop/mobile screenshots show readable line lengths, clear hierarchy and no clipping on portal, product and article templates. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport permits normal scaling, mobile layouts reflow without overflow, core targets are about 40px or larger, and no caption-requiring media is present. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured Error: V from inline support.google.com JavaScript (around lines 195–223) during the portal load. F10 medium: An uncaught exception is logged during page load |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found all 21 img elements without width and height attributes; Lighthouse also failed the unsized-images audit. Although the homepage observer recorded CLS 0, this leaves avoidable shift risk. F11 low: Images omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a large inline first-party JavaScript file without a valid source map, reducing production diagnosability. F12 low: Large first-party JavaScript has no source map |
be-discoverabletitle-and-description | issues | high | The DOM probe and Lighthouse SEO audit both found no meta[name=description] on https://support.google.com/, while product and article pages do provide one. F13 medium: Portal homepage lacks a meta description |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Links use real href values, viewport meta is present, robots permits the audited pages, and link labels are descriptive. |
be-discoverablecanonical-and-indexing-signals | issues | high | The English article exposes an hl locale and a canonical URL but zero hreflang links. /sitemap.xml redirects to the homepage rather than serving a sitemap; robots.txt contains no sitemap declaration. F14 low: Localized indexing signals are incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | The representative Chrome article has no JSON-LD and no Open Graph tags despite representing a stable Help/HowTo entity. F15 medium: Help articles lack structured and share-preview metadata |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no Content-Security-Policy. The cookie audit found six cookies without Secure, including _ga, _gid and tag-manager cookies; these also used SameSite=None. HTTPS, HSTS and nosniff were present. F16 high: CSP is absent and analytics cookies are not Secure |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe observed 13 third-party origins and active Google Analytics/Tag Manager endpoints. The HAR recorded 1.16 MB across 72 requests, including multiple analytics bundles. F17 medium: The portal loads a broad tracking and third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appeared on load, and sign-in is delegated to Google Accounts, which exposes modern authentication including passkeys; no password form exists on support.google.com. |
be-private-and-securedefensive-browser-policies | issues | high | The main response has HSTS, nosniff and X-Frame-Options, but no Referrer-Policy or Permissions-Policy; CSP/frame-ancestors is also absent. F18 medium: Referrer and permissions policies are absent |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures show 100% rendered-word coverage in raw HTML on portal, product and article pages; none is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Menus/header and article controls rendered within desktop/mobile viewports without clipping; fixed chrome remained stable on scroll. |
be-resilientoffline-and-installable | not-applicable | medium | This public help corpus is a content MPA rather than an installed application; offline installability is not necessary for its primary task. |
be-resilientnetwork-and-http-failure-states | pass | medium | The invalid article URL returned HTTP 404 and a useful recovery screen rather than a blank shell or misleading success. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The English templates correctly set lang=en and expose a language selector, but the stylesheet probe found physical left/right declarations and no logical inline/block properties on the representative article. F19 medium: Localized templates use physical rather than logical CSS |
be-internationalisedlocale-aware-data | not-applicable | medium | The representative pages contain no dates, numbers, prices, durations, or other locale-formatted data. |
be-internationalisedtime-zone-correctness | not-applicable | medium | The representative pages expose no event scheduling or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | pass | medium | No consent wall, confirmshaming, forced continuity, disguised ad, or coercive default appeared in the exercised public help journeys. |
be-trustworthyhumane-error-handling | not-applicable | medium | The only exercised input is an optional search field; there is no required-data validation flow. |
be-trustworthytrustworthy-input-assistance | pass | medium | The search field is clearly labelled and autocomplete=off is appropriate for free-form support queries; no address, payment, or account form is present. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | No checkout, subscription, consent, or account-management flow exists on support.google.com; sign-in is delegated to accounts.google.com and was outside scope. |
be-sustainableoptimised-assets | issues | high | The image audit found 20 below-fold images without lazy loading, 19 PNG/legacy-format images, and all 21 without intrinsic dimensions. Image transfer was modest (62 KiB), so this is an efficiency polish issue rather than a weight emergency. F20 low: Below-fold icon assets are not lazily delivered |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 363 KiB unused JavaScript and the tracker capture shows repeated analytics/tag-manager work on a simple help index. F21 medium: Initial load performs avoidable script work |
be-sustainablethird-party-and-media-budget | issues | high | The HAR totals 1.16 MB and 72 requests for a mostly textual portal, including 19 font requests and 13 third-party origins. F22 medium: Third-party and font budget is disproportionate to a help index |
be-agent-readystructured-agent-capabilities | issues | high | Raw support content is fully crawlable, but Lighthouse scored agentic browsing at 0.67 and found no recommended llms.txt; the page exposes no WebMCP or structured agent tool surface. F23 low: Machine-readable support actions are not exposed |
be-agent-readyon-device-inference | not-applicable | medium | No local inference task is required to read, search, or navigate the public help content; the optional assistant implementation was not inspected beyond its entry control. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 menu open/close cycles, heap self-size rose only 176,214 bytes (1.26%) and no Detached* constructors appeared; no unbounded pattern was demonstrated. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap self-size was 13.97MB with 267,426 snapshot nodes, proportionate to the portal and stable after interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction heap summary contained Detached* constructors; repeated menu interaction did not reveal listener/timer accumulation symptoms. |
Provenance
Canonical report: results/atomic/reports/0138-support_google_com.json
Report SHA-256: d916924f7379df6157aafef04937c8cf185573cd33373f51440307ff2b813413
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/support_google_com/2026-07-18T16-43-54-492Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/support_google_com/2026-07-18T16-43-54-492Z
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.