wheelseye.com

Readiness by lane

Green: wheelseye.com. Thin bar: Ride-Hailing Services peer median.

Priority fixes for wheelseye.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   26% of Ride-Hailing Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

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

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   53% of Ride-Hailing Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

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.

   On Amazon CloudFront: Set frame options in a response headers policy.

   63% of Ride-Hailing Services peers do this.

   Guide: A Practical Website Health Check for Owners

What wheelseye.com already does well

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

• Modern image formats in useWebP or AVIF images detected.33% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.47% of peers

What we saw

Homepage checked

https://wheelseye.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-01

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

60 KB, gzip

Images on homepage

46 (svg 35, png 7, webp 4)

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

• go.yandex67
• grab.com70
• indrive.com59
• rapido.bike67
• snapp.ir64

Ride-Hailing Services readiness benchmark