geni.com

Readiness by lane

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

Priority fixes for geni.com

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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.

   50% of Family & Heritage peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 48 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.

   25% of Family & Heritage peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

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

   39% of Family & Heritage peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 48 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   58% of Family & Heritage peers do this.

   Guide: Lazy Loading Without Broken Pages

What geni.com 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.43% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.46% of peers

What we saw

Homepage checked

https://www.geni.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 90-day validity, expiring 2026-12-09

CDN or edge

Imperva

DNS operators

NS1

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

146 KB, gzip

Images on homepage

48 (png 27, jpg 10, svg 9, gif 2)

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

• digitalarkivet.no67
• familie.de66
• familytreedna.com69
• stroller-envy.com67
• trauerhilfe.it68

Family & Heritage readiness benchmark