Website readiness profile · Snapshot 23 October 2026

wkorea.com

wkorea.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index: 44/100
Ahead of: 2%
Practices observed: 12/31
Popularity band: Top 50K

Measured 2026-10-23 11:56:14 UTC from one location. How we measure

Readiness by lane

Green: wkorea.com. Thin bar: News & Media peer median.

Enable

95/100

Peers 89

Harden

29/100

Peers 56

Accelerate

20/100

Peers 68

Recover

0/100

Peers 11

Priority fixes for wkorea.com

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.
94% of News & Media 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.
93% of News & Media peers do this.
Guide: HTTPS and TLS Guide for Website Owners
Priority 3 · 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.
60% of News & Media peers do this.
Guide: Browser Caching Guide for Website Owners
Priority 4 · 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.
35% of News & Media peers do this.
Guide: HTTPS and TLS Guide for Website Owners

What we saw

Homepage checked: https://www.wkorea.com/
Homepage response: HTTP 200
TLS: TLSv1.2
Certificate: Sectigo, 395-day validity, expiring 2027-01-28
Platform or framework: WordPress
DNS operators: 1 self-run or other nameserver domain
Homepage HTML: 140 KB, gzip
Images on homepage: 109 (jpg 43, svg 8, png 5)

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.

WordPress readiness playbook Sectigo (certificate authority)Service guide: WordPress

All 31 checks

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

Not observed 19

Observed 12

HTTP requests move to HTTPS
Certificate has more than 14 days left
HTML compressed
robots.txt published
XML sitemap discoverable
Canonical URL declared
Meta description written
Mobile viewport configured
Structured data present
Social preview image set
Page language declared
At most one redirect to the homepage

Own wkorea.com?

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.

Re-check wkorea.com now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: wkorea.com. This profile covers configuration only.

Compare with other News & Media sites

News & Media readiness benchmark