labs.google

Readiness by lane

Green: labs.google. Thin bar: Generative AI Chatbots & Assistants peer median.

Priority fixes for labs.google

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://labs.google/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   96% of Generative AI Chatbots & Assistants peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 600 seconds, 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.

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

   Guide: Browser Caching Guide for Website Owners

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.

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

   Guide: HTTPS and TLS Guide for Website 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.

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

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

What labs.google already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to pki.goog.28% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers

What we saw

Homepage checked

https://labs.google/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 83-day validity, expiring 2026-12-21

CDN or edge

Google edge

Platform or framework

Angular

DNS operators

Google Cloud DNS

DMARC policy

p=reject

Homepage HTML

290 KB, gzip

Images on homepage

25 (webp 28)

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

• bigmodel.cn64
• chatbot.app63
• chub.ai64
• minimax.io65
• neurosphere.pro64

Generative AI Chatbots & Assistants readiness benchmark