haibunda.com

Readiness by lane

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

Priority fixes for haibunda.com

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

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

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   60% of Family & Heritage peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · 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

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   31% of Family & Heritage peers do this.

   Guide: CDN Guide for Website Owners

What haibunda.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
• Reachable over IPv6IPv6 address published.36% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.43% of peers

What we saw

Homepage checked

https://www.haibunda.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-24

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

234 KB, gzip

Images on homepage

80 (webp 26, png 26, jpg 23)

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

• care.com78
• famousbirthdays.com72
• findagrave.com74
• kekmama.nl82
• urbia.de82

Family & Heritage readiness benchmark