Website readiness profile · Snapshot 23 October 2026
usajobs.gov
usajobs.gov's public homepage, certificate and DNS checked against 31 practices and compared with 382 Job Portals, HR & Recruitment sites.
- Readiness index
- 73/100
- Ahead of
- 74%
- Practices observed
- 21/31
- Popularity band
- Top 10K
Job Portals, HR & Recruitment median 65
of measured Job Portals, HR & Recruitment sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: usajobs.gov. Thin bar: Job Portals, HR & Recruitment peer median.
Enable
74/100
Peers 82
Harden
74/100
Peers 56
Accelerate
73/100
Peers 62
Recover
0/100
Peers 11
Priority fixes for usajobs.gov
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
84% of Job Portals, HR & Recruitment peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
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.
87% of Job Portals, HR & Recruitment peers do this.
Priority 3 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
71% of Job Portals, HR & Recruitment peers do this.
Priority 4 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
68% of Job Portals, HR & Recruitment peers do this.
What usajobs.gov already does well
Practices fewer than half of Job Portals, HR & Recruitment peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.11% of peers
- Content Security Policy presentContent-Security-Policy present.30% of peers
- Referrer-Policy setReferrer-Policy present.31% of peers
What we saw
- Homepage checked
- https://www.usajobs.gov/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, http/1.1
- Certificate
- DigiCert, 198-day validity, expiring 2027-03-19
- CDN or edge
- Azure Front Door/CDN
- DNS operators
- Akamai Edge DNS
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 62 KB, gzip
- Images on homepage
- 6 (svg 4, png 1, webp 1)
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 10
Observed 21
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate has more than 14 days left
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own usajobs.gov?
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: usajobs.gov. This profile covers configuration only.