STATUS IS UPWEBSITE READINESS

Stack playbook · Snapshot 23 October 2026

Nuxt on Cloudflare: readiness playbook

What 223 measured sites on this stack get right, where they fall short, and the Nuxt on Cloudflare-specific steps that close each gap.

Sites measured
223

detected from homepage HTML and headers

Median readiness index
70/100

all sites: 64

Profiles on this stack
121

top-50K sites

Readiness by lane

Enable

84/100

All sites 77

Harden

56/100

All sites 56

Accelerate

80/100

All sites 64

Recover

1/100

All sites 10

The Nuxt on Cloudflare playbook

Gaps ordered by impact, with the platform-specific step where one exists.

  1. HSTS kept for at least a year

    25% observed · all sites 34%

    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.

  2. CAA records limit who can issue certificates

    11% observed · all sites 13%

    Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

  3. security.txt published

    12% observed · all sites 7.1%

    Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

  4. DMARC policy enforces quarantine or reject

    41% observed · all sites 39%

    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.

  5. Content Security Policy present

    23% observed · all sites 32%

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

  6. Modern image formats in use

    55% observed · all sites 40%

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

    On Nuxt: Nuxt Image can output WebP and AVIF.

    On Cloudflare: Cloudflare Polish can convert images to WebP.

  7. DNSSEC signed

    11% observed · all sites 8%

    Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

    On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

  8. Framing restricted

    39% observed · all sites 51%

    Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

    On Cloudflare: Add the header with a response header transform rule.

Where Nuxt on Cloudflare sites lead

  • Reachable over IPv688% observedall sites 48%
  • No render-blocking scripts in <head>80% observedall sites 48%
  • HTTP/3 advertised63% observedall sites 37%
  • Certificate lifetime of 100 days or less90% observedall sites 67%

All 31 checks on Nuxt on Cloudflare

High-readiness Nuxt on Cloudflare sites

Related