customs.gov.om

Readiness by lane

Green: customs.gov.om. Thin bar: Government Services peer median.

Priority fixes for customs.gov.om

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (148 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 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 186 days, below the one-year benchmark.

   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.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. 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 customs.gov.om already does well

Practices fewer than half of Government Services peers use.

• Offscreen images lazy-loadedNative lazy loading in use.36% of peers

What we saw

Homepage checked

https://www.customs.gov.om/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Entrust Limited, 198-day validity, expiring 2027-03-20

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 186 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

148 KB, uncompressed

Images on homepage

38 (png 19, jpg 18, svg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Government Services sites

• operacoes.sp.gov.br26
• pddrc.in26
• sunat.gob.pe27
• vuce.gob.pe27
• washingtonconnection.org28

Government Services readiness benchmark