tik.ninja

Readiness by lane

Green: tik.ninja. Thin bar: Web Tools peer median.

Priority fixes for tik.ninja

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   30% of Web Tools peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 3 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.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   37% of Web Tools peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   66% of Web Tools peers do this.

   Guide: SEO Checklist for a New Website

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   15% of Web Tools peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What tik.ninja already does well

Practices fewer than half of Web Tools peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
• Referrer-Policy setReferrer-Policy present.30% of peers
• X-Content-Type-Options: nosniffnosniff header present.44% of peers

What we saw

Homepage checked

https://tik.ninja/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-18

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

151 KB, br

Images on homepage

3 (jpg 3)

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 Web Tools sites

• 24timezones.com75
• omnicalculator.com76
• paste-l.ink76
• pindown.io76
• tomitingo.com76

Web Tools readiness benchmark