STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

fischkopf.de

fischkopf.de's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.

Readiness index
34/100

Dating Apps median 58

Ahead of
7.8%

of measured Dating Apps sites

Practices observed
9/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:02:22 UTC from one location. How we measure

Readiness by lane

Green: fischkopf.de. Thin bar: Dating Apps peer median.

Enable

46/100

Peers 71

Harden

38/100

Peers 52

Accelerate

18/100

Peers 53

Recover

0/100

Peers 7

Priority fixes for fischkopf.de

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (105 KB) was delivered without gzip, Brotli or zstd compression.

    Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    89% of Dating Apps peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Enable

    Mobile viewport configured

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

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

    79% of Dating Apps peers do this.

  3. Priority 3 · Enable

    XML sitemap discoverable

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

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

    64% of Dating Apps peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: The DMARC policy for fischkopf.de 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.

    42% of Dating Apps peers do this.

What we saw

Homepage checked
https://www.fischkopf.de/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 377-day validity, expiring 2027-01-24
DNS operators
Hetzner DNS
DMARC policy
p=none
Homepage HTML
105 KB, uncompressed
Images on homepage
14 (jpg 10, png 4)

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

Own fischkopf.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: fischkopf.de. This profile covers configuration only.

Compare with other Dating Apps sites