martinus.sk

Readiness by lane

Green: martinus.sk. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for martinus.sk

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 300 seconds, 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 179 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 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

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

   Guide: HTTPS and TLS Guide for Website Owners

What martinus.sk already does well

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

• security.txt publishedsecurity.txt with a contact found.7.6% of peers
• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• Referrer-Policy setReferrer-Policy present.20% of peers

What we saw

Homepage checked

https://www.martinus.sk/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Sectigo, 176-day validity, expiring 2027-04-06

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

312 KB, br

Images on homepage

179 (jpg 152, png 7, svg 5, gif 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

• loesdau.de71
• magicpin.in71
• marelepescar.ro71
• megabad.com71
• megapteka.ru71

E-Commerce & Marketplaces readiness benchmark