Website readiness profile · Snapshot 23 October 2026
ootoya.com
ootoya.com's public homepage, certificate and DNS checked against 31 practices and compared with 413 Food & Grocery Delivery sites.
- Readiness index
- 40/100
- Ahead of
- 2.4%
- Practices observed
- 11/31
- Popularity band
- Top 50K
Food & Grocery Delivery median 68
of measured Food & Grocery Delivery sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: ootoya.com. Thin bar: Food & Grocery Delivery peer median.
Enable
51/100
Peers 85
Harden
38/100
Peers 59
Accelerate
30/100
Peers 64
Recover
100/100
Peers 12
Priority fixes for ootoya.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (57 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
Priority 2 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
91% of Food & Grocery Delivery peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 3 · 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 Food & Grocery Delivery peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, 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.
59% of Food & Grocery Delivery peers do this.
What ootoya.com 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
- No render-blocking scripts in <head>Head scripts load without blocking.43% of peers
What we saw
- Homepage checked
- https://www.ootoya.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-08
- CDN or edge
- Amazon CloudFront
- DNS operators
- 2 self-run or other nameserver domains
- Homepage HTML
- 57 KB, uncompressed
- Images on homepage
- 50 (jpg 47, svg 7, png 5)
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 20
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Structured data present
Observed 11
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- No render-blocking scripts in <head>
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own ootoya.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: ootoya.com. This profile covers configuration only.