myraymond.com

Readiness by lane

Green: myraymond.com. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for myraymond.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 91 days, below the one-year benchmark.

   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.

   32% of E-Commerce & Marketplaces 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 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   60% of E-Commerce & Marketplaces peers do this.

   Guide: SEO Checklist for a New Website

3. Priority 3 · Harden

   CAA records limit who can issue certificates

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

   16% of E-Commerce & Marketplaces 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.

   7.6% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

What myraymond.com already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked

https://myraymond.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-14

CDN or edge

Cloudflare, Shopify

Platform or framework

Shopify

DNS operators

GoDaddy DNS

HSTS

max-age 91 days

DMARC policy

p=reject

Homepage HTML

3,217 KB, br

Images on homepage

142 (jpg 808, webp 89, png 70)

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 E-Commerce & Marketplaces sites

• mourjan.com82
• mueller.de82
• myborosil.com82
• mysleepwell.com82
• newbalance.com.br82

E-Commerce & Marketplaces readiness benchmark