bigbasket.com

Readiness by lane

Green: bigbasket.com. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for bigbasket.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.bigbasket.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   96% of Food & Grocery Delivery peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 6 hours, short of the 30-day benchmark.

   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.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   On Next.js: The next/image component serves optimized formats automatically.

   40% of Food & Grocery Delivery peers do this.

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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   37% of Food & Grocery Delivery peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What bigbasket.com already does well

Practices fewer than half of Food & Grocery Delivery peers use.

• Referrer-Policy setReferrer-Policy present.27% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.42% of peers

What we saw

Homepage checked

https://www.bigbasket.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 364-day validity, expiring 2027-02-12

CDN or edge

Akamai

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

319 KB, br

Images on homepage

52 (jpg 46, png 6)

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

• daskochrezept.de67
• emmikochteinfach.de67
• heninthekitchen.com68
• hy-vee.com68
• picard.fr68

Food & Grocery Delivery readiness benchmark