caveduck.io

Readiness by lane

Green: caveduck.io. Thin bar: Generative AI Chatbots & Assistants peer median.

Priority fixes for caveduck.io

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

1. Priority 1 · Accelerate

   Modern image formats in use

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

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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.

   67% of Generative AI Chatbots & Assistants peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   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.

   46% of Generative AI Chatbots & Assistants peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for caveduck.io was p=none, which asks receivers to take no action on failing mail.

   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.

   41% of Generative AI Chatbots & Assistants peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   44% of Generative AI Chatbots & Assistants peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What caveduck.io already does well

Practices fewer than half of Generative AI Chatbots & Assistants peers use.

• Referrer-Policy setReferrer-Policy present.35% of peers
• X-Content-Type-Options: nosniffnosniff header present.46% of peers

What we saw

Homepage checked

https://caveduck.io/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-20

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 180 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

666 KB, br

Images on homepage

10 (png 66, svg 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 Generative AI Chatbots & Assistants sites

• clank.world69
• meraprompt.com70
• notegpt.io71
• prompthero.com70
• talkie-ai.com69

Generative AI Chatbots & Assistants readiness benchmark