STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

ktoto.info

ktoto.info's public homepage, certificate and DNS checked against 31 practices and compared with 190 Ratings & Reviews sites.

Readiness index
49/100

Ratings & Reviews median 66

Ahead of
8.4%

of measured Ratings & Reviews sites

Practices observed
12/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:45:55 UTC from one location. How we measure

Readiness by lane

Green: ktoto.info. Thin bar: Ratings & Reviews peer median.

Enable

64/100

Peers 82

Harden

34/100

Peers 54

Accelerate

67/100

Peers 68

Recover

0/100

Peers 6

Priority fixes for ktoto.info

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.

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

  2. Priority 2 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 300 seconds, 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.

    64% of Ratings & Reviews peers do this.

  3. 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.

    72% of Ratings & Reviews peers do this.

  4. Priority 4 · Harden

    HSTS kept for at least a year

    Observed: The homepage response did not include a Strict-Transport-Security header.

    What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

    31% of Ratings & Reviews peers do this.

What we saw

Homepage checked
https://www.ktoto.info/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2026-12-29
DNS operators
1 self-run or other nameserver domain
Homepage HTML
24 KB, br
Images on homepage
1 (png 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

Observed 12

  • HTTP requests move to HTTPS
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own ktoto.info?

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: ktoto.info. This profile covers configuration only.

Compare with other Ratings & Reviews sites