familytreedna.com

Readiness by lane

Green: familytreedna.com. Thin bar: Family & Heritage peer median.

Priority fixes for familytreedna.com

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

1. 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.

   90% of Family & Heritage peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

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.

   50% of Family & Heritage peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 5 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.

   39% of Family & Heritage peers do this.

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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   34% of Family & Heritage peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What familytreedna.com already does well

Practices fewer than half of Family & Heritage peers use.

• Modern image formats in useWebP or AVIF images detected.25% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.28% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.43% of peers

What we saw

Homepage checked

https://www.familytreedna.com/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

GoDaddy, 397-day validity, expiring 2027-02-22

Platform or framework

WordPress

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

226 KB, gzip

Images on homepage

20 (png 57, webp 10, 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 Family & Heritage sites

• aarp.org69
• digitalarkivet.no67
• myheritage.se71
• nounou-top.fr70
• trauerhilfe.it68

Family & Heritage readiness benchmark