STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

dsv.com

dsv.com's public homepage, certificate and DNS checked against 31 practices and compared with 185 Postage & Courier Services sites.

Readiness index
74/100

Postage & Courier Services median 60

Ahead of
84%

of measured Postage & Courier Services sites

Practices observed
21/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:29:25 UTC from one location. How we measure

Readiness by lane

Green: dsv.com. Thin bar: Postage & Courier Services peer median.

Enable

85/100

Peers 75

Harden

73/100

Peers 56

Accelerate

65/100

Peers 53

Recover

100/100

Peers 12

Priority fixes for dsv.com

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

  1. Priority 1 · Accelerate

    Modern image formats in use

    Observed: The homepage had 37 images and none used WebP or AVIF.

    Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

    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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

    50% of Postage & Courier Services peers do this.

  3. Priority 3 · Accelerate

    Offscreen images lazy-loaded

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

    44% of Postage & Courier Services peers do this.

  4. Priority 4 · Harden

    Content Security Policy present

    Observed: The homepage response did not include a Content-Security-Policy header.

    What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

    31% of Postage & Courier Services peers do this.

What dsv.com already does well

Practices fewer than half of Postage & Courier Services peers use.

  • DNSSEC signedDNSSEC delegation (DS record) present.11% of peers
  • Nameservers spread across providersNameservers spread across more than one operator.12% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to digicert.com.16% of peers

What we saw

Homepage checked
https://www.dsv.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2027-01-09
CDN or edge
Amazon CloudFront
DNS operators
2 self-run or other nameserver domains
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
199 KB, br
Images on homepage
37 (svg 6)

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

Observed 21

  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DNSSEC signed
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Not measured 1

  • HTTP requests move to HTTPS

Own dsv.com?

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: dsv.com. This profile covers configuration only.

Compare with other Postage & Courier Services sites