tekstowo.pl

Readiness by lane

Green: tekstowo.pl. Thin bar: Literary & Knowledge peer median.

Priority fixes for tekstowo.pl

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

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

   Guide: HTTPS and TLS 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 4 hours, 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 Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   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.

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

   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 1 external script 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.

   48% of Literary & Knowledge peers do this.

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

What tekstowo.pl already does well

Practices fewer than half of Literary & Knowledge peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
• Content Security Policy presentContent-Security-Policy present.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.22% of peers

What we saw

Homepage checked

https://www.tekstowo.pl/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-11

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

96 KB, br

Images on homepage

29 (webp 25, png 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

Compare with other Literary & Knowledge sites

• mvlempyr.io71
• pensador.com71
• pidruchnyk.com.ua71
• up-manga.com71
• wikihow.com71

Literary & Knowledge readiness benchmark