Website readiness profile · Snapshot 23 October 2026

jisho.org

jisho.org's public homepage, certificate and DNS checked against 31 practices and compared with 696 Literary & Knowledge sites.

Readiness index: 51/100
Ahead of: 19%
Practices observed: 12/29
Popularity band: Top 10K

Measured 2026-10-23 12:25:45 UTC from one location. How we measure

Readiness by lane

Green: jisho.org. Thin bar: Literary & Knowledge peer median.

Enable

49/100

Peers 78

Harden

57/100

Peers 51

Accelerate

43/100

Peers 62

Recover

0/100

Peers 6

Priority fixes for jisho.org

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

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
Priority 2 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
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.
Guide: HTTPS and TLS Guide for Website Owners
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.
69% of Literary & Knowledge peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · 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.
49% of Literary & Knowledge peers do this.
Guide: Browser Caching Guide for Website Owners

What jisho.org already does well

Practices fewer than half of Literary & Knowledge peers use.

CAA records limit who can issue certificatesCAA limits issuance to comodoca.com.13% of peers
HSTS kept for at least a yearHSTS with a 365-day max-age.28% of peers
Framing restrictedFraming controls present.37% of peers

What we saw

Homepage checked: https://jisho.org/
Homepage response: HTTP 200
TLS: TLSv1.2
Certificate: Sectigo, 198-day validity, expiring 2026-12-27
DNS operators: 1 self-run or other nameserver domain
HSTS: max-age 365 days
Homepage HTML: 31 KB, gzip
Images on homepage: 0

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.

Sectigo (certificate authority)

All 31 checks

Select a gap for the method and fix. How each check works

Not observed 17

Observed 12

HTTP requests move to HTTPS
HSTS kept for at least a year
Certificate has more than 14 days left
CAA records limit who can issue certificates
X-Content-Type-Options: nosniff
Framing restricted
HTML compressed
No render-blocking scripts in <head>
robots.txt published
Meta description written
Mobile viewport configured
At most one redirect to the homepage

Not measured 2

Modern image formats in use
Offscreen images lazy-loaded

Own jisho.org?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Re-check jisho.org now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: jisho.org. This profile covers configuration only.

Compare with other Literary & Knowledge sites

Literary & Knowledge readiness benchmark