Website readiness profile · Snapshot 23 October 2026
parivahan.gov.in
parivahan.gov.in's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.
- Readiness index
- 49/100
- Ahead of
- 37%
- Practices observed
- 15/30
- Popularity band
- Top 5K
Government Services median 53
of measured Government Services sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: parivahan.gov.in. Thin bar: Government Services peer median.
Enable
33/100
Peers 59
Harden
76/100
Peers 59
Accelerate
23/100
Peers 41
Recover
100/100
Peers 25
Priority fixes for parivahan.gov.in
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (289 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
74% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
55% of Government Services peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.parivahan.gov.in.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
52% of Government Services peers do this.
Priority 4 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
61% of Government Services peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
What parivahan.gov.in already does well
Practices fewer than half of Government Services peers use.
- CAA records limit who can issue certificatesCAA limits issuance to emsign.com, letsencrypt.org, sectigo.com.17% of peers
- Nameservers spread across providersNameservers spread across more than one operator.25% of peers
- Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.34% of peers
What we saw
- Homepage checked
- https://parivahan.gov.in/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-22
- Platform or framework
- Drupal
- DNS operators
- 4 self-run or other nameserver domains
- HSTS
- max-age 365 days, includeSubDomains, preload
- Homepage HTML
- 289 KB, uncompressed
- Images on homepage
- 49 (png 37, jpg 12)
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
Not observed 15
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
Observed 15
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 1
- HTTP requests move to HTTPS
Own parivahan.gov.in?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: parivahan.gov.in. This profile covers configuration only.