Manifest position 657 · CrUX rank bucket 1000
https://www.google.com.hk
Partial after retries
57 of 58 checks judged; primary-flow-completion was blocked by Google unusual-traffic reCAPTCHA.
Attempts
3 / 3
Judged checks
57 / 58
Blocked
1
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 | pass | high | Light and dark emulation screenshots both show a coherent dark surface; the site adapts to the browser condition without illegible controls. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, the active probe found zero running document animations. |
respect-user-preferencesrespects-contrast | pass | high | Under prefers-contrast: more, primary controls and text remained present and usable; Lighthouse found only an inline-link distinction issue recorded separately under inclusive contrast. |
implement-natural-interactionsview-transitions | issues | high | Platform and DOM probes found no view-transition declaration on observed state/navigation surfaces. F002 low: Primary state and document changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the audited search and form templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven carousel, swipe, pull-to-reveal or comparable physical interaction exists in the audited core paths. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The audited homepage and advanced-search form have no long scrolling chrome whose state needs to react to scrolling. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, transient menu or edge-positioned anchored overlay was part of the exercised core states. |
provide-guided-navigationdirects-attention | pass | high | The homepage centers the search control and Advanced Search groups fields under explicit headings and labels; screenshots show a clear reading path. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Initial screenshots show the consent dialog obscuring the primary page until a choice is made. F001 medium: The consent dialog interrupts and obscures the primary search task on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | The initial consent surface is implemented as a native dialog and exposes explicit Reject all and Accept all actions. |
maximize-content-reduce-noisereduced-chrome | pass | high | Homepage and advanced-search screenshots devote the main viewport to the search task with minimal persistent navigation chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360px viewport, the page uses a 980px layout viewport scaled to 0.367 because viewport meta is absent. F003 high: The homepage omits a viewport meta tag, so a 360px device receives a 980px layout scaled down to 0.367. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container-query rules were found; Advanced Search computed a fixed 484px form width. F004 low: Observed layouts do not use component-level container responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused search textarea has no outline or shadow and multiple controls are below 44px. F005 high: Keyboard focus is not visibly indicated on the primary search field, and several targets are below 44px. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The Google search input and search actions dominate the first viewport; Advanced Search has a descriptive H1 and grouped controls. |
support-core-task-successprimary-flow-completion | blocked | high | Search submission was attempted, but Google returned an unusual-traffic reCAPTCHA page, preventing end-to-end result-flow judgement from this environment. |
support-core-task-successclear-system-state-and-recovery | pass | high | The unusual-traffic response clearly explains the blocker, presents reCAPTCHA, and links to an explanation rather than showing a blank or misleading state. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 1.3s, CLS 0 and TBT 0ms; trace corroborated CLS 0 and only 9.51ms TBT. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer and Lighthouse both measured CLS 0 with no recorded shifts. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found one 59.51ms task and 9.51ms TBT; Lighthouse measured 0ms TBT. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR/Lighthouse show 700KB script transfer plus network dependency and render-blocking opportunities. F006 low: The minimalist homepage still transfers 700KB of JavaScript and retains avoidable render-path work. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 56KiB unused JavaScript and 11KiB unused CSS. F007 low: The page ships measurable unused JavaScript and CSS. |
be-inclusivenames-roles-labels | pass | high | Lighthouse accessibility scored 0.96; the primary textarea has aria-label Search and submit controls have explicit accessible labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed link-in-text-block, indicating inline links are not sufficiently distinguishable. F008 medium: Some inline links do not maintain sufficient distinguishability from surrounding text. |
be-inclusivestructure-and-focus | issues | high | Probe found no main landmark and no visible focus indication on the primary search textarea. F009 high: The homepage lacks a main landmark and a visible focus treatment on the primary field. |
be-inclusivelegible-text | pass | high | Desktop and advanced-search screenshots show unclipped, readable headings, labels and body text at the rendered desktop condition. |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta, 0.367 mobile scaling, and multiple sub-44px targets were observed. F010 high: Zoom/reflow and target sizing are undermined by the missing viewport declaration and undersized controls. |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices scored 1.0 and reported no console-error or uncaught-exception audit failure. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but all seven img elements omit intrinsic dimensions and Lighthouse flags unsized images. F011 low: Images omit intrinsic width and height attributes. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0; probes found no paste prevention or permission prompt on load. |
be-discoverabletitle-and-description | issues | high | Title is Google, but meta description is absent and Lighthouse fails meta-description. F012 medium: The homepage has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Real href links and permissive robots are present, but viewport meta is absent. F013 medium: Mobile crawlability quality is reduced by the missing viewport meta tag. |
be-discoverablecanonical-and-indexing-signals | issues | high | HTTP 200 and robots allow the localized homepage, but no canonical or hreflang signal was found. F014 low: Localized homepage indexing signals omit canonical and hreflang declarations. |
be-discoverablestructured-and-shareable-metadata | issues | high | No JSON-LD or Open Graph metadata was found for the public organization/search entity. F015 low: The public organization/search homepage exposes no structured or social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and secure cookies pass, but CSP, HSTS, nosniff and Referrer-Policy are absent. F016 high: The main document lacks several baseline defensive response headers. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | The consent copy explains measurement/personalisation, Reject all is equally prominent, cookies are first-party Secure/HttpOnly/SameSite=Lax, and no known tracker domain was detected. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No geolocation/notification prompt occurred on load; authentication is linked as a separate explicit Sign in journey. |
be-private-and-securedefensive-browser-policies | issues | high | SAMEORIGIN and Permissions-Policy exist, but CSP/HSTS/nosniff/referrer defenses are absent. F017 high: Browser-enforced defenses are incomplete. |
be-resilientprogressive-enhancement | pass | high | The crawler screenshot with JavaScript disabled still exposes the core search input, buttons, navigation and footer; the page is not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | The native consent dialog remains contained at desktop and mobile conditions; defer/async probes show initial scripts are sequenced without a broken shell. |
be-resilientoffline-and-installable | not-applicable | high | Public web search is intrinsically network-dependent; an installable/offline result experience is not a reasonable requirement for this surface. |
be-resilientnetwork-and-http-failure-states | pass | high | The anti-automation failure state is explicit, explains unusual traffic, offers reCAPTCHA recovery and a diagnostic link. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang is en-GB, but probes show 238 physical left/right declarations and no observed logical inline/block styles. F018 low: The localized UI relies heavily on physical directional CSS rather than logical properties. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited surfaces render no dates, currencies, durations or locale-sensitive numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited surfaces contain no events, stored times or time-zone-sensitive scheduling. |
be-trustworthyno-dark-patterns | pass | high | Consent presents Reject all and Accept all side by side with equal visual weight and explains each data-use choice. |
be-trustworthyhumane-error-handling | not-applicable | high | The observed search and advanced-search fields have no required validation constraints; no invalid-input state exists to exercise. |
be-trustworthytrustworthy-input-assistance | pass | high | Search deliberately uses autocomplete=off for query privacy/prediction behavior; no address, payment or sign-up fields requiring autofill occur on audited forms. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or account-management flow is hosted on the audited public search surfaces. |
be-sustainableoptimised-assets | pass | high | HAR records only 973 image bytes, SVG for the loaded logo, and the images probe found no oversized raster or legacy-format asset. |
be-sustainableno-wasteful-work | issues | high | A minimalist search form transfers 700KB script; Lighthouse identifies 67KiB combined unused JS/CSS. F019 medium: Script weight and unused code are disproportionate to the simple search landing surface. |
be-sustainablethird-party-and-media-budget | issues | high | Eight third-party requests transfer 90,624 bytes, mostly gstatic supporting code. F020 low: Third-party and supporting-origin resources add about 90KB to the initial page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No explicit agent-facing transactional capability is declared for these public search/form surfaces; this emerging capability is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No audited task calls for site-authored on-device inference; browser AI globals alone do not show site usage. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative query input/clear cycles, heap totals rose modestly from 15,048,896 to 15,336,503 bytes (1.9%) and 348,251 to 351,630 nodes; no unbounded trend is shown in this bounded test. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap summary reports 15.0MB self size and 348,251 nodes, proportionate to this script-heavy search application. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The ten-cycle input exercise produced only 1.9% heap growth and 0.97% node growth; no escalating detached/listener symptom appeared in the bounded comparison. |
Provenance
Canonical report: results/atomic/reports/0657-www_google_com_hk.json
Report SHA-256: 6ac199e5d202b81f93be20de7dbb7cfb7df4e7ccace1a515094a5243f9c6a897
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_google_com_hk/2026-07-28T04-08-40-521Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_google_com_hk/2026-07-28T04-08-40-521Z
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.