salomon.com

Readiness by lane

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

Priority fixes for salomon.com

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   44% of E-Commerce & Marketplaces peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

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

   Guide: Technical SEO Audit: A Practical Owner’s Guide

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

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

   Guide: CDN 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.

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

   Guide: A Practical Website Health Check for Owners

What salomon.com already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• CAA records limit who can issue certificatesCAA limits issuance to globalsign.com, letsencrypt.org, pki.goog and others.16% of peers
• Referrer-Policy setReferrer-Policy present.20% of peers

What we saw

Homepage checked

https://www.salomon.com/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-02

CDN or edge

Vercel

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

241 KB, br

Images on homepage

1 (jpg 13)

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

• oziva.in85
• quince.com85
• rallyhouse.com85
• sezane.com85
• stitchfix.com85

E-Commerce & Marketplaces readiness benchmark