Manifest position 146 · CrUX rank bucket 1000

https://www.google.com

Partial after retries

The homepage was inspected across visual, responsive, accessibility, performance, network, security, crawler, and memory conditions, but the representative search-results journey redirected to Google’s unusual-traffic reCAPTCHA. One atomic check is blocked, so this 57/58 run is partial and has no score.

Attempts

3 / 3

Judged checks

57 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Evaluate probes under prefers-color-scheme: light and dark both returned body background rgb(34, 36, 42) and text rgb(232, 232, 232); the light and dark screenshots are byte-identical. WU-GOOGLE-001 medium: The page stays dark even when the browser explicitly requests a light color scheme.
respect-user-preferences `respects-reduced-motion`	pass	high	Under prefers-reduced-motion: reduce, the probe matched the media query and found zero running document animations.
respect-user-preferences `respects-contrast`	pass	high	Lighthouse’s color-contrast audit passed, and the prefers-contrast: more screenshot retained readable text and controls.
implement-natural-interactions `view-transitions`	pass	high	CSS inspection found view-transition usage on the homepage; no running animation blocked or obscured the core search state.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	The inspected homepage and blocked search response have no scroll-linked storytelling, parallax, carousel, or reveal interaction to implement.
implement-natural-interactions `physical-gestures`	not-applicable	high	No custom swipe, pull, drag, carousel, or other gesture-driven surface exists on the representative public paths.
provide-guided-navigation `scroll-state-aware-chrome`	not-applicable	high	The homepage is a single-viewport search surface with no meaningful scrolling chrome; the search-results archetype was externally blocked.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, anchored menu, or edge-sensitive popover is present on the inspected homepage.
provide-guided-navigation `directs-attention`	pass	high	The first viewport centers the Google mark and the single search field; search has a clear accessible name and the consent state presents explicit equal-choice actions.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	The desktop screenshot shows a modal covering nearly the full viewport before interaction; the DOM probe identifies an aria-modal=true consent dialog over the search form. WU-GOOGLE-002 high: A consent interstitial obscures the primary search experience on initial load.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The DOM/evaluate probe reports the visible consent surface as DIV role=dialog aria-modal=true, while the only native DIALOG belongs to a separate hidden voice-search surface. WU-GOOGLE-003 medium: The active consent modal is implemented as a div with ARIA rather than the native dialog primitive.
maximize-content-reduce-noise `reduced-chrome`	pass	high	Outside the consent state, the inspected page is a sparse search surface with one dominant field and minimal surrounding chrome.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	The mobile layout capture reports no viewport meta and a 980 CSS-pixel layout viewport scaled to about 0.367 inside a 360px device viewport; the full-page screenshot shows tiny desktop navigation and controls. WU-GOOGLE-004 high: The desktop document is scaled down rather than genuinely reflowing at a 360px viewport.
adapt-to-the-form-factor `component-level-responsiveness`	not-applicable	high	The inspected homepage does not reuse a component in materially different container contexts; viewport responsiveness is judged separately.
adapt-to-the-form-factor `input-modality-aware`	issues	high	After focusing the search textarea, the evaluate probe returned outline "none" and box-shadow "none"; several visible search buttons are only 36 CSS pixels high. WU-GOOGLE-005 high: Keyboard focus on the primary search field has no visible focus indicator.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The Google brand, centrally placed search field labelled Search, and Google Search action make the page purpose and next action unambiguous.
support-core-task-success `primary-flow-completion`	blocked	high	Direct navigation to https://www.google.com/search?q=web+platform redirected to /sorry/ with unusual-traffic reCAPTCHA. The auditor cannot solve the external CAPTCHA, so end-to-end search completion is blocked.
support-core-task-success `clear-system-state-and-recovery`	pass	high	The unusual-traffic response clearly explains why search cannot continue, provides a reCAPTCHA recovery action, and links to more explanation.
be-fast-and-stable `good-core-web-vitals`	pass	high	Lighthouse measured LCP 1.8s, CLS 0, and TBT 0ms (performance 0.99); the CDP trace measured LCP 2.60s and TBT 6.44ms.
be-fast-and-stable `visual-stability`	pass	high	The homepage mobile layout observer recorded CLS 0 with no shifts; Lighthouse independently measured CLS 0.
be-fast-and-stable `efficient-main-thread`	pass	high	The trace recorded one 56.44ms long task and 6.44ms total blocking time; Lighthouse measured TBT 0ms.
be-fast-and-stable `efficient-resource-delivery`	pass	high	The HAR recorded no HTTP errors; Lighthouse LCP was 1.8s and the trace showed only 6.44ms blocking time, despite a short parser-inserted dependency chain.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	The HAR reports 706,075 transferred script bytes out of 805,494 total bytes. Lighthouse estimates 56KiB unused JavaScript and 11KiB unused CSS. WU-GOOGLE-007 medium: The simple search landing page ships a disproportionately large JavaScript payload with measurable unused code.
be-inclusive `names-roles-labels`	pass	high	Lighthouse image-alt and button-name audits passed; the search textarea has aria-label Search, links have text, and the consent surface exposes dialog semantics.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse’s basic color-contrast audit passed, while its separate link-in-text-block audit found the consent “cookies” link only 1.47:1 against surrounding text and not otherwise distinguished.
be-inclusive `structure-and-focus`	issues	high	The focused search textarea is the activeElement but its computed outline is none and box-shadow is none. The generic first focusable link probe also returned no outline. WU-GOOGLE-006 high: The primary keyboard focus state is not visually perceivable.
be-inclusive `legible-text`	issues	high	Lighthouse failed link-in-text-block: the consent “cookies” link has 1.47:1 contrast against surrounding text and no underline or other non-color distinction. WU-GOOGLE-008 low: At least one text link relies on color alone to be distinguishable.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	At 360x800, layout metrics expose a 980px CSS layout viewport and no viewport meta, producing a 0.367 visual scale and very small desktop text and links. WU-GOOGLE-009 medium: The narrow-viewport experience uses shrink-to-fit instead of accessible reflow.
follow-best-practices `no-console-errors`	pass	high	Lighthouse errors-in-console passed with no browser errors.
follow-best-practices `sound-document-and-assets`	pass	high	The document has HTML doctype and UTF-8 charset; Lighthouse doctype/charset passed and images caused no observed CLS.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse passed deprecations, BFCache, third-party-cookie, console-error, and inspector-issues audits; no prompt appeared on load.
be-discoverable `title-and-description`	issues	high	The DOM probe returned description=null and Lighthouse failed the meta-description audit. The title is present as "Google". WU-GOOGLE-010 low: The public homepage has no meta description.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Links are crawlable and robots.txt is valid, but the homepage has no viewport meta; at a 360px device viewport Chrome used a 980 CSS-pixel layout viewport and scaled it to 0.367. WU-GOOGLE-018 high: The homepage omits viewport metadata and is shrink-to-fit rather than mobile-friendly.
be-discoverable `canonical-and-indexing-signals`	issues	medium	https://google.com/ redirects to https://www.google.com/, but the rendered DOM probe reports canonical=null. robots.txt is valid and the document returns 200 after the redirect. WU-GOOGLE-011 low: The homepage redirect target does not expose an explicit canonical URL.
be-discoverable `structured-and-shareable-metadata`	issues	medium	The DOM/evaluate evidence contains no JSON-LD, Open Graph metadata, or equivalent structured description for the Google Search/Organization entity. WU-GOOGLE-012 low: The homepage exposes no structured entity or social-preview metadata in the inspected DOM.
be-private-and-secure `secure-transport-and-headers`	issues	high	The headers primitive confirms HTTPS and X-Frame-Options SAMEORIGIN, but reports missing Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, and Referrer-Policy. WU-GOOGLE-013 high: The inspected main document omits several baseline security response headers.
be-private-and-secure `data-minimisation-and-third-parties`	issues	medium	The initial-load HAR includes play.google.com/log requests and requests to ogads-pa.clients6.google.com while the screenshot still shows the unresolved consent dialog. The tracker matcher found no known tracker domain, so the classification is medium-confidence rather than asserting ad tracking. WU-GOOGLE-014 medium: The page performs background logging and async-data requests before the user resolves the consent modal.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	No permission prompt fires on the public homepage; authentication is a separate linked account journey outside the representative public search scope.
be-private-and-secure `defensive-browser-policies`	issues	high	The headers capture finds clickjacking protection and Permissions-Policy unload=(), but no HSTS, CSP/frame-ancestors policy, Referrer-Policy, or X-Content-Type-Options. WU-GOOGLE-015 high: Browser-enforced defensive policy coverage is incomplete.
be-resilient `progressive-enhancement`	pass	high	The no-JavaScript crawler screenshot still exposes the Google search field, buttons, navigation, and footer; the raw page is not a JS shell despite only 11% token overlap with the richer rendered consent state.
be-resilient `resilient-runtime-behaviour`	pass	high	The consent modal remains contained within the viewport, controls stay visible, and no runtime or inspector errors were reported.
be-resilient `offline-and-installable`	not-applicable	high	Public web search is intrinsically network-dependent and the homepage is not presented as an installable app.
be-resilient `network-and-http-failure-states`	pass	high	The anti-abuse response gives a clear explanation, a CAPTCHA recovery route, and help text rather than a blank screen or spinner.
be-internationalised `lang-dir-and-logical-properties`	pass	high	The document declares lang=en-GB and resolves to ltr; it exposes a language control and locale-specific UK links/content.
be-internationalised `locale-aware-data`	not-applicable	high	The inspected search landing surface contains no dates, currencies, durations, or other locale-sensitive data values.
be-internationalised `time-zone-correctness`	not-applicable	high	The inspected search landing surface contains no scheduling or time-zone-sensitive concepts.
be-trustworthy `no-dark-patterns`	pass	high	Reject all and Accept all are presented with equal visual weight, More options is available, and pricing/continuity pressure is absent on the public page.
be-trustworthy `humane-error-handling`	not-applicable	high	The homepage search field has no format or required-field error state; the externally imposed CAPTCHA is not authored validation for this form.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	The sole user-entered field is an open-ended search query; address, payment, sign-in, and identity autocomplete tokens do not apply.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No checkout, subscription, purchase, consent-to-payment, or account-management flow exists in the selected public search journey.
be-sustainable `optimised-assets`	pass	high	Only 973 transferred image bytes were recorded; the sole loaded external image is a 24px SVG and no oversized image was reported.
be-sustainable `no-wasteful-work`	issues	high	The HAR records 42 requests and 805,494 transferred bytes, including 706,075 bytes of JavaScript; Lighthouse estimates 56KiB unused JavaScript and 11KiB unused CSS. WU-GOOGLE-016 medium: Initial resource use is heavy for a single-field search landing page.
be-sustainable `third-party-and-media-budget`	pass	high	No video/audio/autoplay media was present, known trackers were zero, and image transfer was under 1KB; same-company redirect origins account for most nominal third-party bytes.
be-agent-ready `structured-agent-capabilities`	issues	medium	The evaluate probe reports navigator.modelContext absent and no agentic form/tool annotations, despite search being a clear, bounded capability suitable for structured invocation. WU-GOOGLE-017 low: The core search form is not exposed as a structured agent capability.
be-agent-ready `on-device-inference`	not-applicable	high	The inspected core task is remote web search; no summarisation or language-model task on this surface clearly benefits from built-in on-device inference.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten search-field focus/type/clear/blur cycles, heap self-size rose from 15,104,138 to 15,387,476 bytes (1.9%) and heap nodes from 349,526 to 352,718 (0.9%), a bounded two-snapshot change.
be-memory-efficient `bounded-footprint`	pass	high	The homepage heap is about 15.1MB self-size with 349,526 heap nodes; the DOM probe counted 502 elements, proportionate to this interactive landing page.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	After ten repeated input cycles, heap node growth was under 1%; no evidence of unbounded listener/timer or detached-DOM accumulation appeared in the bounded comparison.

Provenance

Canonical report: results/atomic/reports/0146-www_google_com.json
Report SHA-256: 15f8c584e5022993fb8900c1e0ba572bf0bbd60a4896dd839290c7c442503f25
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_google_com/2026-07-27T15-59-33-931Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_google_com/2026-07-27T15-59-33-931Z
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.