starbucks.com.mx

Readiness by lane

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

Priority fixes for starbucks.com.mx

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (80 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

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

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · 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.

   42% of Food & Grocery Delivery peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   93% of Food & Grocery Delivery peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 6 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.

   40% of Food & Grocery Delivery peers do this.

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

What starbucks.com.mx already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.12% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.42% of peers
• Reachable over IPv6IPv6 address published.49% of peers

What we saw

Homepage checked

https://www.starbucks.com.mx/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 365-day validity, expiring 2027-01-23

CDN or edge

Amazon CloudFront

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

80 KB, uncompressed

Images on homepage

6 (png 10)

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

• bobs.com.br56
• foodsharing.de55
• kalleh.com57
• nosalty.hu57
• snapp.market55

Food & Grocery Delivery readiness benchmark