Manifest position 562 · CrUX rank bucket 1000
https://www.flipkart.com
Coverage complete
Coverage-complete atomic audit across six representative paths; authenticated account pages, a real purchase/payment, seller tools, and personalised post-login states were not covered because they require credentials or irreversible/private actions.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-scheme screenshot is visually the same light white/grey UI as the default, and the fetched 458 KB CSS contains no prefers-color-scheme rule. F01 medium: The interface remains light under a dark system preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found five running animations, including durations of 4.72 s and 5.33 s; CSS feature inspection found no prefers-reduced-motion rule. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | Fetched CSS contains no prefers-contrast or forced-colors rules; the increased-contrast capture does not establish a purpose-built high-contrast treatment. F03 medium: No authored high-contrast adaptation is present. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection across home, search, and product found zero view-transition declarations; the modal-cycle video shows an abrupt custom state swap. F04 low: Route and modal state changes do not use authored View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked parallax/reveal behavior was present on sampled paths, so there was no authored scroll-handler anti-pattern to replace. |
implement-natural-interactionsphysical-gestures | pass | high | Home/product CSS contains scroll-snap and overscroll-behavior, and native scrolling remained usable. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The listing scroll video and CSS inspection show no progress indicator, shrinking header, scroll-state query, or equivalent positional feedback on a 10,183 px page. F05 low: Long listing navigation does not provide scroll-state guidance. |
provide-guided-navigationanchored-positioning | issues | high | CSS inspection found zero anchor-name, position-anchor, or position-try declarations on the sampled templates. F06 low: Menus and the login overlay are manually positioned rather than anchored. |
provide-guided-navigationdirects-attention | pass | high | Active category underline, breadcrumbs, clear empty-cart actions, and product variant selection provide location and next-step cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The desktop and mobile first-load screenshots show a dimmed page covered by a large login prompt before user intent; on mobile the overlay is clipped. F07 high: A login interstitial obscures the homepage on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM/probe evidence reports dialog=0, ariaModal=0 and a full-viewport custom DIV while the screenshot clearly shows modal behavior. F08 high: The login modal is an unlabelled custom div, not a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport is dominated by the account modal, header categories, and ad creative; core product content is mostly obscured. F09 medium: Promotional chrome and the account prompt crowd out shopping content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport, layout reports clientWidth=980, scale=0.367 and hasViewportMeta=false for search and login, making text and controls tiny; the homepage modal also scrolls to 370 px. F10 critical: Search and login templates ship a 980 px desktop viewport to 360 px devices. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Search/login render as scaled desktop pages while product/cart use true 360 px layouts; all three CSS probes report zero @container/container-type usage. F11 high: Shared search/auth components do not adapt consistently by container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home probe found 42/96 visible interactive targets under 44 px; search found 50/88. Focused search inputs/buttons computed outline:none. F12 high: Many controls are undersized and several suppress focus indication. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Search, category navigation, product pricing/variants, and cart recovery actions are prominent and specific. |
support-core-task-successprimary-flow-completion | pass | high | Anonymous users can move from search results to a product surface and to cart/login entry points without a bot or account wall blocking discovery. Transaction completion was not attempted. |
support-core-task-successclear-system-state-and-recovery | pass | high | Empty cart offers Login and Continue Shopping; the tested 404 explains the missing page and links home; invalid login gives visible corrective text. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.0 s, TBT 470 ms, Speed Index 7.7 s and interactive 18.1 s (performance 0.65). F13 high: Mobile lab loading misses the good LCP and responsiveness bar. |
be-fast-and-stablevisual-stability | issues | high | The layout observer measured CLS 0.083 on product and 0.106 on cart, with the cart shift concentrated in a 0.106 event. F14 medium: Product and cart views shift materially after load. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse TBT was 470 ms; traces found 3 long tasks on both home and product, and the product trace recorded 120 ms TBT. F15 high: Startup JavaScript blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | The home HAR records 123 requests and 3.44 MB transferred, including 2.81 MB of script; product transfers 3.31 MB with 2.86 MB script. Parser-initiated modules were confirmed deferred, leaving the stylesheet and sheer startup graph as the concern. F16 high: Critical delivery is script-heavy. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Home loads 27 script requests/2.81 MB and search still loads polyfills plus analytics/tag-manager scripts; script is over 80% of transferred bytes. F17 medium: Large legacy and instrumentation bundles dominate page weight. |
be-inclusivenames-roles-labels | issues | high | axe found 14 missing image alternatives, critical unlabeled form elements, and three unnamed links on home; login has an unnamed button, unlabeled input, ten images without alt, and four unnamed links. F18 critical: Core controls and images lack accessible names or labels. |
be-inclusivesufficient-contrast | issues | high | axe reported five contrast failures on home and twenty on login, including form/help text and policy links; Lighthouse also failed color-contrast. F19 high: Text and links fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The product has no main landmark and duplicate contentinfo landmarks; home has no main/nav landmarks. Focus probes show outline:none on search fields and many links across search/login. F20 high: Landmarks and visible focus are inconsistent. |
be-inclusivelegible-text | issues | high | The 360 px search capture scales a 980 px, 10,183 px desktop page to 36.7%, and the login capture similarly miniaturises the whole form/footer. F21 critical: Desktop scaling makes mobile listing and login text illegible. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Home/product declare user-scalable=no; search/login omit viewport meta and render at 980 px. axe flags the viewport setting as critical. F22 critical: Several templates prevent zoom or omit the responsive viewport. |
follow-best-practicesno-console-errors | issues | high | Lighthouse recorded three console failures: one 401 unread-count request and two 406 analytics collector requests. F23 medium: The homepage emits failed network requests in the console. |
follow-best-practicessound-document-and-assets | issues | high | Image inspection found 45/97 homepage images and 18/64 product images without dimensions; 54 homepage images use legacy formats and six are oversized. F24 medium: Many images lack intrinsic dimensions and use legacy formats. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 0.96; no on-load permission prompt, deprecated-API audit failure, paste prevention, or broken image aspect ratio was observed. |
be-discoverabletitle-and-description | issues | high | Direct DOM probes found meta[name=description] absent on home, search, product, login, and cart, although titles were descriptive; Lighthouse observed a homepage description in a separate run, indicating inconsistent output. F25 medium: Rendered representative pages do not expose meta descriptions consistently. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Search has no viewport meta and is scaled to 980 px; Lighthouse found one non-crawlable anchor and the live home probe found one anchor without href. F26 high: Public listing pages are not mobile-friendly and one anchor is not crawlable. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and product expose canonical URLs; robots.txt is reachable and declares product/store sitemaps; cart is intentionally noindex/disallowed. |
be-discoverablestructured-and-shareable-metadata | pass | high | Product exposes matching Product JSON-LD, title, canonical and og:image; homepage exposes Organization JSON-LD and Open Graph title/URL. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and CSP are present, but HSTS and nosniff are missing; CSP permits unsafe-inline/unsafe-eval. Cookie audit reports 14 SameSite=None cookies and 8 without Secure. F27 high: Transport policy and cookie flags are weaker than expected. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found eight cross-origin origins and active New Relic endpoints; the HAR attributes 121/123 requests and 3.27 MB to other origins (mostly Flipkart CDNs, plus monitoring). F28 medium: Analytics and third-party activity are broad for an anonymous first load. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The sampled login page requests email/mobile and Request OTP; no password is collected, but no WebAuthn/passkey option or credential affordance appears. No permission prompt appeared on load. F29 low: Login offers OTP only, with no visible passkey route. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no HSTS, frame-ancestors/X-Frame-Options, Referrer-Policy, Permissions-Policy, or nosniff, and CSP allows unsafe-inline/unsafe-eval. F30 high: Defensive response policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Core home and product content remains visible without JavaScript; crawler captures are populated and raw/rendered word coverage is 62%/55%, not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | The 360 px homepage capture shows the modal extending beyond both sides, with its left content and create-account action cut off. F31 high: The custom login overlay is clipped on narrow screens. |
be-resilientoffline-and-installable | issues | high | Home/product/search probes found no link rel=manifest; no install surface was present. F32 medium: The commerce experience is not installable from the sampled pages. |
be-resilientnetwork-and-http-failure-states | pass | high | A tested HTTP 404 returns a clear moved/deleted explanation and a GO TO HOMEPAGE recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | lang is present (en/en-IN), but fetched CSS across representative templates contains zero logical margin/padding/inset properties and no authored dir adaptation. F33 medium: International layout support is incomplete. |
be-internationalisedlocale-aware-data | pass | high | Sampled prices use the Indian rupee symbol and Indian-facing number formatting consistently; lang is en-IN on home/product/cart. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public paths exposed no event scheduling, stored time, recurrence, or cross-time-zone workflow to judge. |
be-trustworthyno-dark-patterns | issues | high | The homepage opens the login prompt automatically over product content, while login is also available in the header; this creates an avoidable account-pressure interruption. F34 high: Authentication is nagged before the user asks for it. |
be-trustworthyhumane-error-handling | issues | high | After empty Request OTP, text says “Please enter valid Email ID/Mobile number”, but every sampled input still has aria-invalid=null, :user-invalid=false, and no native validationMessage. F35 medium: Login errors are visible but not exposed as invalid state. |
be-trustworthytrustworthy-input-assistance | issues | high | Login probe shows the identity field with autocomplete=off and no label/aria-label; search fields also use autocomplete=off. F36 high: Sign-in and search inputs disable autocomplete and lack visible labels. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Product pricing, discount, variants, offers, and Protect Promise fee are visible; empty cart offers reversible navigation and login; OTP terms/privacy links are adjacent to continuation. |
be-sustainableoptimised-assets | issues | high | Homepage image audit found 54 legacy-format images, six oversized images, and 45 without dimensions; product found 28 legacy and three oversized. F37 medium: Image delivery still wastes bytes and layout certainty. |
be-sustainableno-wasteful-work | issues | high | The homepage makes 123 requests including 25 fetch/XHR; Lighthouse logs a predictable 401 and two 406 collector calls, while traces record repeated long tasks. F38 medium: Anonymous loads perform avoidable failing and analytics work. |
be-sustainablethird-party-and-media-budget | issues | high | HAR reports 3.27 MB/3.44 MB and 121/123 homepage requests from origins other than www.flipkart.com; 2.81 MB is script and New Relic tracking is active. Most byte-heavy origins are Flipkart CDNs, but they still consume user resources. F39 medium: The startup budget is dominated by cross-origin scripts. |
be-agent-readystructured-agent-capabilities | issues | high | The product is reasonably crawlable and has JSON-LD, but no WebMCP/agentic form registration was observed on search, product, login, or cart. F40 low: High-value commerce actions are not exposed as structured agent tools. |
be-agent-readyon-device-inference | not-applicable | high | No sampled task requires generative summarisation or language-model inference; adding on-device AI solely to satisfy this check would not improve the core commerce journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten login modal close/open cycles, DOM nodes fell from 2,062 to 2,040 and JS heap rose only 1.46 MB (~3.7%); the independent post heap snapshot was smaller than baseline. No monotonic leak signal was established. |
be-memory-efficientbounded-footprint | pass | high | A loaded home state used about 39 MB JS heap with 2,062 DOM elements in the interaction probe; the heap summary was 60.9 MB, proportionate to a dense commerce homepage though optimisation is warranted. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | DOM count decreased across ten modal cycles and neither heap summary listed Detached constructors among top retained constructors. No accumulating detached-node signal was observed. |
Provenance
Canonical report: results/atomic/reports/0562-www_flipkart_com.json
Report SHA-256: 8544522bdb826cdde3a882fecfa782dbe240c306e36d43accb85ae4f99ddd8be
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_flipkart_com/2026-07-21T14-26-30-176Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_flipkart_com/2026-07-21T14-26-30-176Z
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.