Website readiness profile · Snapshot 23 October 2026
mollygram.com
mollygram.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 58/100
- Ahead of
- 20%
- Practices observed
- 17/31
- Popularity band
- Top 10K
Web Tools median 67
of measured Web Tools sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: mollygram.com. Thin bar: Web Tools peer median.
Enable
87/100
Peers 84
Harden
40/100
Peers 55
Accelerate
60/100
Peers 69
Recover
0/100
Peers 6
Priority fixes for mollygram.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.
92% of Web Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 8 days, 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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
54% of Web Tools peers do this.
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.
73% of Web Tools peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · 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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
30% of Web Tools peers do this.
What mollygram.com already does well
Practices fewer than half of Web Tools peers use.
- Framing restrictedFraming controls present.48% of peers
What we saw
- Homepage checked
- https://mollygram.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-01
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- Homepage HTML
- 81 KB, br
- Images on homepage
- 36 (svg 27, jpg 7, png 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 14
- HSTS kept for at least a year
- TLS 1.3 negotiated
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Content Security Policy present
- Referrer-Policy set
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- XML sitemap discoverable
- Nameservers spread across providers
Observed 17
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own mollygram.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: mollygram.com. This profile covers configuration only.