Manifest position 202 · CrUX rank bucket 1000
https://ssc.gov.in
Coverage complete
Coverage-complete agentic audit of representative public, content, listing, resource, login, and failure-state surfaces.
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 default light screenshot, and computed styles report color-scheme: normal with a white surface. F-001 medium: The interface ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | No animations were running; Bootstrap transition rules explicitly disable transitions under reduce. |
respect-user-preferencesrespects-contrast | issues | medium | The prefers-contrast: more capture is pixel-equivalent in appearance to the default, and no contrast-preference CSS was found. Baseline contrast is generally good, so this is a preference-adaptation gap rather than an immediate legibility failure. F-002 low: The page does not adapt to increased-contrast preferences. |
implement-natural-interactionsview-transitions | issues | medium | The CSS/API probe found no view-transition rules on this Angular SPA, while representative routes replace the main content area. F-003 low: SPA route changes use abrupt state swaps rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked visual effect or custom parallax/scrollytelling behavior was present, so no main-thread scroll-animation anti-pattern was observed. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-refresh, drag, carousel gesture, or other gesture-driven control is part of the representative journeys. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The homepage is 3,695 CSS px tall, but the CSS probe found no scroll-state container query or progress indicator. F-004 low: The long homepage has static navigation chrome with no scroll-position feedback. |
provide-guided-navigationanchored-positioning | issues | medium | DOM inspection shows nested Bootstrap dropdown divs and no anchor-name, position-anchor, or position-try CSS. F-005 low: Dropdown navigation relies on custom Bootstrap positioning rather than anchored, edge-aware platform positioning. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs and active underlines identify the current section on Chairman, Calendar, and Script Evaluation routes. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No modal, consent wall, or viewport-blocking interstitial obscured core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM contains no dialog, popover, or details elements; navigation dropdowns are nested div structures with manual Bootstrap behavior. F-006 low: Rich navigation controls use ad-hoc div-based dropdown structures instead of semantic platform primitives. |
maximize-content-reduce-noisereduced-chrome | pass | medium | The site uses a compact header and content-led cards/tables; chrome does not dominate after the hero. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | scrollWidth equals innerWidth at 360px with 0px horizontal overflow and viewport meta present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The stylesheet probe found no @container/container-type rules across the representative component-heavy homepage. F-007 low: Reusable components are driven only by viewport-era layout CSS, not container context. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/size probe measured language and menu buttons at 20px high, pagination arrows at 30px, and multiple buttons with outline:none and box-shadow:none after programmatic focus. F-008 medium: Several interactive targets are too small and some buttons lack a visible focused state. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Identity, notices, Apply/Login actions, calendar, and resource headings clearly communicate purpose and next steps. |
support-core-task-successprimary-flow-completion | pass | medium | Representative public tasks reach their destination without dead ends; authenticated completion was not claimed or required to verify public journey continuity. |
support-core-task-successclear-system-state-and-recovery | issues | high | After requestSubmit() on the empty login form, the captured state shows no inline error, summary, or recovery instruction, only unchanged required-field labels. F-009 medium: Empty login submission provides no visible, actionable field feedback. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.9s, FCP 5.5s, Speed Index 10.9s, and TTI 18.2s; the independent trace measured LCP 4.86s. Both LCP results exceed the good threshold. F-010 high: The primary page loads far too slowly in a mobile Lighthouse run. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.0027 desktop and 0.00044 mobile; Lighthouse CLS was effectively 0. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported about 3.0s main-thread work and 250ms TBT; the trace found two long tasks up to 100ms. F-011 medium: Startup JavaScript creates avoidable main-thread work. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 72 requests and 3.34MB transferred, including 1.61MB across 14 fonts; multiple large text resources were uncompressed, and a preloaded banner URL returned 404. F-012 high: Resource delivery is heavy and inefficient for a public information homepage. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 430KiB unused CSS and 362KiB unused JS, including both Angular bundles and legacy jQuery/Bootstrap assets. F-013 high: The page ships large amounts of unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | The login DOM probe found labels:null and aria:null for username/password inputs; Lighthouse also reported a visible-label/accessibility-name mismatch elsewhere. F-014 medium: The login fields are not programmatically associated with their visible labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed with no failing nodes on the homepage. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed landmark-one-main; DOM probes found navigation landmarks but no main, while several buttons had no outline or focus shadow. F-015 medium: Pages lack a main landmark and visible focus is inconsistent. |
be-inclusivelegible-text | pass | medium | Body text remains readable with reasonable line spacing and no observed clipping on sampled pages. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | The viewport permits scaling, mobile content reflows without overflow, Lighthouse target-size passed, and no essential timed media was present. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a 404 for /assets/banner/New%20SSC%20Banners%2001%201.webp; the HAR recorded the same failed image. F-016 medium: A broken banner preload generates a console/network error. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse measured the banner at 3.43:1 versus its natural 4.95:1 ratio; the images primitive found 84/84 images missing a complete width/height pair. F-017 medium: The homepage banner is rendered at the wrong aspect ratio and many images omit intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported missing source maps for large first-party JavaScript and three BFCache failure reasons. F-018 low: The app has avoidable platform diagnostics and BFCache blockers. |
be-discoverabletitle-and-description | issues | high | The login route reports “Home | Staff Selection Commission | GoI” and the same generic description as the homepage, so route metadata is not unique. F-019 medium: Distinct routes reuse the homepage title and generic description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors and the login probe counted 34 <a> elements without href; affected links include key navigation and View All actions. F-020 high: Many navigation links have no href and therefore are not crawler-reachable. |
be-discoverablecanonical-and-indexing-signals | issues | high | No canonical or hreflang links were present, /robots.txt returned 404, and /sitemap.xml was rewritten to the Angular shell instead of serving an XML sitemap. F-021 medium: Public routes lack canonical/indexing infrastructure. |
be-discoverablestructured-and-shareable-metadata | issues | high | The route probe found zero JSON-LD blocks and zero Open Graph properties despite the site representing a government organization and publishing notices. F-022 medium: The public government site exposes no structured or social preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirmed HTTPS but no CSP, HSTS, X-Content-Type-Options, frame protection, Referrer-Policy, or Permissions-Policy. F-023 high: Core transport security headers are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The trackers primitive observed Google Tag Manager and Google Analytics on load, with four third-party requests and three first-party _ga cookies; the page provides no visible privacy choice in the tested first viewport. F-024 medium: Analytics tracking starts by default without an evident consent or minimisation control. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found no WebAuthn/passkey integration; username and password inputs both have autocomplete="off". No permission prompt fired on load. F-025 medium: Candidate authentication appears password-only and explicitly disables browser autofill. |
be-private-and-securedefensive-browser-policies | issues | high | The response lacks HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, and CSP frame-ancestors; no equivalent defenses were observed. F-026 high: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 1% raw-to-rendered content coverage: raw HTML contained 39 text characters versus 14,162 rendered and no h1, identifying an Angular JS shell. F-027 high: Core notices and navigation disappear without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative routes stabilized and no clipped overlay or broken async state was observed. |
be-resilientoffline-and-installable | not-applicable | high | This is primarily a public information and account portal, not an install-promoted app; offline installability is contextual. Core no-JS resilience is judged separately and fails. |
be-resilientnetwork-and-http-failure-states | pass | high | The site presents a clear branded 404 page stating that the requested page cannot be found, with global recovery navigation. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The English route declares lang="en", exposes English/Hindi selection, and sampled framework CSS includes logical inline properties. |
be-internationalisedlocale-aware-data | issues | medium | The homepage shows fixed strings such as “Jul 16 2026” and the selected Hindi/English interface has no evidence that visible dates are formatted through Intl for the active locale. F-028 medium: Dates are rendered with hand-arranged English abbreviations instead of locale-aware formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled public content uses calendar dates without cross-time-zone event times, recurrence, or DST-sensitive scheduling. |
be-trustworthyno-dark-patterns | pass | high | No confirmshaming, disguised advertising, forced continuity, consent wall, or misleading pricing was observed. |
be-trustworthyhumane-error-handling | issues | high | The empty-submit screenshot contains no field-level message, error summary, aria-invalid state evidence, or clear next recovery step. F-029 medium: Required login errors are not visibly explained after submission. |
be-trustworthytrustworthy-input-assistance | issues | high | Both username and password controls report autocomplete="off" and have no semantic autocomplete tokens. F-030 high: The login form blocks standard autofill assistance. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | No commercial commitment exists; login clearly labels candidate/admin modes and exposes Forgot Password without deceptive continuity. |
be-sustainableoptimised-assets | issues | high | The images primitive found 84 missing complete intrinsic dimensions, 77 below-fold images without lazy loading, 24 without responsive sources, and three oversized images. F-031 medium: Images are modern-format but not responsively or dimensionally optimized. |
be-sustainableno-wasteful-work | issues | high | The HAR shows duplicate browse-exam API requests, 72 total requests, uncompressed CSS/document/API payloads, and legacy jQuery alongside Angular. F-032 medium: The page performs redundant work and transfers uncompressed application resources. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR transferred 3.34MB, including 1.61MB across 14 fonts and 169KB from Google Tag Manager; font bytes exceed all scripts combined. F-033 medium: The font and analytics budget is disproportionate to a text-heavy government information page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or structured transaction surface was found; emerging WebMCP capability is not required for this public information portal. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or language-model feature is offered where on-device inference is an expected product capability. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Heap self-size changed from 26.07MB to 26.49MB (about 1.6%) after ten cycles, with no evidence of unbounded retained growth in this bounded exercise. |
be-memory-efficientbounded-footprint | pass | medium | The loaded Angular page used about 26MB heap self-size and 1,130 DOM elements, proportionate to the sampled portal page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The summaries did not surface a Detached* constructor population, and bounded growth after ten cycles did not indicate accumulating detached DOM/listeners. |
Provenance
Canonical report: results/atomic/reports/0202-ssc_gov_in.json
Report SHA-256: ac3aaee15505fb3dafecbef564d2acb57e5c886a54af58c55ec7778c27e58832
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ssc_gov_in/2026-07-19T03-41-08-418Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ssc_gov_in/2026-07-19T03-41-08-418Z
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.