STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

speisekarte.de

speisekarte.de's public homepage, certificate and DNS checked against 31 practices and compared with 190 Ratings & Reviews sites.

Readiness index
66/100

Ratings & Reviews median 66

Ahead of
47%

of measured Ratings & Reviews sites

Practices observed
18/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:44:52 UTC from one location. How we measure

Readiness by lane

Green: speisekarte.de. Thin bar: Ratings & Reviews peer median.

Enable

85/100

Peers 82

Harden

52/100

Peers 54

Accelerate

75/100

Peers 68

Recover

0/100

Peers 6

Priority fixes for speisekarte.de

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

  1. Priority 1 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 600 seconds, short of the 30-day benchmark.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    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.

    On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

    64% of Ratings & Reviews peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

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

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

    31% of Ratings & Reviews peers do this.

  3. Priority 3 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 10 images and none used loading="lazy".

    What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

    65% of Ratings & Reviews peers do this.

  4. Priority 4 · Harden

    Framing restricted

    Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

    What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

    On Cloudflare: Add the header with a response header transform rule.

    47% of Ratings & Reviews peers do this.

What speisekarte.de already does well

Practices fewer than half of Ratings & Reviews peers use.

  • DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers
  • Modern image formats in useWebP or AVIF images detected.37% of peers
  • HTTP/3 advertisedHTTP/3 advertised.40% of peers

What we saw

Homepage checked
https://www.speisekarte.de/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-21
CDN or edge
Cloudflare
DNS operators
Cloudflare
DMARC policy
p=quarantine
Homepage HTML
55 KB, gzip
Images on homepage
10 (svg 5, png 3, jpg 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

Observed 18

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Modern image formats in use
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Own speisekarte.de?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: speisekarte.de. This profile covers configuration only.

Compare with other Ratings & Reviews sites