Website readiness profile · Snapshot 23 October 2026
russianfood.com
russianfood.com's public homepage, certificate and DNS checked against 31 practices and compared with 413 Food & Grocery Delivery sites.
- Readiness index
- 48/100
- Ahead of
- 7.3%
- Practices observed
- 12/31
- Popularity band
- Top 1K
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: russianfood.com. Thin bar: Food & Grocery Delivery peer median.
Enable
54/100
Peers 85
Harden
52/100
Peers 59
Accelerate
38/100
Peers 64
Recover
0/100
Peers 12
Priority fixes for russianfood.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.
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. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 days, 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.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
59% of Food & Grocery Delivery peers do this.
Priority 3 · 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
42% of Food & Grocery Delivery peers do this.
Priority 4 · Accelerate
Modern image formats in use
Observed: The homepage had 71 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.
On Cloudflare: Cloudflare Polish can convert images to WebP.
40% of Food & Grocery Delivery peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
What russianfood.com already does well
Practices fewer than half of Food & Grocery Delivery peers use.
- 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.russianfood.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-11-30
- CDN or edge
- Cloudflare
- DNS operators
- Linode/Akamai DNS
- DMARC policy
- p=reject
- Homepage HTML
- 395 KB, br
- Images on homepage
- 71 (gif 36, jpg 32, svg 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 19
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- 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>
- XML sitemap discoverable
- Canonical URL declared
- Structured data present
- Social preview image set
- Page language declared
- Nameservers spread across providers
Observed 12
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- robots.txt published
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- At most one redirect to the homepage
Own russianfood.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: russianfood.com. This profile covers configuration only.