Manifest position 705 · CrUX rank bucket 1000
https://testbook.com
Coverage complete
Coverage complete across six representative public templates. Checkout after purchase, authenticated test execution, and account cancellation were not covered because they require credentials/payment.
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-condition screenshot is visually identical to light; computed color-scheme is normal and CSS probe found no dark preference rule. F001 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | Three animations remained running under reduce (durations 1000, 1000, and 2500 ms), and no reduced-motion CSS rule was found. F002 high: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | issues | high | No prefers-contrast or forced-colors styling was found; Lighthouse found 31 color-contrast failures. F003 high: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | medium | No View Transition CSS/API use was found across the Angular homepage and representative navigation surfaces; state changes are abrupt. F004 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked storytelling/parallax behavior or JavaScript-driven scroll animation was observed, so the page avoids the main-thread anti-pattern. |
implement-natural-interactionsphysical-gestures | pass | medium | Native scrolling and ordinary tap controls worked without custom gesture interception or scroll fighting on audited mobile paths. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Navigation adapts between desktop header and mobile menu while long content remains scrollable; no blocking fixed chrome was observed. |
provide-guided-navigationanchored-positioning | issues | medium | The site has dropdown/menu and floating notification UI, but no CSS anchor positioning or fallback-position rules were found. F005 low: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | pass | medium | Headings, selected Pass navigation, direct CTA labels, and content grouping provide visible orientation on representative routes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A fixed notification-permission banner occupies the bottom of both first viewports while promotional chrome and WhatsApp also compete with core content. F006 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | The persistent notification UI is custom chrome rather than a native dialog/popover flow; the DOM reports a role=dialog surface and no popover primitive. F007 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | On mobile, the trial banner, fixed notification prompt, WhatsApp control, header, and app badges crowd the primary preparation content. F008 medium: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | medium | The online test-series listing has 8 px horizontal overflow (scrollWidth 368 vs clientWidth 360); other sampled templates did not overflow. F009 medium: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe found no container queries; reusable cards/navigation rely on viewport-wide treatment and the listing overflows at 360 px. F010 low: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Several focused links report outline:none and many exam-category controls are only 34 px tall, below a comfortable touch target. F011 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage states “Complete Exam Preparation” with Get Started For Free; listing, exam detail, signup, and Pass routes expose clear next actions. |
support-core-task-successprimary-flow-completion | pass | medium | Get Started reaches a focused mobile-number signup step, while Pass exposes plan, total, renewal note, and purchase CTA without an avoidable detour. |
support-core-task-successclear-system-state-and-recovery | issues | high | Blank submission left the page visually unchanged with no inline error, recovery instruction, or announced required-field state. F012 high: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.9 s, TBT 760 ms, and CLS 0.132; the trace measured LCP 7.13 s and 864.91 ms total blocking time. F013 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | Mobile layout observation measured CLS 0.183 on home and 0.169 on the exam detail; 54 of 98 images lack dimensions. F014 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded six long tasks, a 667.58 ms longest task, and 864.91 ms total blocking time. F015 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 118 requests and 2.86 MB transferred; 50 scripts carried 2.12 MB and several parser-inserted high-priority scripts are candidates in the critical path. F016 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 611 KiB unused JavaScript and 53 KiB unused CSS; multiple GTM/gtag and Facebook bundles dominate transfer. F017 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found seven unnamed links and an image-alt failure; image inspection found four images without alt text. F018 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 31 failing contrast nodes on the homepage. F019 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found three heading-order failures; the document has two h1 elements and no main landmark, while multiple focused controls suppress outlines. F020 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | pass | medium | Core headings and body text reflow without clipping on sampled home, signup, Pass, blog, and detail views. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport scaling is allowed, but many controls are 34 px tall and the test-series template overflows by 8 px at 360 px. F021 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no console errors. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but Lighthouse found four aspect-ratio failures and image inspection found 54 images without explicit dimensions. F022 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | pass | medium | No console exception or browser permission prompt occurred on load; notification consent is rendered as site UI with a defer option. |
be-discoverabletitle-and-description | pass | high | Homepage and sampled content expose descriptive titles and meta descriptions; Lighthouse passed both audits. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport and robots are valid, but Lighthouse found 77 non-crawlable anchors; recon shows many javascript:void(0) links for categories and actions. F023 high: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage/detail return 200 with canonical/sitemap signals, but the public blog index raw fetch returned HTTP 500 while still rendering content. F024 high: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Homepage DOM contains application/ld+json and Open Graph title, description, URL, type, image, locale, and site metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy are absent; all 15 observed cookies were flagged insecure. F025 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Load contacted 22 third-party origins and five known trackers; 70 third-party requests transferred 1.33 MB, including Google, Facebook, DoubleClick, Bing, and WebEngage. F026 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | Signup uses a mobile-number/OTP entry with no visible passkey/WebAuthn option; phishing-resistant authentication was not offered on the sampled auth path. F027 medium: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | Only X-Frame-Options was present; HSTS, CSP/frame-ancestors, Referrer-Policy, Permissions-Policy, and nosniff were absent, and many cookies use SameSite=None without Secure. F028 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Raw HTML preserves 98% of home and 100% of exam-detail content, including titles, h1, and descriptions; neither route is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Core content remained rendered and scrollable across sampled mobile routes without blank shells or clipped primary content. |
be-resilientoffline-and-installable | issues | medium | No manifest link was present in recon and no offline fallback was evidenced for this app-like exam-preparation service. F029 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | issues | high | The blog index returns HTTP 500 while rendering a normal content page, providing a misleading success-like UI and broken status signal rather than intentional recovery. F030 high: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | html lang=en is present, but no dir and no logical inline/block properties were detected despite the site exposing language switching and localized content. F031 medium: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | pass | medium | The interface exposes language selection and renders Indian currency/number conventions consistently on the sampled Pass and home surfaces. |
be-internationalisedtime-zone-correctness | not-applicable | medium | No user-entered scheduling or cross-time-zone event flow was present in the audited public routes. |
be-trustworthyno-dark-patterns | pass | medium | Notification can be deferred, trial close is visible, Pass pricing and renewal are disclosed, and no preselected add-on was observed. |
be-trustworthyhumane-error-handling | issues | high | The blank mobile-number submission produced no visible required-field feedback or actionable error. F032 high: Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | The mobile-number step is not represented by a semantic form in the rendered DOM and its input exposes no autocomplete token, reducing autofill/input assistance. F033 medium: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Pass shows annual price, crossed-out reference price, total, 365-day validity, renewal text, and a specific purchase CTA before commitment. |
be-sustainableoptimised-assets | issues | high | Of 98 images, 64 use legacy formats, 16 are oversized, 15 lack responsive sources, and 54 lack dimensions. F034 high: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | An idle homepage load executes 50 scripts, transfers 2.12 MB of script, and records 70 third-party requests plus 864.91 ms blocking time. F035 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 1.33 MB across 70 requests; duplicate Google tags and Facebook/WebEngage code consume substantial budget before user interaction. F036 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | No declared agent-facing intent was available for this public exam-preparation audit. |
be-agent-readyon-device-inference | not-applicable | medium | No declared agent-facing intent was available for this public exam-preparation audit. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Node count grew 924,210 to 933,764 and self size 54.76 MB to 55.69 MB (about 1.7%); this bounded change does not evidence unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | Post-interaction heap remained about 55.7 MB with 933,764 snapshot nodes, proportionate to the large rendered homepage and stable relative to baseline. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | The small 1.7% total-size delta after ten cycles did not show a runaway population; constructor-level detached-node evidence was not exposed by this compact summary, so confidence is low. |
Provenance
Canonical report: results/atomic/reports/0705-testbook_com.json
Report SHA-256: d0d4e0fea2ba45f9b06d6050e9a3077105a2354ce18c54bdac8be18d25ca381c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/testbook_com/2026-07-22T12-50-22-841Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/testbook_com/2026-07-22T12-50-22-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.