ojk.go.id

Readiness by lane

Green: ojk.go.id. Thin bar: Government Services peer median.

Priority fixes for ojk.go.id

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   77% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 17 external scripts 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.

   39% of Government Services peers do this.

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

What ojk.go.id already does well

Practices fewer than half of Government Services peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Referrer-Policy setReferrer-Policy present.39% of peers
• Content Security Policy presentContent-Security-Policy present.41% of peers

What we saw

Homepage checked

https://ojk.go.id/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2

Certificate

DigiCert, 180-day validity, expiring 2027-03-21

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

640 KB, gzip

Images on homepage

10 (png 5)

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.nagoya.jp55
• funcionpublica.gov.co55
• nenkin.go.jp55
• sme.gov.ao55
• un.org55

Government Services readiness benchmark