Website readiness profile · Snapshot 23 October 2026
gocharting.com
gocharting.com's public homepage, certificate and DNS checked against 31 practices and compared with 241 Stock & Crypto Trading sites.
- Readiness index
- 72/100
- Ahead of
- 58%
- Practices observed
- 20/31
- Popularity band
- Top 50K
Stock & Crypto Trading median 69
of measured Stock & Crypto Trading sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: gocharting.com. Thin bar: Stock & Crypto Trading peer median.
Enable
100/100
Peers 82
Harden
54/100
Peers 61
Accelerate
78/100
Peers 67
Recover
0/100
Peers 6
Priority fixes for gocharting.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
44% of Stock & Crypto Trading peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
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.
51% of Stock & Crypto Trading peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · 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.
On Cloudflare: Add the header with a response header transform rule.
60% of Stock & Crypto Trading peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
40% of Stock & Crypto Trading peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What gocharting.com already does well
Practices fewer than half of Stock & Crypto Trading peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.15% of peers
- Reachable over IPv6IPv6 address published.46% of peers
- Modern image formats in useWebP or AVIF images detected.48% of peers
What we saw
- Homepage checked
- https://gocharting.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-10
- CDN or edge
- Cloudflare, Amazon CloudFront
- Platform or framework
- Astro
- DNS operators
- Amazon Route 53
- DMARC policy
- p=reject
- Homepage HTML
- 282 KB, br
- Images on homepage
- 74 (png 51, webp 11, avif 6, jpg 6, svg 5)
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 11
Observed 20
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- 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 gocharting.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: gocharting.com. This profile covers configuration only.