nounou-top.fr

Readiness by lane

Green: nounou-top.fr. Thin bar: Family & Heritage peer median.

Priority fixes for nounou-top.fr

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 2 days, 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.

   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. 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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for nounou-top.fr 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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 13 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 · Accelerate

   Offscreen images lazy-loaded

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

   On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.

   58% of Family & Heritage peers do this.

   Guide: Lazy Loading Without Broken Pages

What nounou-top.fr already does well

Practices fewer than half of Family & Heritage peers use.

• Modern image formats in useWebP or AVIF images detected.25% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age.43% of peers

What we saw

Homepage checked

https://www.nounou-top.fr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

ZeroSSL, 90-day validity, expiring 2026-11-29

Platform or framework

WordPress

DNS operators

OVHcloud DNS

HSTS

max-age 730 days

DMARC policy

p=none

Homepage HTML

100 KB, gzip

Images on homepage

42 (svg 32, webp 7, png 3)

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
• familytreedna.com69
• myheritage.nl71
• myheritage.pl71
• myheritage.se71

Family & Heritage readiness benchmark