Website readiness profile · Snapshot 23 October 2026
coto.com.ar
coto.com.ar's public homepage, certificate and DNS checked against 31 practices and compared with 413 Food & Grocery Delivery sites.
- Readiness index
- 37/100
- Ahead of
- 1.7%
- Practices observed
- 9/27
- Popularity band
- Top 50K
Food & Grocery Delivery median 68
of measured Food & Grocery Delivery sites
4 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: coto.com.ar. Thin bar: Food & Grocery Delivery peer median.
Enable
65/100
Peers 85
Harden
11/100
Peers 59
Accelerate
57/100
Peers 64
Recover
0/100
Peers 12
Priority fixes for coto.com.ar
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate has more than 14 days left
Observed: The certificate from DigiCert Inc was due to expire on 2026-10-30 (7 days after the check).
Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.
What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.
99% of Food & Grocery Delivery peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
93% of Food & Grocery Delivery peers do this.
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
59% of Food & Grocery Delivery peers do this.
Priority 4 · 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.
42% of Food & Grocery Delivery peers do this.
What coto.com.ar already does well
Practices fewer than half of Food & Grocery Delivery peers use.
- HTTP/3 advertisedHTTP/3 advertised.35% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.43% of peers
What we saw
- Homepage checked
- https://www.coto.com.ar/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- DigiCert, 396-day validity, expiring 2026-10-30
- DNS operators
- 1 self-run or other nameserver domain
- Homepage HTML
- 4 KB, gzip
- Images on homepage
- 0
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 18
- HSTS kept for at least a year
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- Static files cached for 30 days or more
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 9
- TLS 1.3 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 4
- HTTP requests move to HTTPS
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
Own coto.com.ar?
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: coto.com.ar. This profile covers configuration only.