Website readiness profile · Snapshot 23 October 2026
sefam.com
sefam.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 78/100
- Ahead of
- 78%
- Practices observed
- 22/30
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: sefam.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
95/100
Peers 86
Harden
53/100
Peers 60
Accelerate
100/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for sefam.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 91 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
32% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for sefam.com was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
39% of E-Commerce & Marketplaces peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for sefam.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
16% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
7.6% of E-Commerce & Marketplaces peers do this.
What sefam.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
- Modern image formats in useWebP or AVIF images detected.47% of peers
- HTTP/3 advertisedHTTP/3 advertised.47% of peers
What we saw
- Homepage checked
- https://sefam.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-19
- CDN or edge
- Cloudflare, Shopify
- Platform or framework
- Shopify
- DNS operators
- Azure DNS
- HSTS
- max-age 91 days
- DMARC policy
- p=none
- Homepage HTML
- 2,530 KB, br
- Images on homepage
- 157 (jpg 376, webp 6, png 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 8
Observed 22
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- 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
Not measured 1
- HTTP requests move to HTTPS
Own sefam.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: sefam.com. This profile covers configuration only.