Website readiness profile · Snapshot 23 October 2026
amazon.in
amazon.in's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 57/100
- Ahead of
- 13%
- Practices observed
- 13/26
- Popularity band
- Top 1K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
5 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: amazon.in. Thin bar: E-Commerce & Marketplaces peer median.
Enable
44/100
Peers 86
Harden
58/100
Peers 60
Accelerate
67/100
Peers 69
Recover
100/100
Peers 11
Priority fixes for amazon.in
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (4 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.
97% of E-Commerce & Marketplaces 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
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 · 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.
95% of E-Commerce & Marketplaces peers do this.
Guide: Meta Titles and Descriptions That Match Search Intent
Priority 4 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
85% of E-Commerce & Marketplaces peers do this.
What amazon.in already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- security.txt publishedsecurity.txt with a contact found.7.6% of peers
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
- HSTS kept for at least a yearHSTS with a 549-day max-age covering subdomains.32% of peers
What we saw
- Homepage checked
- https://www.amazon.in/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 363-day validity, expiring 2027-01-17
- CDN or edge
- Amazon CloudFront
- DNS operators
- 4 self-run or other nameserver domains
- HSTS
- max-age 549 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 4 KB, uncompressed
- Images on homepage
- 0
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 13
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
Observed 13
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTTP/3 advertised
- No render-blocking scripts in <head>
- Reachable over IPv6
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 5
- HTTP requests move to HTTPS
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
Own amazon.in?
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: amazon.in. This profile covers configuration only.