district.in

Readiness by lane

Green: district.in. Thin bar: Events & Online Ticketing peer median.

Priority fixes for district.in

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

   42% of Events & Online Ticketing 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

   Modern image formats in use

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

   42% of Events & Online Ticketing peers do this.

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

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 Next.js: Use the next/script component with an appropriate loading strategy.

   35% of Events & Online Ticketing peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

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

   54% of Events & Online Ticketing peers do this.

   Guide: Lazy Loading Without Broken Pages

What district.in already does well

Practices fewer than half of Events & Online Ticketing peers use.

• HTTP/3 advertisedHTTP/3 advertised.24% of peers
• Reachable over IPv6IPv6 address published.35% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.44% of peers

What we saw

Homepage checked

https://www.district.in/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-01-21

CDN or edge

Akamai

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

777 KB, gzip

Images on homepage

8 (jpg 4, svg 2, 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 Events & Online Ticketing sites

• collabo-cafe.com59
• kinopolis.de59
• ticketmaster.ca59
• ticketmaster.pe60
• vettix.org60

Events & Online Ticketing readiness benchmark