about.google

Readiness by lane

Green: about.google. Thin bar: Uncategorized peer median.

Priority fixes for about.google

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

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

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   39% of Uncategorized peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

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

   37% of Uncategorized peers do this.

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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 8 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 Uncategorized peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

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

   43% of Uncategorized peers do this.

   Guide: A Practical Website Health Check for Owners

What about.google already does well

Practices fewer than half of Uncategorized peers use.

• CAA records limit who can issue certificatesCAA limits issuance to pki.goog.8.7% of peers
• Content Security Policy presentContent-Security-Policy present.24% of peers
• Modern image formats in useWebP or AVIF images detected.33% of peers

What we saw

Homepage checked

https://about.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

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

130 KB, gzip

Images on homepage

8 (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 Uncategorized sites

• 10elotto5minuti.com79
• astroyogi.com80
• backenmachtgluecklich.de78
• bestgore.fun79
• mon-horoscope-du-jour.com80

Uncategorized readiness benchmark