lens.google

Readiness by lane

Green: lens.google. Thin bar: Search Engines peer median.

Priority fixes for lens.google

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

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   85% of Search Engines peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts 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.

   72% of Search Engines peers do this.

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

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   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.

   51% of Search Engines peers do this.

   Guide: A Practical Website Health Check for Owners

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

   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.

   30% of Search Engines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What lens.google already does well

Practices fewer than half of Search Engines peers use.

• Content Security Policy presentContent-Security-Policy present.28% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers

What we saw

Homepage checked

https://lens.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=none

Homepage HTML

78 KB, gzip

Images on homepage

22 (svg 13, webp 9)

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 Search Engines sites

• businesslist.com.ng70
• hitta.se69
• hot.com73
• paginebianche.it68
• search.ch73

Search Engines readiness benchmark