STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

ejalshakti.gov.in

ejalshakti.gov.in's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
44/100

Government Services median 53

Ahead of
26%

of measured Government Services sites

Practices observed
11/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:00:41 UTC from one location. How we measure

Readiness by lane

Green: ejalshakti.gov.in. Thin bar: Government Services peer median.

Enable

26/100

Peers 59

Harden

71/100

Peers 59

Accelerate

15/100

Peers 41

Recover

100/100

Peers 25

Priority fixes for ejalshakti.gov.in

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (189 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.

  2. 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.

  3. Priority 3 · 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.

  4. Priority 4 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    42% of Government Services peers do this.

What ejalshakti.gov.in already does well

Practices fewer than half of Government Services peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org, sectigo.com.17% of peers
  • Nameservers spread across providersNameservers spread across more than one operator.25% of peers
  • Static files cached for 30 days or moreLong-lived caching on static files.30% of peers

What we saw

Homepage checked
https://ejalshakti.gov.in/
Homepage response
HTTP 200, after 4 redirects
TLS
TLSv1.3
Certificate
Sectigo, 395-day validity, expiring 2026-11-16
DNS operators
4 self-run or other nameserver domains
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
189 KB, uncompressed
Images on homepage
57 (png 49, svg 5, gif 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

Observed 11

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • Static files cached for 30 days or more
  • Mobile viewport configured
  • Page language declared
  • Nameservers spread across providers

Own ejalshakti.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: ejalshakti.gov.in. This profile covers configuration only.

Compare with other Government Services sites