ams.at

Readiness by lane

Green: ams.at. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for ams.at

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

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

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   36% of Job Portals, HR & Recruitment peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

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

   48% of Job Portals, HR & Recruitment peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

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

   47% of Job Portals, HR & Recruitment peers do this.

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

What ams.at already does well

Practices fewer than half of Job Portals, HR & Recruitment peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• DNSSEC signedDNSSEC delegation (DS record) present.11% of peers
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, harica.gr, sectigo.com.14% of peers

What we saw

Homepage checked

https://www.ams.at/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 372-day validity, expiring 2027-02-18

Platform or framework

Adobe Experience Manager

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

92 KB, gzip

Images on homepage

28 (svg 20, webp 17, jpg 8)

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 Job Portals, HR & Recruitment sites

• adecco.com71
• arbetsformedlingen.se71
• assamcareer.com71
• isinolsun.com72
• pharmabharat.com72

Job Portals, HR & Recruitment readiness benchmark