Website readiness profile · Snapshot 23 October 2026
findagrave.com
findagrave.com's public homepage, certificate and DNS checked against 31 practices and compared with 69 Family & Heritage sites.
- Readiness index
- 74/100
- Ahead of
- 81%
- Practices observed
- 21/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: findagrave.com. Thin bar: Family & Heritage peer median.
Enable
87/100
Peers 80
Harden
82/100
Peers 61
Accelerate
53/100
Peers 60
Recover
0/100
Peers 7
Priority fixes for findagrave.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
43% of Family & Heritage peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 days, 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 Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
50% of Family & Heritage peers do this.
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
67% of Family & Heritage peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Accelerate
Modern image formats in use
Observed: The homepage had 4 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Cloudflare: Cloudflare Polish can convert images to WebP.
25% of Family & Heritage peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
What findagrave.com already does well
Practices fewer than half of Family & Heritage peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.10% of peers
- security.txt publishedsecurity.txt with a contact found.12% of peers
- HTTP/3 advertisedHTTP/3 advertised.31% of peers
What we saw
- Homepage checked
- https://www.findagrave.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-17
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 180 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 131 KB, br
- Images on homepage
- 4 (jpg 3, png 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
Not observed 7
Observed 21
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 3
- HTTP requests move to HTTPS
- CAA records limit who can issue certificates
- Offscreen images lazy-loaded
Own findagrave.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: findagrave.com. This profile covers configuration only.