cabify.com

Readiness by lane

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

Priority fixes for cabify.com

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 no max-age, 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.

   47% of Ride-Hailing Services 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: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 23 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 23 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 cabify.com already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org.21% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers
• Referrer-Policy setReferrer-Policy present.37% of peers

What we saw

Homepage checked

https://cabify.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-01

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 0 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

106 KB, gzip

Images on homepage

23 (svg 18, jpg 3, png 2)

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

• bolt.eu82
• grab.com70
• lyft.com80
• uber.com77
• yango.com71

Ride-Hailing Services readiness benchmark