ixdzs.tw

Readiness by lane

Green: ixdzs.tw. Thin bar: Literary & Knowledge peer median.

Priority fixes for ixdzs.tw

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.

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

   69% of Literary & Knowledge peers do this.

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

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 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.

   49% of Literary & Knowledge peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 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.

   48% of Literary & Knowledge peers do this.

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

What ixdzs.tw already does well

Practices fewer than half of Literary & Knowledge peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.5.7% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.28% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://ixdzs.tw/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

SSL2BUY EMEA LLC, 198-day validity, expiring 2026-12-24

DNS operators

GoDaddy DNS

HSTS

max-age 365 days, includeSubDomains, preload

Homepage HTML

58 KB, gzip

Images on homepage

45 (jpg 44)

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

• avidreaders.ru49
• dmxs.org49
• lex.uz49
• manhuagui.com49
• omicaso.org50

Literary & Knowledge readiness benchmark