nzdating.com

Readiness by lane

Green: nzdating.com. Thin bar: Dating Apps peer median.

Priority fixes for nzdating.com

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   82% of Dating Apps 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 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   64% of Dating Apps peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for nzdating.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.

   42% of Dating Apps peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

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

   54% of Dating Apps peers do this.

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

What nzdating.com already does well

Practices fewer than half of Dating Apps peers use.

• Referrer-Policy setReferrer-Policy present.17% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.35% of peers
• X-Content-Type-Options: nosniffnosniff header present.40% of peers

What we saw

Homepage checked

https://www.nzdating.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 366-day validity, expiring 2027-02-19

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 90 days

DMARC policy

p=none

Homepage HTML

39 KB, br

Images on homepage

40 (gif 36, png 3, jpg 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 Dating Apps sites

• ange.gift47
• celibouest.com50
• liruch.com51
• simpatie.ro50
• tvojerande.cz48

Dating Apps readiness benchmark