Manifest position 313 · CrUX rank bucket 1000
https://myaccount.google.com
Coverage complete
Coverage complete. Public unauthenticated account marketing, passkey, Sign in with Google, and authentication-entry templates were audited; authenticated account settings and credential submission were not covered.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-emulated screenshot remains the same white surface and the DOM computed color-scheme is normal. F001 medium: The public Google Account pages do not honor the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, matchMedia was true and document.getAnimations() returned no active animations after load. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse accessibility scored 1.0, axe reported no violations, and increased-contrast rendering retained visible text and controls. |
implement-natural-interactionsview-transitions | pass | high | Public route changes are ordinary full navigations; each destination renders a coherent first state with no jarring in-page state swap observed. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling interaction exists on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven control, carousel, swipe action, or scroll-snap surface exists on the audited public templates. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop navigation remains orienting and mobile collapses to a menu while the primary account action stays visible. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned menu was present on the audited states. |
provide-guided-navigationdirects-attention | pass | high | Skip link, selected navigation state, headings, and prominent blue primary actions make destination and focus clear. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | At 360x800 the fixed cookie bar occupies about the bottom 194px and visibly covers the hero copy until consent. F002 high: The fixed cookie notice obscures a substantial part of the mobile hero. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | The only interruption is a simple non-modal cookie bar, not a disclosure, transient popover, or modal flow requiring these primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop and mobile screenshots show restrained navigation and large content-first areas. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout reported scrollWidth 360, clientWidth 360, and horizontalOverflowPx 0 at 360x800. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | The same header, hero, imagery and content columns recompose into a single-column 360px layout without clipping. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Primary buttons are 48-50px tall, a Jump to Content link exists, labels are present, and Lighthouse accessibility scored 1.0. |
support-core-task-successclear-purpose-and-primary-action | pass | high | All three public templates have specific H1s and prominent actions such as Go to Google Account, Create a passkey, and Review your connections. |
support-core-task-successprimary-flow-completion | pass | high | The unauthenticated journey reaches the labelled Google identifier form and passkey/account destinations without a dead end; credential submission was outside audit scope. |
support-core-task-successclear-system-state-and-recovery | pass | high | The public pages clearly distinguish marketing, consent, and sign-in states; browser back remains available and no context loss was observed before credential submission. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 4.9s, TBT 850ms and CLS 0.175 (performance 0.40), outside good ranges; desktop trace LCP was 1.90s. F003 high: Mobile load performance is outside good Core Web Vitals ranges. |
be-fast-and-stablevisual-stability | issues | high | The 360px layout observer recorded CLS 0.1493 at about 4.44s and Lighthouse recorded 0.175. F004 medium: The mobile page shifts visibly after initial layout. |
be-fast-and-stableefficient-main-thread | pass | high | CDP trace found one 51.19ms long task and 1.19ms TBT on desktop, although Lighthouse mobile TBT was 850ms; mobile variability is covered by F003. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 295 requests and 3,388,173 transferred bytes, including 24 fonts/993,856 bytes, 43 fetches/1,861,554 bytes and six render-blocking candidates. F005 high: The content-light landing page ships an excessive request, font, fetch, and decorative-animation payload. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 434,569 script bytes plus 288,298 bytes from Tag Manager; Lighthouse performance was 0.40 on the content-light page. F005 high: The content-light landing page ships an excessive request, font, fetch, and decorative-animation payload. |
be-inclusivenames-roles-labels | pass | high | axe found zero violations (48 passing rule groups), Lighthouse accessibility scored 1.0, images had alt text, and the identifier input had a visible label. |
be-inclusivesufficient-contrast | pass | high | axe found no contrast violation and Lighthouse accessibility scored 1.0; six axe contrast nodes required manual review and remained legible in screenshots. |
be-inclusivestructure-and-focus | pass | high | The DOM has header/nav/main/footer landmarks, one H1 followed by H2s, and a Jump to Content link; Lighthouse accessibility scored 1.0. |
be-inclusivelegible-text | pass | high | Desktop and mobile screenshots show unclipped, readable body text and clear heading hierarchy; reflow remains coherent. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport permits scaling to 5, mobile has no overflow, primary targets are at least 48px high, and the image audit found no missing alt/dimensions. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console returned no items and best-practices scored 1.0. |
follow-best-practicessound-document-and-assets | pass | high | DOCTYPE html and viewport are present; image audit found no missing dimensions, oversized images, missing srcset, legacy formats, or missing alt. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0; no load-time permission prompt or paste-prevention behavior was observed. |
be-discoverabletitle-and-description | pass | high | Overview, passkeys, and Sign in with Google each expose a distinct descriptive title, meta description, and H1. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO scored 0.92 and links/viewport were valid, but the non-JS crawler request received HTTP 429 and only 12% rendered-word overlap. F008 medium: The non-JavaScript crawler path is rate-limited and does not expose the intended marketing content. |
be-discoverablecanonical-and-indexing-signals | pass | high | Browser navigation succeeded after two expected redirects; canonical, robots.txt, and sitemap signals exist and Lighthouse robots/crawlable audits passed. |
be-discoverablestructured-and-shareable-metadata | pass | high | Overview exposes one JSON-LD block and complete Open Graph title/url/description/image metadata aligned with visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, nosniff and a Secure/HttpOnly/SameSite=Lax cookie were present, but the final response audit found no CSP or HSTS. F007 high: Several baseline browser-enforced response defenses are absent on the inspected final page. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker audit found Google Tag Manager and Google Analytics; HAR attributed 102 requests and 3,379,611 bytes to origins classed third-party relative to myaccount.google.com. F006 medium: The unauthenticated account landing page loads a large analytics and cross-origin footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load; passkey education and Create a passkey actions are prominent, and sign-in uses username autocomplete. |
be-private-and-securedefensive-browser-policies | issues | high | Header audit found no CSP/frame protection, HSTS, Referrer-Policy, or Permissions-Policy on the inspected final page response. F007 high: Several baseline browser-enforced response defenses are absent on the inspected final page. |
be-resilientprogressive-enhancement | issues | high | The discoverability non-JS request received 429, exposed 12% word overlap, and lacked raw title/H1/description for the rendered marketing page. F008 medium: The non-JavaScript crawler path is rate-limited and does not expose the intended marketing content. |
be-resilientresilient-runtime-behaviour | pass | high | Representative pages and mobile chrome rendered coherently; no cut-off menu or blank runtime state was observed. |
be-resilientoffline-and-installable | not-applicable | high | This public account marketing/sign-in entry is intrinsically online and is not presented as an installable app. |
be-resilientnetwork-and-http-failure-states | issues | high | The crawler-facing HTTP 429 response provides a generic error payload rather than the intended account content or a useful recovery route. F008 medium: The non-JavaScript crawler path is rate-limited and does not expose the intended marketing content. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The overview reports lang=en-US and dir=ltr, and Google serves localized URL/content variants; layout survived mobile reflow. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public templates contain no dates, currencies, quantities, or other locale-sensitive data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public templates expose no dates, events, schedules, or time-zone-sensitive concepts. |
be-trustworthyno-dark-patterns | pass | high | Cookie consent has neutral Learn more and OK, got it choices; account/passkey actions state their destinations without confirmshaming or disguised ads. |
be-trustworthyhumane-error-handling | pass | medium | The credential form begins with a clearly labelled Email or phone field and a predictable Next action; no invalid submission was made to avoid sending test credentials. |
be-trustworthytrustworthy-input-assistance | pass | high | Identifier input is visibly labelled Email or phone and uses autocomplete=username. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Passkey and account-management entry actions are plainly labelled, and sensitive continuation redirects to Google reauthentication. |
be-sustainableoptimised-assets | pass | high | Image audit found dimensions, srcset, modern served formats and no oversized raster images; three below-fold images were not lazy but are only 160px assets. |
be-sustainableno-wasteful-work | issues | high | A content-light landing page transfers 3.39MB over 295 requests, including 204 image/Lottie requests and 43 fetches. F005 high: The content-light landing page ships an excessive request, font, fetch, and decorative-animation payload. |
be-sustainablethird-party-and-media-budget | issues | high | HAR reports 3.38MB classed third-party, 994KB of fonts and 288KB Tag Manager; the page uses many decorative Lottie assets. F005 high: The content-light landing page ships an excessive request, font, fetch, and decorative-animation payload. F006 medium: The unauthenticated account landing page loads a large analytics and cross-origin footprint. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent actions are not appropriate on a sensitive unauthenticated account and credential entry surface without an explicit safe capability model. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, translation, or inference task is part of these account entry pages. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The unauthenticated marketing page has no representative stateful interaction to repeat; scrolling was not fabricated as a leak test. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap summary measured 539,263 nodes and 25,562,930 self-size bytes on a static marketing page, with 17,464 Float32Arrays and 17,468 ArrayBuffers. F009 medium: The static marketing page starts with a disproportionately large object and graphics footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The baseline heap constructor summary contained no Detached* constructor population; no repeated stateful interaction exists to test accumulation. |
Provenance
Canonical report: results/atomic/reports/0313-myaccount_google_com.json
Report SHA-256: 793ee4034a8b3467273f8eca8ddb43628b575349e2674800fbc064a099bf6280
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/myaccount_google_com/2026-07-27T19-41-18-681Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/myaccount_google_com/2026-07-27T19-41-18-681Z
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.