STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

kakaoid.com

kakaoid.com's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.

Readiness index
53/100

Dating Apps median 58

Ahead of
36%

of measured Dating Apps sites

Practices observed
15/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:02:41 UTC from one location. How we measure

Readiness by lane

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

Enable

79/100

Peers 71

Harden

43/100

Peers 52

Accelerate

48/100

Peers 53

Recover

0/100

Peers 7

Priority fixes for kakaoid.com

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

  1. Priority 1 · Enable

    XML sitemap discoverable

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

    Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

    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. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.kakaoid.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.

  3. Priority 3 · Accelerate

    No render-blocking scripts in <head>

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

  4. Priority 4 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 4 hours, short of the 30-day benchmark.

    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 Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

    35% of Dating Apps peers do this.

What kakaoid.com already does well

Practices fewer than half of Dating Apps peers use.

  • HTTP/3 advertisedHTTP/3 advertised.18% of peers
  • Reachable over IPv6IPv6 address published.34% of peers

What we saw

Homepage checked
https://kakaoid.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2026-12-02
CDN or edge
Cloudflare
DNS operators
Cloudflare
Homepage HTML
25 KB, br
Images on homepage
13 (png 13)

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

Observed 15

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • robots.txt published
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own kakaoid.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: kakaoid.com. This profile covers configuration only.

Compare with other Dating Apps sites