Manifest position 359 · CrUX rank bucket 1000
https://www.bikewale.com
Coverage complete
Coverage-complete representative audit of six paths. Excluded: login/account, used-bike sale, dealership lead submission, checkout-like lead completion, and individual article pages because they require identity/location or duplicate audited templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark emulation retints the home page, but the EMI calculator remains a white legacy layout under prefers-color-scheme: dark. BW-001 medium: Theme support is inconsistent across templates |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, matchMedia was true and getAnimations() returned no running animations. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found seven contrast failures, including 4.03:1 EV badges, 3.69:1 Install Now text, and 4.24:1 review text. BW-002 medium: Dark-theme text and controls miss contrast requirements |
implement-natural-interactionsview-transitions | issues | high | CSS/DOM feature probe found no view-transition declarations or startViewTransition usage across the home template. BW-003 low: Route and state changes do not use view transitions |
implement-natural-interactionsscroll-driven-animations | issues | high | Feature probe found no animation-timeline, scroll-timeline, or view-timeline usage while the page presents multiple horizontal tracks. BW-004 low: Scrollable presentations rely on clipped tracks without modern scroll-linked feedback |
implement-natural-interactionsphysical-gestures | issues | high | Feature probe found no scroll-snap or overscroll-behavior; mobile screenshots show partially clipped cards and tabs. BW-005 medium: Horizontal bike tracks lack native gesture containment and snapping |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots show persistent navigation and clear active tab indicators across home/listing/detail paths. |
provide-guided-navigationanchored-positioning | issues | high | The 360 px product screenshot shows the ad, EMI card, offer button, AI strip, and controls overlapping; no anchor positioning or position-try usage was found. BW-006 medium: Floating detail-page UI collides at the viewport edge |
provide-guided-navigationdirects-attention | pass | high | Screenshots show headings, active tabs, and a prominent primary search or calculator action. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | On the TVS iQube mobile detail page, an ad and multiple floating controls overlap the product image, price card, offer action, and each other. BW-007 high: Advertising and floating prompts obstruct the primary product content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Lighthouse reports a role=button whose aria-label is [object Object], while DOM probes found no dialog or popover primitives. BW-008 medium: Expandable and floating controls use custom semantics |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile product viewport devotes most visible space to an ad, floating EMI panel, tabs, offer button, AI prompt, and icons rather than product information. BW-009 high: Chrome and monetisation overwhelm the product detail surface |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout measurements at 360 px found overflow of 126 px home, 81 px listing, 95 px detail, 84 px news, and 600 px EMI calculator. BW-010 high: Every representative mobile template overflows horizontally |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Feature probe found no container queries; the EMI calculator remains 960 px wide in a 360 px viewport and product widgets overlap. BW-011 high: Components do not adapt to their available width |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found inputs and buttons with outline none 0px and no box-shadow, including Search and check-price buttons. BW-012 medium: Several interactive controls have no visible keyboard focus |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home first viewport states “Find the right bike” with a prominent search; listing/detail/calculator H1s state their purpose. |
support-core-task-successprimary-flow-completion | issues | high | At 360 px the calculator is 600 px wider than the viewport; headings, explanatory text, term options, and results area are cut off. BW-013 high: The EMI calculation journey is clipped on mobile |
support-core-task-successclear-system-state-and-recovery | pass | high | The exercised 404 returns HTTP 404, explains the missing page, and offers Back to Home plus useful links. |
be-fast-and-stablegood-core-web-vitals | issues | high | The mobile listing layout observer measured CLS 0.617 across four shifts; Lighthouse home LCP was 3.02 s and TBT 198 ms. BW-014 high: The listing template has severe layout instability |
be-fast-and-stablevisual-stability | issues | high | Layout evidence records four listing shifts between 1.42 s and 1.52 s, totalling CLS 0.617; all 100 audited images lacked width/height attributes. BW-015 high: Late listing content causes large visual shifts |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded two long tasks up to 98.86 ms and 87.74 ms TBT; mobile layout runs also recorded repeated 50-90 ms tasks. BW-016 medium: Script execution creates avoidable blocking work |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 95 requests and 1.93 MB transferred, including 62 scripts/1.61 MB; 91 requests and 1.86 MB were classified third-party. BW-017 high: The page ships a large, script-heavy dependency graph |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 533 KiB unused JavaScript and 41 KiB unused CSS, including multiple vendor bundles with 80-99% waste. BW-018 high: More than half a megabyte of JavaScript is unused on load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an accessible-name mismatch where View More Brands exposes aria-label="[object Object]"; the EMI probe found multiple unlabeled text, radio, textarea, and select controls. BW-019 high: Accessible names and labels are incomplete |
be-inclusivesufficient-contrast | issues | high | Lighthouse enumerated seven color-contrast failures from 3.69:1 to 4.24:1. BW-020 medium: Several dark-theme elements fail WCAG AA contrast |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark; focus probing found multiple buttons/inputs with no visible outline or shadow. BW-021 high: Main landmark and focus indication are incomplete |
be-inclusivelegible-text | pass | high | Representative screenshots show readable body sizing and clear heading hierarchy; metadata probes found one H1 on each path. |
be-inclusivezoom-reflow-targets-and-media | issues | high | All five templates overflow at 360 px, with the EMI calculator overflowing by 600 px despite a zoom-permitting viewport meta tag. BW-022 high: Content does not reflow at narrow/zoom-equivalent widths |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 with no items. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 100/100 images missing width and height and 72 below-fold images without lazy loading; one image lacked alt text. BW-023 medium: Images omit intrinsic dimensions and lazy-loading hints |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found the page ineligible for bfcache because the main resource and a JavaScript request use Cache-Control: no-store. BW-024 medium: Cache policy prevents back/forward cache restoration |
be-discoverabletitle-and-description | pass | high | All five representative DOM captures have distinct titles, descriptions, and one H1. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Home has 234 href-bearing links, viewport metadata, robots.txt, and 97% raw-HTML content coverage. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home exposes a canonical URL; robots.txt and sitemap.xml respond, and the tested missing route returns HTTP 404. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home probe found one JSON-LD block and six Open Graph tags. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers include HSTS/nosniff, but CSP allows unsafe-inline and unsafe-eval; cookie audit found four cookies without Secure and many SameSite=None cookies. BW-025 high: CSP and cookie flags weaken an otherwise strong HTTPS baseline |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found nine third-party origins including GTM and DoubleClick; HAR attributes 91 requests and 1.86 MB to third-party origins. BW-026 high: The landing page has a large analytics and third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load across audited public paths; authentication was not required for their core tasks. |
be-private-and-securedefensive-browser-policies | issues | high | CSP permits scripts from any origin plus unsafe-inline and unsafe-eval; several long-lived cookies use SameSite=None. BW-027 medium: Defensive policy is undermined by permissive script execution |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 97% content coverage in raw HTML and isJsShell=false. |
be-resilientresilient-runtime-behaviour | issues | high | Product detail overlays collide and obscure each other at 360 px, with no anchor positioning fallback detected. BW-028 medium: Floating runtime UI is not resilient to a narrow viewport |
be-resilientoffline-and-installable | issues | high | The manifest is complete with icons, shortcuts and standalone display, but navigator.serviceWorker.getRegistrations() returned an empty array. BW-029 medium: Install metadata exists but no service worker is registered |
be-resilientnetwork-and-http-failure-states | pass | high | The exercised invalid URL returns a clear 404 state with recovery navigation. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page declares lang=en, but the CSS probe found physical left/right properties and no logical properties; the header exposes language selection. BW-030 medium: Internationalisation relies on physical CSS despite language switching |
be-internationalisedlocale-aware-data | pass | high | Audited pages declare lang=en and present Indian rupee prices and Indian-number grouping consistently. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative pages contain no event scheduling or user-facing time-zone conversion. |
be-trustworthyno-dark-patterns | issues | high | The product mobile screenshot layers an ad, Get July Offers action, EMI card, and AI prompt over the product surface. BW-031 medium: Competing offer and ad UI makes intent hard to distinguish |
be-trustworthyhumane-error-handling | issues | high | The EMI page uses unlabeled controls, radio inputs without label association, no required attributes, and only one aria-live region. BW-032 medium: Calculator inputs lack robust semantic validation support |
be-trustworthytrustworthy-input-assistance | issues | high | Most public inputs have empty autocomplete values, while several EMI controls have no names or labels. BW-033 medium: Relevant inputs omit autocomplete semantics |
be-trustworthysafe-commercial-and-account-flows | issues | high | On the product detail path, price/offer controls and content overlap with ads and floating widgets, reducing confidence in the next action. BW-034 high: Commercial product actions are obscured on mobile |
be-sustainableoptimised-assets | issues | high | Image audit found 57 oversized images, 17 without srcset, four legacy-format assets, and all 100 without intrinsic dimensions. BW-035 high: Image delivery is not consistently right-sized or dimensioned |
be-sustainableno-wasteful-work | issues | high | HAR shows 62 scripts and trace shows two long tasks; Lighthouse estimates 533 KiB unused JavaScript. BW-036 medium: Optional scripts create avoidable transfer and main-thread work |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributes 1.86 MB of 1.93 MB and 91 of 95 requests to third-party origins, led by CDN bundles and Google tags. BW-037 high: Third parties dominate page transfer |
be-agent-readystructured-agent-capabilities | issues | high | The public task-heavy marketplace exposes structured metadata but the probe found no WebMCP or agent tool registration. BW-038 low: Core shopping tasks have no explicit agent-facing capabilities |
be-agent-readyon-device-inference | not-applicable | high | The bike search/catalog tasks do not require on-device generative inference; no product inference feature was observed. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten repeated bottom/top scroll cycles, heap changed by only 54 nodes and 14,472 bytes, with no material retained growth. |
be-memory-efficientbounded-footprint | issues | high | Heap summary recorded 559,221 nodes, 2,436,718 edges, and 30.82 MB self size for the landing page. BW-039 medium: The home page has a large initial heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/post heap summaries show negligible node growth (559,221 to 559,275) and no Detached constructor in reported top populations. |
Provenance
Canonical report: results/atomic/reports/0359-www_bikewale_com.json
Report SHA-256: d565ca561824b23bade93971ce29ed13e453e6d7f1f28fcf53b26069b6ed41ff
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bikewale_com/2026-07-20T05-22-10-841Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bikewale_com/2026-07-20T05-22-10-841Z
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.