Website readiness profile · Snapshot 23 October 2026
sinsay.com
sinsay.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 63/100
- Ahead of
- 27%
- Practices observed
- 16/29
- Popularity band
- Top 5K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: sinsay.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
69/100
Peers 86
Harden
43/100
Peers 60
Accelerate
100/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for sinsay.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://www.sinsay.com/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
96% of E-Commerce & Marketplaces peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · 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.
32% of E-Commerce & Marketplaces peers do this.
Priority 3 · Enable
At most one redirect to the homepage
Observed: The homepage was reached after 3 redirects.
What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.
98% of E-Commerce & Marketplaces peers do this.
Priority 4 · Enable
Page language declared
Observed: The homepage <html> element had no lang attribute.
What to do: Set lang on the html element (for example lang="en") and on any sections in another language.
96% of E-Commerce & Marketplaces peers do this.
What sinsay.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
- Reachable over IPv6IPv6 address published.40% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
What we saw
- Homepage checked
- https://www.sinsay.com/
- Homepage response
- HTTP 200, after 3 redirects
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2027-02-17
- DNS operators
- Akamai Edge DNS
- HSTS
- max-age 30 days, includeSubDomains
- DMARC policy
- p=quarantine
- Homepage HTML
- 8 KB, gzip
- Images on homepage
- 1 (svg 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 13
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- Content Security Policy present
- Referrer-Policy set
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Observed 16
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own sinsay.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: sinsay.com. This profile covers configuration only.