Website readiness profile · Snapshot 23 October 2026
g4nd.com
g4nd.com's public homepage, certificate and DNS checked against 31 practices and compared with 87 SEO & Email Marketing sites.
- Readiness index
- 51/100
- Ahead of
- 20%
- Practices observed
- 13/29
- Popularity band
- Top 50K
SEO & Email Marketing median 62
of measured SEO & Email Marketing sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: g4nd.com. Thin bar: SEO & Email Marketing peer median.
Enable
38/100
Peers 77
Harden
48/100
Peers 55
Accelerate
80/100
Peers 66
Recover
0/100
Peers 3
Priority fixes for g4nd.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
58% of SEO & Email Marketing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
79% of SEO & Email Marketing peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
71% of SEO & Email Marketing peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 0 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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
36% of SEO & Email Marketing peers do this.
What g4nd.com already does well
Practices fewer than half of SEO & Email Marketing peers use.
- HTTP/3 advertisedHTTP/3 advertised.41% of peers
- X-Content-Type-Options: nosniffnosniff header present.41% of peers
What we saw
- Homepage checked
- https://g4nd.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-18
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 0 days
- Homepage HTML
- 7 KB, gzip
- Images on homepage
- 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
Not observed 16
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 13
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- Reachable over IPv6
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own g4nd.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: g4nd.com. This profile covers configuration only.