ourdream.ai

Readiness by lane

Green: ourdream.ai. Thin bar: Generative AI Chatbots & Assistants peer median.

Priority fixes for ourdream.ai

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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

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

   Guide: SEO Checklist for a New Website

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

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

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for ourdream.ai, so any public certificate authority may issue for it.

   What to do: 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.

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

   Guide: HTTPS and TLS Guide for Website Owners

What ourdream.ai already does well

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

• Content Security Policy presentContent-Security-Policy present.40% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.41% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age.46% of peers

What we saw

Homepage checked

https://ourdream.ai/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-31

CDN or edge

Vercel

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 730 days

DMARC policy

p=quarantine

Homepage HTML

410 KB, br

Images on homepage

31 (svg 4, webp 3, 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

Compare with other Generative AI Chatbots & Assistants sites

• copilot.com80
• deepai.org79
• giga.chat76
• justdone.com76
• v0.app79

Generative AI Chatbots & Assistants readiness benchmark