grow.google

Readiness by lane

Green: grow.google. Thin bar: Education & Online Learning peer median.

Priority fixes for grow.google

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   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.

   34% of Education & Online Learning 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

   Offscreen images lazy-loaded

   Observed: The homepage had 10 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   52% of Education & Online Learning peers do this.

   Guide: Lazy Loading Without Broken Pages

3. Priority 3 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

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

   5% of Education & Online Learning peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for grow.google at its parent zone, so its DNS answers are not DNSSEC-signed.

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

   8.1% of Education & Online Learning peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What grow.google already does well

Practices fewer than half of Education & Online Learning peers use.

• CAA records limit who can issue certificatesCAA limits issuance to pki.goog.13% of peers
• Content Security Policy presentContent-Security-Policy present.25% of peers
• HTTP/3 advertisedHTTP/3 advertised.25% of peers

What we saw

Homepage checked

https://grow.google/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Google edge

DNS operators

Google Cloud DNS

HSTS

max-age 30 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

117 KB, gzip

Images on homepage

10 (svg 2)

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 Education & Online Learning sites

• abcmouse.com84
• goodandbeautiful.com84
• grancursosonline.com.br84
• hotmart.com84
• lumni.fr84

Education & Online Learning readiness benchmark