gastronom.ru

Readiness by lane

Green: gastronom.ru. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for gastronom.ru

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · 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.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · 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.

   42% of Food & Grocery Delivery peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 74 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   63% of Food & Grocery Delivery peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   56% of Food & Grocery Delivery peers do this.

   Guide: A Practical Website Health Check for Owners

What gastronom.ru 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
• Modern image formats in useWebP or AVIF images detected.40% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.42% of peers

What we saw

Homepage checked

https://www.gastronom.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2027-05-06

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

459 KB, br

Images on homepage

74 (webp 109, 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

Compare with other Food & Grocery Delivery sites

• dominos.com62
• familienkost.de62
• sukesanudon.com62
• talabat.com63
• wholefoodsmarket.com62

Food & Grocery Delivery readiness benchmark