Website readiness profile · Snapshot 23 October 2026
familysearch.org
familysearch.org's public homepage, certificate and DNS checked against 31 practices and compared with 69 Family & Heritage sites.
- Readiness index
- 60/100
- Ahead of
- 22%
- Practices observed
- 13/28
- Popularity band
- Top 5K
Family & Heritage median 67
of measured Family & Heritage sites
3 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: familysearch.org. Thin bar: Family & Heritage peer median.
Enable
62/100
Peers 80
Harden
71/100
Peers 61
Accelerate
33/100
Peers 60
Recover
0/100
Peers 7
Priority fixes for familysearch.org
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.
90% of Family & Heritage peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
75% of Family & Heritage peers do this.
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script 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.
39% of Family & Heritage peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Enable
At most one redirect to the homepage
Observed: The homepage was reached after 2 redirects.
What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.
97% of Family & Heritage peers do this.
What familysearch.org already does well
Practices fewer than half of Family & Heritage peers use.
- Content Security Policy presentContent-Security-Policy present.34% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.43% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.46% of peers
What we saw
- Homepage checked
- https://www.familysearch.org/
- Homepage response
- HTTP 200, after 2 redirects
- TLS
- TLSv1.3
- Certificate
- DigiCert, 198-day validity, expiring 2027-03-03
- CDN or edge
- Amazon CloudFront, Imperva, Heroku
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=quarantine
- Homepage HTML
- 19 KB, gzip
- Images on homepage
- 0
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
Not observed 15
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- No render-blocking scripts in <head>
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
- At most one redirect to the homepage
- Nameservers spread across providers
Observed 13
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- HTML compressed
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Page language declared
Not measured 3
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
Own familysearch.org?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: familysearch.org. This profile covers configuration only.