Website readiness profile · Snapshot 23 October 2026
pecheur.com
pecheur.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 80/100
- Ahead of
- 86%
- 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: pecheur.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
100/100
Peers 86
Harden
74/100
Peers 60
Accelerate
75/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for pecheur.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 45 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Cloudflare: Cloudflare Polish can convert images to WebP.
47% of E-Commerce & Marketplaces peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for pecheur.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 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
47% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for pecheur.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.
What pecheur.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- Referrer-Policy setReferrer-Policy present.20% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.32% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.pecheur.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
- DNS operators
- Gandi DNS
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=none
- Homepage HTML
- 160 KB, br
- Images on homepage
- 45 (png 29, jpg 12, svg 4)
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
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- 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 pecheur.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: pecheur.com. This profile covers configuration only.