job-medley.com

Readiness by lane

Green: job-medley.com. Thin bar: Job Portals, HR & Recruitment peer median.

Priority fixes for job-medley.com

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

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

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

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

   Guide: HTTPS and TLS 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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

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

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

What job-medley.com already does well

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

• Modern image formats in useWebP or AVIF images detected.38% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.45% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.48% of peers

What we saw

Homepage checked

https://job-medley.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2027-03-16

Platform or framework

WordPress, Next.js

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

754 KB, gzip

Images on homepage

19 (jpg 78, png 29, webp 2)

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

• francetravail.fr60
• hotnigerianjobs.com60
• ik-danismanlik.com60
• jobbank.gc.ca60
• mid-tenshoku.com60

Job Portals, HR & Recruitment readiness benchmark