Manifest position 500 · CrUX rank bucket 1000
https://go.search-start.org
Coverage complete
Atomic coverage complete across the single search landing template, primary redirect flow, and representative 404 recovery path.
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 | Dark-emulated screenshot remains the same white surface as light mode; CSS feature probe found theme declarations but the rendered page did not retint. F01 medium: Dark preference does not produce a dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations; the simple landing state has no auto-advance. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserves visible text, search outline, icons and footer links with system high-contrast colors. |
implement-natural-interactionsview-transitions | issues | medium | The primary search changes from this page to an external results document with no transition treatment; CSS/source probe found no view-transition usage. F02 low: Search navigation swaps documents abruptly |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal, carousel, or other scroll-linked motion exists on this single-view search landing page. |
implement-natural-interactionsphysical-gestures | pass | high | The core interaction is a native text input and Enter-key submission; source inspection found no custom pointermove or gesture implementation fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The core landing viewport does not scroll at 360x800 or desktop, and there is no progress-dependent chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | DOM and source inspection found no tooltip, menu, popover, or transient overlay requiring anchored positioning. |
provide-guided-navigationdirects-attention | issues | high | Four prominent footer destinations (How Search works, Terms, FAQs, About) all use href="#" and do not move users to the promised destination. F03 medium: Footer navigation promises destinations but goes nowhere |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial desktop and mobile screenshots show the search task unobscured, with no load-time modal, banner, or interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | DOM probe found zero dialog, popover, or details surfaces and the page presents no overlay control. |
maximize-content-reduce-noisereduced-chrome | issues | high | The simple search landing loads a large recommendation/advertising feed: the rendered DOM text contains dozens of Taboola-style headlines and Lighthouse measured a 2,852px mobile body. F04 medium: Advertising recommendations overwhelm a minimal search task |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x500 viewport, layout reported 500px content width and 140px horizontal overflow; the short-height media query hard-codes the search UI to 500px. F05 high: Short mobile viewports force a 500px desktop layout |
adapt-to-the-form-factorcomponent-level-responsiveness | not-applicable | medium | The page has no reused component rendered in materially different containers; its one search shell is page-level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused search input computes outline:none, border:0 and box-shadow:none; several footer links are only about 35.5px high, below a comfortable touch target. F06 high: Keyboard focus is invisible and targets are undersized |
support-core-task-successclear-purpose-and-primary-action | pass | medium | First-viewport screenshots show a conventional search logo and a single visually dominant search field with no competing primary CTA. |
support-core-task-successprimary-flow-completion | pass | high | Loading the supported q=modern web flow redirected end-to-end to a Yahoo results URL carrying the query and rendered a retry-capable search-results state. |
support-core-task-successclear-system-state-and-recovery | issues | high | A representative unknown URL returns a generic Cloudflare R2 bucket-owner 404 with only an external Public Access documentation link and no route back to search. F07 medium: The 404 state strands users in storage-provider diagnostics |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.3s and TTI 8.4s (performance 0.69), despite low CLS; trace corroborated a 2.07s LCP in a separate warm/desktop-style run, so load speed is variable and poor under Lighthouse mobile conditions. F08 high: Mobile load is too slow and variable |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0.0002 desktop, 0.017 at 360x800 and 0.032 at 360x500; Lighthouse CLS was 0.046, all within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms TBT; layout observers also recorded no long tasks, while Lighthouse TBT was 80ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 41 requests/727KB with parser-blocking Bootstrap and local CSS plus a non-deferred head script; Lighthouse estimated 1,040ms render-blocking savings and 93KiB cache savings. F09 high: Render-blocking and cache policy delay the small page |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 172KiB unused Taboola JavaScript and 38KiB unused CSS, including 97% of Bootstrap. F10 medium: Most shipped framework and ad code is unused |
be-inclusivenames-roles-labels | issues | high | Lighthouse found the search input has no label/name and the logo image has no alt attribute; DOM also found no main landmark. F11 high: Core search UI lacks accessible names and semantics |
be-inclusivesufficient-contrast | issues | high | Lighthouse found repeated ad-branding text at 2.84:1 contrast (#999 on white), below the 4.5:1 minimum for 11px text. F12 medium: Advertising attribution text fails contrast |
be-inclusivestructure-and-focus | issues | high | The page has no headings or main landmark, and the focused search input has no visible outline, border or shadow. F13 high: Page structure and focus indication are missing |
be-inclusivelegible-text | pass | medium | Desktop, mobile and forced-color screenshots show core search and footer text without clipping at standard portrait sizes; text remains readable. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360x500 reflow condition overflows horizontally by 140px and footer targets are about 35.5px high; the viewport itself permits scaling. F14 high: Reflow and target sizing fail on a common narrow condition |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 with no error rows. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8/viewport are valid, but the 1692px-wide PNG logo renders at 65px without width/height attributes; image audit reports seven unsized image elements. F15 low: Logo asset is unsized and grossly oversized |
follow-best-practicesbrowser-platform-hygiene | issues | high | Source contains duplicate id="lucky_button" controls and a malformed unitless max-width media query; Lighthouse also reported inspector issues and legacy JavaScript savings. F16 low: Markup and CSS contain avoidable structural defects |
be-discoverabletitle-and-description | issues | high | The title is only “Search” and no meta description exists in rendered or raw HTML; Lighthouse meta-description audit failed. F17 medium: Search result snippet metadata is weak |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport and robots are valid, but four descriptive footer labels resolve only to the same-page # fragment rather than crawlable destination content. F18 medium: Prominent informational links are not crawlable destinations |
be-discoverablecanonical-and-indexing-signals | issues | high | The public page returns 200 and robots allows search, but it has no canonical URL and /sitemap.xml returns 404. F19 medium: Canonical and sitemap signals are absent |
be-discoverablestructured-and-shareable-metadata | issues | high | DOM probe found zero JSON-LD blocks and no Open Graph metadata, leaving this public search product without a reliable share preview or organization/site entity description. F20 low: Share and entity metadata is absent |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used and no first-party cookies were found, but CSP, HSTS and X-Content-Type-Options are all absent. F21 high: Foundational security headers are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker audit found 10 third-party origins and eight known tracker hosts; HAR recorded 35 third-party requests and 411KB, including Taboola/Criteo event and sync traffic. F22 high: Tracking footprint is disproportionate to the search task |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication flow or permission request is part of this public search landing page; Notification remained default and no prompt appeared. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no clickjacking defense, Referrer-Policy or Permissions-Policy in addition to missing HSTS/CSP. F23 high: Browser-enforced defenses are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 100% rendered-word coverage in raw HTML, no JS shell, and equivalent core landing content without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | The suggestion box is manually absolutely positioned with invalid unitless offsets, while the 360x500 condition expands layout to 500px; this is fragile near viewport edges. F24 medium: Suggestion overlay positioning is brittle |
be-resilientoffline-and-installable | not-applicable | high | This search gateway is intrinsically online and exposes neither a manifest nor an active service-worker controller. |
be-resilientnetwork-and-http-failure-states | issues | high | Unknown routes show storage-provider diagnostics and no recovery to the product; the tested external results state did at least offer a search-again control. F07 medium: The 404 state strands users in storage-provider diagnostics |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The document declares html lang="en" and the CSS feature probe found logical-property usage; no conflicting direction was present. |
be-internationalisedlocale-aware-data | not-applicable | high | The page renders no dates, numbers, currencies, durations, or calendar data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The page has no event or time data. |
be-trustworthyno-dark-patterns | issues | high | The core search page initializes Taboola/Criteo tracking and can inject a long feed of sensational recommendation headlines beneath the task, while no consent or preference surface appeared. F25 high: Recommendation and tracking behavior is not transparent or user-controlled |
be-trustworthyhumane-error-handling | not-applicable | high | The only input is a free-text search field with no constrained validity or required-field error state. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The site collects no address, payment, account, or other autofill-appropriate personal information. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent choice, authentication, or account-management flow exists. |
be-sustainableoptimised-assets | issues | high | The 1692×2358 PNG logo is displayed at 65×90 and transfers about 106KB; Lighthouse estimated about 106KB savings for it and 148KiB total image-delivery savings. F26 medium: The logo wastes image bytes |
be-sustainableno-wasteful-work | issues | high | A minimal search shell makes 41 requests; 35 are third-party and Lighthouse found 172KiB unused Taboola JavaScript plus 38KiB unused CSS. F27 medium: Background advertising work dominates a tiny page |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 411KB across 35 requests, over half the 727KB transfer, dominated by advertising/tracking scripts rather than the search task. F28 high: Third-party bytes are disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | The emerging WebMCP surface was absent and this externally redirected search gateway exposes no safe site-owned action beyond a simple crawlable input. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or other inference task is presented where on-device AI would clearly improve this minimal gateway. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten focus/type/input/blur/clear cycles, heap self-size decreased from 9,719,098 to 9,710,411 bytes and node count decreased from 167,590 to 167,488. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary measured about 9.7MB self-size for the loaded state; despite third-party code, the captured footprint remained bounded and did not grow in the exercised session. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries contained no Detached* constructor among reported constructors, and aggregate node/closure counts did not grow after repeated interaction. |
Provenance
Canonical report: results/atomic/reports/0500-go_search-start_org.json
Report SHA-256: 94e2b281993cee71b7a76f167c901deddf5be21b8393a1fea5223f62e8af5dee
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/go_search-start_org/2026-07-21T05-21-25-940Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/go_search-start_org/2026-07-21T05-21-25-940Z
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.