STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

kiddle.co

kiddle.co's public homepage, certificate and DNS checked against 31 practices and compared with 59 Search Engines sites.

Readiness index
49/100

Search Engines median 65

Ahead of
12%

of measured Search Engines sites

Practices observed
12/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:52:36 UTC from one location. How we measure

Readiness by lane

Green: kiddle.co. Thin bar: Search Engines peer median.

Enable

67/100

Peers 74

Harden

48/100

Peers 57

Accelerate

36/100

Peers 68

Recover

0/100

Peers 8

Priority fixes for kiddle.co

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    92% of Search Engines 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 no max-age, 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.

    62% of Search Engines peers do this.

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

    30% of Search Engines peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

    Observed: The homepage had 4 images and none used WebP or AVIF.

    What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

    31% of Search Engines peers do this.

What we saw

Homepage checked
https://www.kiddle.co/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
GoDaddy, 198-day validity, expiring 2027-01-18
DNS operators
GoDaddy DNS
DMARC policy
p=reject
Homepage HTML
8 KB, gzip
Images on homepage
4 (png 2, svg 1, 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

Observed 12

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Meta description written
  • Mobile viewport configured
  • At most one redirect to the homepage

Not measured 1

  • Offscreen images lazy-loaded

Own kiddle.co?

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: kiddle.co. This profile covers configuration only.

Compare with other Search Engines sites