Website readiness profile · Snapshot 23 October 2026
efarma.com
efarma.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 85/100
- Ahead of
- 97%
- Practices observed
- 24/31
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: efarma.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
92/100
Peers 86
Harden
74/100
Peers 60
Accelerate
100/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for efarma.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
Why it matters: A CSP limits where scripts, styles and frames can load from, which reduces the impact of injected or compromised third-party code.
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.
48% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 2 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
60% of E-Commerce & Marketplaces peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for efarma.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 efarma.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.32% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.efarma.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-15
- CDN or edge
- Cloudflare, Fastly
- Platform or framework
- Magento / Adobe Commerce
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 656 KB, br
- Images on homepage
- 100 (svg 29, png 23, jpg 21, webp 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 7
Observed 24
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- 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
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Own efarma.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: efarma.com. This profile covers configuration only.