infojobs.net

Readiness by lane

Green: infojobs.net. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for infojobs.net

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for infojobs.net was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   45% of Job Portals, HR & Recruitment peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   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.

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

3. Priority 3 · 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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 31 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

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

   Guide: Lazy Loading Without Broken Pages

What infojobs.net already does well

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

• security.txt publishedsecurity.txt with a contact found.6.2% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.36% of peers

What we saw

Homepage checked

https://www.infojobs.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2026-12-31

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

51 KB, gzip

Images on homepage

31 (jpg 24, png 6, svg 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

Compare with other Job Portals, HR & Recruitment sites

• choisirleservicepublic.gouv.fr70
• estaff365.com70
• ezjobsbangla.com70
• iranestekhdam.ir70
• qyzmet.kz70

Job Portals, HR & Recruitment readiness benchmark