cooky.cz

Readiness by lane

Green: cooky.cz. Thin bar: Literary & Knowledge peer median.

Priority fixes for cooky.cz

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   89% of Literary & Knowledge peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN 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 no max-age, 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   49% of Literary & Knowledge peers do this.

   Guide: Browser Caching Guide for Website Owners

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

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 6 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   48% of Literary & Knowledge peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What cooky.cz already does well

Practices fewer than half of Literary & Knowledge peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.5.7% of peers
• Nameservers spread across providersNameservers spread across more than one operator.5.8% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers

What we saw

Homepage checked

https://cooky.cz/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-05

Platform or framework

WordPress

DNS operators

4 self-run or other nameserver domains

DMARC policy

p=none

Homepage HTML

420 KB, gzip

Images on homepage

47 (jpg 7, png 4, webp 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 Literary & Knowledge sites

• alukah.net60
• behindthename.com60
• flash-manga.net60
• frasicelebri.it60
• zen-manga.com61

Literary & Knowledge readiness benchmark