kaufda.de

Readiness by lane

Green: kaufda.de. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for kaufda.de

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   87% of E-Commerce & Marketplaces peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 71 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 Next.js: The next/image component serves optimized formats automatically.

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

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

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

   On Next.js: Next.js documents nonce-based CSP with middleware.

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

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

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

What kaufda.de already does well

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

• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.32% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://www.kaufda.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2027-02-04

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

339 KB, gzip

Images on homepage

71 (png 37, jpg 29, svg 5)

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

• jabko.ua73
• jwpei.com73
• jysk.ch73
• kmart.com.au73
• kotte-zeller.de73

E-Commerce & Marketplaces readiness benchmark