ss.lv

Readiness by lane

Green: ss.lv. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for ss.lv

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   93% of E-Commerce & Marketplaces peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 7 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.

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

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

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

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

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

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What ss.lv 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 ssl.com.16% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.32% of peers

What we saw

Homepage checked

https://www.ss.lv/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

SSL Corporation, 197-day validity, expiring 2027-04-04

DNS operators

4 self-run or other nameserver domains

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

24 KB, gzip

Images on homepage

18 (png 12, gif 1, svg 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

Compare with other E-Commerce & Marketplaces sites

• motivi.com57
• rakuten.co.jp57
• rendez-vous.ru57
• topsecret.pl57
• torecolo.jp57

E-Commerce & Marketplaces readiness benchmark