Website readiness profile · Snapshot 23 October 2026
starbucks.co.jp
starbucks.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 54/100
- Ahead of
- 9.8%
- Practices observed
- 16/31
- Popularity band
- Top 10K
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: starbucks.co.jp. Thin bar: E-Commerce & Marketplaces peer median.
Enable
69/100
Peers 86
Harden
54/100
Peers 60
Accelerate
38/100
Peers 69
Recover
100/100
Peers 11
Priority fixes for starbucks.co.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
95% of E-Commerce & Marketplaces peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 2 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
87% of E-Commerce & Marketplaces peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 600 seconds, 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.
60% of E-Commerce & Marketplaces peers do this.
Priority 4 · Accelerate
Modern image formats in use
Observed: The homepage had 76 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.
47% of E-Commerce & Marketplaces peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
What starbucks.co.jp already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.7.7% of peers
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
What we saw
- Homepage checked
- https://www.starbucks.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 396-day validity, expiring 2027-03-31
- CDN or edge
- Amazon CloudFront
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 0 days, includeSubDomains
- DMARC policy
- p=none
- Homepage HTML
- 75 KB, gzip
- Images on homepage
- 76 (jpg 38, svg 32, png 1)
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 15
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- security.txt published
- DMARC policy enforces quarantine or reject
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
Observed 16
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- 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
- Nameservers spread across providers
Own starbucks.co.jp?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: starbucks.co.jp. This profile covers configuration only.