work.ua

Readiness by lane

Green: work.ua. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for work.ua

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   36% of Job Portals, HR & Recruitment peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 128 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

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for work.ua, 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.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

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

   Guide: A Practical Website Health Check for Owners

What work.ua already does well

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

• Content Security Policy presentContent-Security-Policy present.30% of peers
• HTTP/3 advertisedHTTP/3 advertised.34% of peers
• Modern image formats in useWebP or AVIF images detected.38% of peers

What we saw

Homepage checked

https://www.work.ua/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-14

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

301 KB, br

Images on homepage

128 (png 434, jpg 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

• freejobalert.com80
• meteojob.com80
• peopleperhour.com82
• praca.pl82
• resume.io81

Job Portals, HR & Recruitment readiness benchmark