nichireifoods.co.jp

Readiness by lane

Green: nichireifoods.co.jp. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for nichireifoods.co.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.

   87% of E-Commerce & Marketplaces peers do this. Limit: Only the standard location was requested, once, at the time of the check.

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

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

   32% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   85% of E-Commerce & Marketplaces peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.nichireifoods.co.jp.

   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.

   39% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

What nichireifoods.co.jp already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• Referrer-Policy setReferrer-Policy present.20% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://www.nichireifoods.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Cybertrust Japan Co., Ltd., 391-day validity, expiring 2026-12-06

Platform or framework

WordPress

DNS operators

3 self-run or other nameserver domains

Homepage HTML

60 KB, gzip

Images on homepage

39 (jpg 30, svg 12, webp 4, png 4)

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 E-Commerce & Marketplaces sites

• mavi.com59
• mi.co.id59
• minne.com59
• plati.market59
• regatta.com59

E-Commerce & Marketplaces readiness benchmark