Website readiness profile · Snapshot 23 October 2026
kanajo.com
kanajo.com's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.
- Readiness index
- 39/100
- Ahead of
- 11%
- Practices observed
- 9/30
- Popularity band
- Top 50K
Dating Apps median 58
of measured Dating Apps sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: kanajo.com. Thin bar: Dating Apps peer median.
Enable
46/100
Peers 71
Harden
34/100
Peers 52
Accelerate
42/100
Peers 53
Recover
0/100
Peers 7
Priority fixes for kanajo.com
Ordered by impact and by how common each practice is among peers.
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.
Priority 2 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
88% of Dating Apps peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 3 · 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
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.kanajo.com.
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.
What we saw
- Homepage checked
- https://kanajo.com/
- Homepage response
- HTTP 200, after 2 redirects
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-11-29
- DNS operators
- 1 self-run or other nameserver domain
- Homepage HTML
- 6 KB, gzip
- Images on homepage
- 5 (jpg 4)
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
Not observed 21
- HSTS kept for at least a year
- TLS 1.3 negotiated
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Social preview image set
- At most one redirect to the homepage
- Nameservers spread across providers
Observed 9
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTML compressed
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
Not measured 1
- Offscreen images lazy-loaded
Own kanajo.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: kanajo.com. This profile covers configuration only.