Website readiness profile · Snapshot 23 October 2026
tatamutualfund.com
tatamutualfund.com's public homepage, certificate and DNS checked against 31 practices and compared with 241 Stock & Crypto Trading sites.
- Readiness index
- 77/100
- Ahead of
- 73%
- Practices observed
- 22/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: tatamutualfund.com. Thin bar: Stock & Crypto Trading peer median.
Enable
95/100
Peers 82
Harden
68/100
Peers 61
Accelerate
78/100
Peers 67
Recover
0/100
Peers 6
Priority fixes for tatamutualfund.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · 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.
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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
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.
On Next.js: Use the next/script component with an appropriate loading strategy.
51% of Stock & Crypto Trading peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.
36% of Stock & Crypto Trading peers do this.
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
60% of Stock & Crypto Trading peers do this.
What tatamutualfund.com already does well
Practices fewer than half of Stock & Crypto Trading peers use.
- Referrer-Policy setReferrer-Policy present.38% of peers
- Content Security Policy presentContent-Security-Policy present.40% of peers
- Modern image formats in useWebP or AVIF images detected.48% of peers
What we saw
- Homepage checked
- https://www.tatamutualfund.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-02-18
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 0 days
- DMARC policy
- p=reject
- Homepage HTML
- 466 KB, gzip
- Images on homepage
- 67 (svg 35, webp 22, png 6, avif 2, jpg 2)
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 9
Observed 22
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- 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
- 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 tatamutualfund.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: tatamutualfund.com. This profile covers configuration only.