biblegateway.com

Readiness by lane

Green: biblegateway.com. Thin bar: Literary & Knowledge peer median.

Priority fixes for biblegateway.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

   69% of Literary & Knowledge peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   49% of Literary & Knowledge peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 90 days, below the one-year benchmark.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   48% of Literary & Knowledge peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What biblegateway.com already does well

Practices fewer than half of Literary & Knowledge peers use.

• security.txt publishedsecurity.txt with a contact found.5% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, letsencrypt.org.13% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers

What we saw

Homepage checked

https://www.biblegateway.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-07

CDN or edge

Amazon CloudFront

Platform or framework

WordPress, Shopify

DNS operators

Amazon Route 53

HSTS

max-age 90 days

DMARC policy

p=reject

Homepage HTML

154 KB, gzip

Images on homepage

14 (jpg 8, png 5, gif 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Literary & Knowledge sites

• aruuz.com58
• bilinovel.com58
• homeread.net58
• surahquran.com59
• toolsjw.com59

Literary & Knowledge readiness benchmark