ninisite.com

Readiness by lane

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

Priority fixes for ninisite.com

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Asseco Data Systems S.A. was due to expire on 2026-11-06 (13 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for ninisite.com was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   46% of Family & Heritage peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 80 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 ninisite.com already does well

Practices fewer than half of Family & Heritage peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.43% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://www.ninisite.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Asseco Data Systems S.A., 394-day validity, expiring 2026-11-06

DNS operators

ClouDNS

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

271 KB, gzip

Images on homepage

80 (png 73, jpg 6, svg 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

• kidsline.me64
• nostrofiglio.it63
• rip.ie66
• scotlandspeople.gov.uk64
• smartsitter.jp66

Family & Heritage readiness benchmark