Website readiness profile · Snapshot 23 October 2026
myhermes.de
myhermes.de's public homepage, certificate and DNS checked against 31 practices and compared with 185 Postage & Courier Services sites.
- Readiness index
- 62/100
- Ahead of
- 52%
- Practices observed
- 17/31
- Popularity band
- Top 50K
Postage & Courier Services median 60
of measured Postage & Courier Services sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: myhermes.de. Thin bar: Postage & Courier Services peer median.
Enable
67/100
Peers 75
Harden
69/100
Peers 56
Accelerate
48/100
Peers 53
Recover
0/100
Peers 12
Priority fixes for myhermes.de
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
81% of Postage & Courier Services peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for myhermes.de 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.
52% of Postage & Courier Services peers do this.
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 days, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
44% of Postage & Courier Services peers do this.
Priority 4 · Accelerate
Modern image formats in use
Observed: The homepage had 10 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
31% of Postage & Courier Services peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
What myhermes.de already does well
Practices fewer than half of Postage & Courier Services peers use.
- HTTP/3 advertisedHTTP/3 advertised.22% of peers
- Referrer-Policy setReferrer-Policy present.28% of peers
- Content Security Policy presentContent-Security-Policy present.31% of peers
What we saw
- Homepage checked
- https://www.myhermes.de/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 392-day validity, expiring 2027-03-03
- CDN or edge
- Google edge
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 730 days
- DMARC policy
- p=none
- Homepage HTML
- 119 KB, br
- Images on homepage
- 10 (jpg 43, 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
Not observed 14
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 17
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own myhermes.de?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: myhermes.de. This profile covers configuration only.