hrmos.co

Readiness by lane

Green: hrmos.co. Thin bar: Workplace Productivity peer median.

Priority fixes for hrmos.co

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 hrmos.co 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.

   63% of Workplace Productivity 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 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   80% of Workplace Productivity peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

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

   72% of Workplace Productivity peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   52% of Workplace Productivity peers do this.

   Guide: A Practical Website Health Check for Owners

What hrmos.co already does well

Practices fewer than half of Workplace Productivity peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers
• Modern image formats in useWebP or AVIF images detected.49% of peers

What we saw

Homepage checked

https://hrmos.co/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

106 KB, gzip

Images on homepage

172 (webp 171, svg 7, png 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 Workplace Productivity sites

• aladdin.ie66
• fwcms.com.my66
• otter.ai66
• skyroom.online66
• sportsyou.com67

Workplace Productivity readiness benchmark