snapp.ir

Readiness by lane

Green: snapp.ir. Thin bar: Ride-Hailing Services peer median.

Priority fixes for snapp.ir

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 60 seconds, 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   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: 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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   26% of Ride-Hailing Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   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 Next.js: Add it in next.config.js headers().

   63% of Ride-Hailing Services peers do this.

   Guide: A Practical Website Health Check for Owners

What snapp.ir 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
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.42% of peers

What we saw

Homepage checked

https://snapp.ir/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-20

Platform or framework

WordPress, Next.js

DNS operators

Alibaba Cloud DNS

DMARC policy

p=quarantine

Homepage HTML

244 KB, gzip

Images on homepage

87 (png 57, jpg 19, svg 8, webp 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

• go.yandex67
• grab.com70
• indrive.com59
• rapido.bike67
• wheelseye.com66

Ride-Hailing Services readiness benchmark