Manifest position 773 · CrUX rank bucket 1000
https://corp.sbi.bank.in
Coverage complete
Coverage complete across 58 catalog checks and four representative paths. Authentication systems on separate origins were not covered.
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 | The dark-mode screenshot is visually identical to the light capture, and computed styles report color-scheme: normal with white surfaces. F01 medium: The gateway ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched prefers-reduced-motion: reduce but still found a running 60,000 ms marquee animation. F02 medium: The scrolling announcement keeps animating when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast: more screenshot retained visible text, controls, borders, and links. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules, while the representative site uses cross-document navigation and accordion/state changes. F03 low: Navigation and state changes use abrupt swaps rather than view transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scroll-linked reveal, scrollytelling, or other scroll-driven animation exists on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-reveal, drag, or gesture-driven interaction exists on the representative pages. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Desktop screenshots and CSS inspection show fixed/static navigation with no scroll-state container rules or progress cue on long pages. F04 low: Navigation chrome is static and does not respond to scroll position. |
provide-guided-navigationanchored-positioning | issues | high | DOM/CSS inspection found Bootstrap menu/dialog structures and no anchor-name, position-anchor, or position-try usage. F05 low: Menus and overlays rely on legacy Bootstrap/manual positioning rather than resilient anchored placement. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs on the FAQ and clearly separated account-opening cards provide visible orientation and next-step cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first viewport contains two full-width warning banners plus a continuously moving announcement before the personal-banking action. F06 medium: Stacked notices and a moving announcement dominate the gateway before core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The accessibility probe found six div-based role=dialog modals and 18 javascript: links rather than native dialog/popover/details controls. F07 medium: Transient UI is implemented with custom Bootstrap div dialogs and JavaScript links. |
maximize-content-reduce-noisereduced-chrome | issues | high | The corporate template screenshot shows a dense tab bar, banner, announcement panels, decorative imagery, and compact 12 px text around the primary login action. F08 medium: Dense legacy chrome competes with core banking actions. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The gateway overflows by 33 px at 360 px. The FAQ lacks a viewport meta tag and renders a 980 px desktop canvas scaled to fit. F09 high: Representative pages do not reliably reflow on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found zero container rules; the corporate template includes fixed widths such as #wrapper { width: 980px } and many fixed-size panels. F10 medium: Components depend on fixed widths and viewport-era styling rather than adapting to their containers. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found the navigation toggle with outline:none and counted 23 controls below 24 px in at least one dimension; Lighthouse also failed target-size. F11 high: Keyboard focus and touch-target support are inconsistent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The gateway clearly labels Personal Banking and Corporate Banking login actions, and the account page presents three explicit next actions. |
support-core-task-successprimary-flow-completion | issues | high | Following Start New Application leads directly to “Your session has expired” instead of the registration form, before any user input. F12 critical: The current-account application journey dead-ends immediately. |
support-core-task-successclear-system-state-and-recovery | pass | high | The expired-session state is explicit and offers separate continuation links for relationship managers and customers. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP/FCP at 4.4 s; the raw-CDP trace measured LCP/FCP at 8.23 s under the observed run. F13 high: The gateway’s main content paints too slowly. |
be-fast-and-stablevisual-stability | issues | high | The 360 px FAQ layout run recorded CLS 0.139, including a 0.137 shift around 6.1 seconds. F14 medium: The FAQ template has a material load-time layout shift. |
be-fast-and-stableefficient-main-thread | pass | high | Raw-CDP trace and layout captures observed no long tasks and 0 ms total blocking time in the measured load. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR/Lighthouse found four VeryHigh-priority blocking stylesheets, four synchronous head scripts, uncompressed HTML/CSS/JS, weak cache lifetimes, and an estimated 3.27 s render-blocking saving. F15 high: Render-blocking, uncompressed, poorly cached resources delay the page. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 264 KiB unused CSS and 96 KiB unused JavaScript, alongside unminified CSS/JS opportunities. F16 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name and label-content-name-mismatch; the image audit also found one image without alt text. F17 high: Some links lack reliable accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse reported no failed color-contrast audit, and the high-contrast capture retained readable controls and text. |
be-inclusivestructure-and-focus | issues | high | The gateway toggle computes outline:none when focused, while the legacy corporate pages omit a main landmark and even a visible h1 in the inspected DOM. F18 high: Focus visibility and semantic structure are inconsistent across templates. |
be-inclusivelegible-text | issues | high | Computed styles show 12 px Tahoma throughout the fixed 980 px corporate template; on mobile the whole FAQ canvas is scaled down rather than reflowed. F19 medium: Legacy pages use cramped, fixed 12 px typography and scaled desktop layouts. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The FAQ has no viewport meta and exposes a 980 px layout at a 360 px condition; Lighthouse failed touch-target sizing. F20 high: Zoom/reflow and target sizing fail on representative pages. |
follow-best-practicesno-console-errors | issues | high | Lighthouse’s errors-in-console audit failed for the tested navigation. F21 medium: The gateway logs browser errors during load. |
follow-best-practicessound-document-and-assets | issues | high | The image probe found 23 of 24 images without explicit dimensions, 23 legacy-format images, and one oversized image; Lighthouse also failed unsized-images. F22 medium: Image and document assets are not consistently soundly authored. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed the inspector-issues audit; the DOM also contains 18 javascript: pseudo-links that bypass native link/button behavior. F23 medium: DevTools reports platform hygiene issues. |
be-discoverabletitle-and-description | pass | high | The gateway has a descriptive title and meta description (“State Bank of India”), both present in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The DOM probe found 18 javascript: links, Lighthouse failed crawlable-anchors, and the FAQ template lacks viewport metadata. F24 high: Important navigation is not fully crawlable or consistently mobile-friendly. |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical URL was present; /robots.txt and /sitemap.xml both returned branded 404 rejection pages. F25 medium: Canonical, robots, and sitemap indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found zero JSON-LD blocks and no Open Graph tags on the organization/service gateway. F26 medium: The public bank gateway lacks structured and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The header audit found no HSTS or nosniff and a CSP allowing unsafe-inline; all four observed cookies use SameSite=None, with one not HttpOnly. F27 high: Transport is HTTPS, but key security headers and cookie posture are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | Tracker inspection found no known tracker domains, only one zero-byte third-party image request, and the secrets scan found no exposed credentials. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | This host presents no permission request or authentication form; authentication is delegated to separate YONO origins outside the requested host scope. |
be-private-and-securedefensive-browser-policies | issues | high | No frame-ancestors/X-Frame-Options, Referrer-Policy, or Permissions-Policy was observed, and the CSP lacks the documented clickjacking defense. F28 high: Browser-enforced defensive policies are largely absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 96% rendered-content coverage in raw HTML, with title, h1, and description available without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | A fresh navigation to Start New Application immediately rendered a session-expired state, showing that initial session state is not stabilized. F29 high: The account flow starts in stale runtime state. |
be-resilientoffline-and-installable | not-applicable | high | This public banking gateway delegates intrinsically online transactions and is not an installable app surface; offline account operations would be inappropriate. |
be-resilientnetwork-and-http-failure-states | issues | high | Both robots.txt and sitemap.xml returned 404 pages saying the URL was rejected and offered only a support ID, with no recovery navigation. F30 medium: Missing infrastructure routes return a dead-end rejection page. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The multilingual current-account pages have an empty html lang attribute, and legacy CSS uses extensive physical left/right properties and fixed positioning. F31 high: Language and bidirectional layout foundations are inconsistent. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited public pages display no user-facing dates, currencies, durations, or locale-sensitive numeric data to format. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited paths expose no events, schedules, timestamps, or recurring-time data. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, forced continuity, disguised advertisement, or confirmshaming was observed across the four representative paths. |
be-trustworthyhumane-error-handling | not-applicable | high | No editable form could be reached on this host: the application route expired before rendering fields, so there was no form-validation interaction to judge. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No sign-in, address, payment, or signup fields were rendered on the audited host; those flows are delegated or blocked before fields appear. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The advertised Start New Application action immediately reports an expired session on a fresh visit, preventing account setup. F32 critical: The account-opening flow is not dependable or continuous. |
be-sustainableoptimised-assets | issues | high | The HAR transferred 5.44 MB, of which 4.84 MB was images; 23 images use legacy JPG/PNG, 23 lack dimensions, and responsive srcset is absent. F33 high: The gateway transfers a large set of unoptimized carousel images. |
be-sustainableno-wasteful-work | issues | high | The network run downloaded 32 images and multiple 1,140–1,920 px banners, including many hidden slides, during initial load. F34 high: Hidden carousel media is eagerly downloaded without immediate user value. |
be-sustainablethird-party-and-media-budget | issues | high | Although known trackers were absent, first-party images alone transferred 4.84 MB for a page whose core task is choosing a login or service link. F35 high: The media budget is disproportionate to the simple gateway task. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or safe transaction-tool surface was found; this emerging capability is optional for the audited banking gateway. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the audited gateway’s core experience, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten menu open/close cycles, heap self-size changed from 5.09 MB to 5.36 MB with no Detached constructor among leading populations; this is modest warm-up, not evidence of unbounded growth. |
be-memory-efficientbounded-footprint | pass | medium | The measured page used about 2.59 MB live JS heap, 647 DOM nodes, and a 5.09 MB snapshot self-size, proportionate to this gateway. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Baseline/post heap summaries showed no Detached constructor in the leading populations and stable jQuery wrapper counts after repeated menu toggles. |
Provenance
Canonical report: results/atomic/reports/0773-corp_sbi_bank_in.json
Report SHA-256: 04ea835f2dd0390054c9df6f8ed7d14c67f86c37ba6fc189aeab85957b951109
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/corp_sbi_bank_in/2026-07-22T23-14-28-673Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/corp_sbi_bank_in/2026-07-22T23-14-28-673Z
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.