easy.com.ar

Readiness by lane

Green: easy.com.ar. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for easy.com.ar

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.easy.com.ar/ 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.

   On Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.

   96% of E-Commerce & Marketplaces peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   93% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   32% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for easy.com.ar 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.

   Guide: A Practical Website Health Check for Owners

What easy.com.ar already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• 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

What we saw

Homepage checked

https://www.easy.com.ar/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2026-12-14

CDN or edge

Amazon CloudFront

DNS operators

4 self-run or other nameserver domains

DMARC policy

p=none

Homepage HTML

2,568 KB, gzip

Images on homepage

57 (webp 30, png 13, svg 12, gif 1, jpg 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

Compare with other E-Commerce & Marketplaces sites

• cropp.com59
• decorte.com59
• deghi.it59
• expert.it59
• farmaciasdesimilares.com59

E-Commerce & Marketplaces readiness benchmark