Website readiness profile · Snapshot 23 October 2026
play.google
play.google's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 72/100
- Ahead of
- 54%
- Practices observed
- 20/30
- Popularity band
- Top 10K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: play.google. Thin bar: E-Commerce & Marketplaces peer median.
Enable
59/100
Peers 86
Harden
77/100
Peers 60
Accelerate
82/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for play.google
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
Modern image formats in use
Observed: The homepage had 208 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
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for play.google 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.
What play.google already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- CAA records limit who can issue certificatesCAA limits issuance to pki.goog.16% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://play.google/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 83-day validity, expiring 2026-12-21
- CDN or edge
- Google edge
- DNS operators
- Google Cloud DNS
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 3,116 KB, gzip
- Images on homepage
- 208 (jpg 54, png 3)
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 10
Observed 20
- 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
- CAA records limit who can issue certificates
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Static files cached for 30 days or more
Own play.google?
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: play.google. This profile covers configuration only.