Manifest position 387 · CrUX rank bucket 1000
https://www.biblegateway.com
Coverage complete
Coverage-complete representative audit. The /learn and /login probes returned a Content Unavailable template; login is recorded as an issue while /learn was excluded as unavailable duplicate error coverage.
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 preference probe matched dark mode but reported body background rgb(250,248,247), black text, and colorScheme normal; the dark passage screenshot remains light. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulated preference matched and document.getAnimations() returned no active animations, so no nonessential motion continued. |
respect-user-preferencesrespects-contrast | pass | medium | The preference matched and text/consent controls remained visible; separate ordinary contrast failures are recorded under be-inclusive. |
implement-natural-interactionsview-transitions | issues | medium | Rendered CSS inspection across home, passage, and version templates found no view-transition rules or API markers; navigation is traditional full-page replacement. F02 low: Page and state changes use abrupt swaps rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or entry/exit reveal behavior was present on representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited reading/search templates expose no swipe, pull, carousel, or custom gesture flow. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The passage is a long 2,582px mobile document, while CSS inspection found no scroll-state query or progress-indicator technique. F03 low: Long reading pages have no scroll-state-aware navigation or reading-position cue. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip/popover surface requiring anchored positioning was observed. |
provide-guided-navigationdirects-attention | pass | medium | The selected Passage tab uses a persistent underline and the passage H1 identifies location after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360px screenshots show a consent surface for 545 partners consuming most of the viewport, followed by a persistent promotion; Scripture/search is not visible initially. F04 high: The initial privacy wall and promotion displace the core Bible task. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | DOM evidence found [role=dialog] spanning 780×321px and no native dialog, popover, or details elements across the inspected templates. F05 medium: The consent experience is implemented as a large role=dialog subtree rather than a native dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | high | Screenshots show consent, masthead, a bright sales banner, and a large blank ad slot before the search or passage content. F06 high: Application chrome dominates the first viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Both paths had viewport metadata and 0px horizontal overflow with scrollWidth exactly 360px. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS inspection across reusable search, navigation, passage, and version surfaces found no @container or container-type rules. F07 low: Responsive behavior is viewport-driven rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home probe found 11 of 20 visible controls below 24px in one dimension; the passage found 43 of 334. Focus received a visible 1px auto outline. F08 medium: Many interactive targets are too small even though keyboard focus is visible. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The first-view screenshots contain no search field or page heading; the home DOM has no H1. Search becomes clear only after consent and scrolling. F09 high: The primary Scripture search is hidden below consent, sales, and ad chrome. |
support-core-task-successprimary-flow-completion | pass | high | The John 3:16 NIV passage loaded with the expected verse, version selector, H1, and canonical URL. |
support-core-task-successclear-system-state-and-recovery | pass | high | The zero-result page clearly says no results and offers spelling, spacing, fewer-word, and alternate-translation recovery suggestions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.8s and CLS 0.699 on the passage (performance 49); the home also measured CLS 0.699. F10 high: The passage template misses good lab Core Web Vitals. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reported CLS 0.699; the mobile layout observer also recorded a 0.816 shift after late UI changes. All 25 passage images lack width/height attributes. F11 medium: Large late shifts make the page visually unstable. |
be-fast-and-stableefficient-main-thread | pass | high | Raw-CDP traces recorded zero long tasks and 0ms TBT; Lighthouse TBT was 130ms home and 200ms passage. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified synchronous head scripts init.min.js and otSDKStub.js; DOM confirmed neither async nor defer. Numerous cover images lacked cache headers. F12 medium: Parser-blocking and poorly cached resources delay content delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse identified about 122KB of OneTrust JavaScript and 19.6KB of consent CSS as largely unused, plus additional unused passage CSS/JS. F13 medium: The passage ships substantial unused consent and template code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 84 and failed button-name, aria-prohibited-attr, list semantics, and accessibility-tree checks; the image audit also found a missing alt attribute. F14 high: The passage has unnamed controls and invalid accessibility semantics. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color-contrast on both home and passage, with concrete failing nodes recorded in its audit tables. F15 medium: Some text and controls fail minimum color contrast. |
be-inclusivestructure-and-focus | issues | high | The home has no H1 and starts at H3; passage Lighthouse failed heading-order and list structure while finding a visible keyboard outline. F16 medium: Heading and list structure does not consistently match reading order. |
be-inclusivelegible-text | pass | medium | The verse uses readable sizing, spacing, and a fluid single-column layout without clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px both tested templates had zero horizontal overflow, yet probes counted 11 small controls on home and 43 on passage. F17 medium: Reflow works, but target sizing remains inadequate. |
follow-best-practicesno-console-errors | pass | high | The errors-in-console audit passed on both inspected templates. |
follow-best-practicessound-document-and-assets | issues | high | All 25 passage images lacked width/height and Lighthouse found an incorrectly displayed image aspect ratio. F18 medium: Image markup is not dimensionally sound. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | No deprecated API, paste prevention, on-load permission prompt, or vulnerable-library failure was reported; home best-practices scored 100. |
be-discoverabletitle-and-description | issues | high | The version probe found a descriptive title but no meta description. F19 low: The version-information template lacks a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO scored 92 on home and failed crawlable-anchors, although viewport metadata and most real href links were present. F20 medium: Some homepage links are not crawlable anchors. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical URLs were present, but /sitemap.xml returned HTTP 403 to the browser probe and no hreflang links were found on English pages despite an explicit Spanish version. F21 medium: Indexing signals are incomplete across a multilingual public site. |
be-discoverablestructured-and-shareable-metadata | issues | medium | The passage has accurate Open Graph fields but no JSON-LD; the version template has only a generic sharing image. F22 low: Rich public content lacks structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS were present, but the header audit found no CSP, X-Content-Type-Options, clickjacking protection, Referrer-Policy, or Permissions-Policy. Cookie evidence found OptanonConsent on .biblegateway.com with Secure=false, SameSite=Lax, and a 365-day expiry. F23 high: Core browser security headers are missing. F24 low: The consent cookie is not marked Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The consent UI describes 545 partners and device-characteristic scanning. The passage transferred 851,512 third-party bytes (78% of 1.09MB), including 413,746 bytes from OneTrust. F25 high: The consent and third-party footprint is disproportionate for a text-reading task. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The prominent Log In/Sign Up link resolves to a “Content Unavailable” page with no controls; no permission prompt fired on the inspected entry path. F26 medium: The advertised sign-in surface is unavailable, preventing a modern-auth experience. |
be-private-and-securedefensive-browser-policies | issues | high | The response had HSTS but no frame-ancestors/X-Frame-Options, Referrer-Policy, Permissions-Policy, CSP, or nosniff. F27 high: Browser-enforced defenses beyond HSTS are absent. |
be-resilientprogressive-enhancement | pass | high | The no-JS passage screenshot contains the search controls and full John 3:16 verse; the page is not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | At 360×800 the consent UI consumes roughly 650px before site navigation; DOM inspection found custom role=dialog markup rather than native dialog behavior. F28 medium: The consent layer is a fragile, oversized custom runtime surface. |
be-resilientoffline-and-installable | not-applicable | high | No manifest or controlling service worker is present. |
be-resilientnetwork-and-http-failure-states | issues | high | The login URL displays only “Content Unavailable” and an apology, with no retry, home link, support link, status detail, or alternate sign-in path. F29 medium: The account failure state offers no recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | Representative pages declare html lang=en and expose a Spanish-language switch; default LTR reading order renders correctly. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited templates contain Scripture text, search controls, and version metadata but no user-facing dates, currencies, durations, events, or time-zone calculations. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited templates contain Scripture text, search controls, and version metadata but no user-facing dates, currencies, durations, events, or time-zone calculations. |
be-trustworthyno-dark-patterns | issues | high | The full-screen notice names 545 partners, personalized advertising, device-characteristic scanning, and inference of religious or philosophical beliefs on a Bible-reading site. Reject is present, but the breadth and interruption undermine a privacy-minimizing default. F30 high: Consent asks users to authorize unusually broad sensitive profiling before content. |
be-trustworthyhumane-error-handling | pass | high | The no-results state avoids blame and gives four concrete recovery strategies. |
be-trustworthytrustworthy-input-assistance | issues | high | Home and passage probes show the newsletter Email field with autocomplete="off" and no visible label in the captured form metadata. F31 low: Email input explicitly disables autofill. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Log In/Sign Up links users to a noindex “Content Unavailable” page with no sign-in, cancellation, recovery, or support controls. F32 high: Account entry is a dead end. |
be-sustainableoptimised-assets | issues | high | The passage image audit found 24 legacy JPG/PNG images, 24 below-fold images not lazy-loaded, 25 without dimensions, and nearly all without responsive sources. F33 medium: Below-fold imagery is delivered in legacy, unstable markup. |
be-sustainableno-wasteful-work | issues | high | The passage made 76 requests, including 24 eager below-fold images and 26 fetch/XHR requests; 413KB of OneTrust resources dominated optional setup. F34 medium: The initial request graph fetches work unrelated to reading one verse. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR recorded 35 third-party requests and 851,512 third-party bytes out of 1,090,146 total; OneTrust alone used about 414KB. F35 high: Third parties consume most transferred bytes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No WebMCP tools, agentic form registration, or built-in inference surface is exposed. |
be-agent-readyon-device-inference | not-applicable | high | No WebMCP tools, agentic form registration, or built-in inference surface is exposed. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Total self size rose only 211,751 bytes (1.1%); closures decreased from 9,923 to 9,921 and Object/Array counts were essentially stable. |
be-memory-efficientbounded-footprint | pass | high | The loaded passage retained about 20MB self size with 363k heap nodes and 3,802 DOM elements, proportionate to the content-rich template. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared in either top summary; closures and arrays did not grow across snapshots. |
Provenance
Canonical report: results/atomic/reports/0387-www_biblegateway_com.json
Report SHA-256: 1d1c780727079a93338e08aaa3e9b8087c6fdc50fc896669345afe49a1b211ad
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_biblegateway_com/2026-07-20T10-14-24-952Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_biblegateway_com/2026-07-20T10-14-24-952Z
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.