STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

omocoro.jp

omocoro.jp's public homepage, certificate and DNS checked against 31 practices and compared with 306 Online Publishing sites.

Readiness index
77/100

Online Publishing median 64

Ahead of
90%

of measured Online Publishing sites

Practices observed
22/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

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

Readiness by lane

Green: omocoro.jp. Thin bar: Online Publishing peer median.

Enable

79/100

Peers 84

Harden

71/100

Peers 51

Accelerate

88/100

Peers 65

Recover

0/100

Peers 5

Priority fixes for omocoro.jp

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

  1. Priority 1 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

    79% of Online Publishing peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · Accelerate

    No render-blocking scripts in <head>

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

    45% of Online Publishing peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

    Observed: The DMARC policy for omocoro.jp was p=none, which asks receivers to take no action on failing mail.

    What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

    20% of Online Publishing peers do this.

  4. Priority 4 · Enable

    Structured data present

    Observed: The homepage had no JSON-LD structured data.

    What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

    64% of Online Publishing peers do this.

What omocoro.jp already does well

Practices fewer than half of Online Publishing peers use.

  • Content Security Policy presentContent-Security-Policy present.18% of peers
  • HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.27% of peers
  • Framing restrictedFraming controls present.37% of peers

What we saw

Homepage checked
https://omocoro.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-07
CDN or edge
Cloudflare
Platform or framework
WordPress
DNS operators
Cloudflare
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=none
Homepage HTML
118 KB, br
Images on homepage
195 (jpg 147, png 43, gif 2, webp 1, svg 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

Observed 22

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own omocoro.jp?

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.

Live status for this site: Status Is Down: omocoro.jp. This profile covers configuration only.

Compare with other Online Publishing sites