go.yandex

Readiness by lane

Green: go.yandex. Thin bar: Ride-Hailing Services peer median.

Priority fixes for go.yandex

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.go.yandex.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   63% of Ride-Hailing Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for 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.

   26% of Ride-Hailing Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 13 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.

   82% of Ride-Hailing Services peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 13 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.

   33% of Ride-Hailing Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What go.yandex already does well

Practices fewer than half of Ride-Hailing Services peers use.

• Reachable over IPv6IPv6 address published.26% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.47% of peers
• Content Security Policy presentContent-Security-Policy present.47% of peers

What we saw

Homepage checked

https://go.yandex/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 181-day validity, expiring 2027-04-04

DNS operators

Yandex DNS

Homepage HTML

131 KB, gzip

Images on homepage

13

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 Ride-Hailing Services sites

• grab.com70
• rapido.bike67
• uber.com77
• wheelseye.com66
• yango.com71

Ride-Hailing Services readiness benchmark