Website readiness profile · Snapshot 23 October 2026
pittarello.com
pittarello.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 84/100
- Ahead of
- 94%
- Practices observed
- 25/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: pittarello.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
100/100
Peers 86
Harden
75/100
Peers 60
Accelerate
85/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for pittarello.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 300 seconds, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
60% 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
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.
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.
Priority 3 · 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.
Priority 4 · Harden
DNSSEC signed
Observed: No DS record was found for pittarello.com at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.
7.7% of E-Commerce & Marketplaces peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
What pittarello.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com, letsencrypt.org and others.16% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.pittarello.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-11-28
- CDN or edge
- Cloudflare, Shopify
- Platform or framework
- Shopify
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 91 days
- DMARC policy
- p=reject
- Homepage HTML
- 2,653 KB, br
- Images on homepage
- 120 (jpg 904, webp 284, png 166, svg 122)
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 6
Observed 25
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- 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
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own pittarello.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: pittarello.com. This profile covers configuration only.