kaup24.ee

Readiness by lane

Green: kaup24.ee. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for kaup24.ee

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   98% 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: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Accelerate

   Modern image formats in use

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

   On Cloudflare: Cloudflare Polish can convert images to WebP.

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

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

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

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

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for kaup24.ee 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.

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

   Guide: A Practical Website Health Check for Owners

What kaup24.ee already does well

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

• Reachable over IPv6IPv6 address published.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
• HTTP/3 advertisedHTTP/3 advertised.47% of peers

What we saw

Homepage checked

https://kaup24.ee/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-03-25

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 183 days

DMARC policy

p=none

Homepage HTML

298 KB, br

Images on homepage

29 (jpg 18, svg 13, png 2)

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

• express.com61
• fiorellarubino.com61
• homecenter.com.co61
• kids-world.dk61
• legami.com61

E-Commerce & Marketplaces readiness benchmark