ssc.gov.in

Readiness by lane

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

Priority fixes for ssc.gov.in

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

1. Priority 1 · Accelerate

   HTML compressed

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

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.

   Guide: CDN Guide for Website Owners

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.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

What ssc.gov.in already does well

Practices fewer than half of Government Services peers use.

• CAA records limit who can issue certificatesCAA limits issuance to globalsign.com.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://ssc.gov.in/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 199-day validity, expiring 2027-04-22

DNS operators

4 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

79 KB, uncompressed

Images on homepage

0

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 Government Services sites

• city.sapporo.jp43
• detran.pe.gov.br43
• jkadmissions.in44
• mypension.be44
• ociservices.gov.in44

Government Services readiness benchmark