resume.io

Readiness by lane

Green: resume.io. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for resume.io

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 89 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   38% of Job Portals, HR & Recruitment peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

2. Priority 2 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

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

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for resume.io, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

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

   Guide: HTTPS and TLS Guide for Website Owners

What resume.io already does well

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

• Content Security Policy presentContent-Security-Policy present.30% of peers
• Referrer-Policy setReferrer-Policy present.31% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.36% of peers

What we saw

Homepage checked

https://resume.io/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-04

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

261 KB, br

Images on homepage

89 (jpg 38, png 37, svg 11)

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

• freejobalert.com80
• jobberman.com82
• peopleperhour.com82
• praca.pl82
• work.ua81

Job Portals, HR & Recruitment readiness benchmark