wholefoodsmarket.com

Readiness by lane

Green: wholefoodsmarket.com. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for wholefoodsmarket.com

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   59% of Food & Grocery Delivery peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   42% of Food & Grocery Delivery peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for wholefoodsmarket.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.

   42% of Food & Grocery Delivery peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 47 images and none used WebP or AVIF.

   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 Next.js: The next/image component serves optimized formats automatically.

   40% of Food & Grocery Delivery peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What wholefoodsmarket.com already does well

Practices fewer than half of Food & Grocery Delivery peers use.

• Referrer-Policy setReferrer-Policy present.27% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• Content Security Policy presentContent-Security-Policy present.37% of peers

What we saw

Homepage checked

https://www.wholefoodsmarket.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-05

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 180 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

160 KB, gzip

Images on homepage

47 (jpg 102, png 14, svg 2)

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 Food & Grocery Delivery sites

• cookidoo.de61
• cookidoo.es61
• familienkost.de62
• gastronom.ru62
• sukesanudon.com62

Food & Grocery Delivery readiness benchmark