codmon.com

Readiness by lane

Green: codmon.com. Thin bar: Workplace Productivity peer median.

Priority fixes for codmon.com

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.

   93% of Workplace Productivity peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   59% of Workplace Productivity peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   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.

   Guide: A Practical Website Health Check for Owners

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

   27% of Workplace Productivity peers do this.

   Guide: CDN Guide for Website Owners

What codmon.com 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
• Content Security Policy presentContent-Security-Policy present.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers

What we saw

Homepage checked

https://www.codmon.com/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Amazon, 197-day validity, expiring 2027-02-22

CDN or edge

Amazon CloudFront

Platform or framework

WordPress, Nuxt

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

599 KB, gzip

Images on homepage

66 (png 23, webp 19, svg 8)

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

• nimenhuuto.com69
• perceptyx.com70
• remind.com69
• sportsyou.com67
• whatsappbusiness.com68

Workplace Productivity readiness benchmark