Website readiness profile · Snapshot 23 October 2026

hotpepper.jp

hotpepper.jp's public homepage, certificate and DNS checked against 31 practices and compared with 413 Food & Grocery Delivery sites.

Readiness index: 45/100
Ahead of: 5.1%
Practices observed: 12/31
Popularity band: Top 5K

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

Readiness by lane

Green: hotpepper.jp. Thin bar: Food & Grocery Delivery peer median.

Enable

49/100

Peers 85

Harden

43/100

Peers 59

Accelerate

48/100

Peers 64

Recover

0/100

Peers 12

Priority fixes for hotpepper.jp

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

Priority 1 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
>99% of Food & Grocery Delivery peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: Responsive Web Design Checklist for Real Devices
Priority 2 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
93% of Food & Grocery Delivery peers do this.
Guide: CDN Guide for Website Owners
Priority 3 · 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.
95% of Food & Grocery Delivery peers do this.
Guide: HTTPS and TLS Guide for Website Owners
Priority 4 · 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.
87% of Food & Grocery Delivery peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

What hotpepper.jp already does well

Practices fewer than half of Food & Grocery Delivery peers use.

Modern image formats in useWebP or AVIF images detected.40% of peers
DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.42% of peers
No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked: https://www.hotpepper.jp/
Homepage response: HTTP 200
TLS: TLSv1.2
Certificate: DigiCert, 198-day validity, expiring 2027-05-06
DNS operators: 1 self-run or other nameserver domain
HSTS: max-age 0 days, includeSubDomains
DMARC policy: p=quarantine
Homepage HTML: 90 KB, gzip
Images on homepage: 24 (png 18, webp 4, gif 1, jpg 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.

DigiCert (certificate authority)

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
DMARC policy enforces quarantine or reject
X-Content-Type-Options: nosniff
HTML compressed
Modern image formats in use
No render-blocking scripts in <head>
robots.txt published
Canonical URL declared
Meta description written
Page language declared
At most one redirect to the homepage

Own hotpepper.jp?

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

Re-check hotpepper.jp now Add to owner workspace Request a correction or removal

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

Compare with other Food & Grocery Delivery sites

Food & Grocery Delivery readiness benchmark