Website readiness profile · Snapshot 23 October 2026
kaldi.co.jp
kaldi.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 413 Food & Grocery Delivery sites.
- Readiness index
- 58/100
- Ahead of
- 18%
- Practices observed
- 15/31
- Popularity band
- Top 50K
Food & Grocery Delivery median 68
of measured Food & Grocery Delivery sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: kaldi.co.jp. Thin bar: Food & Grocery Delivery peer median.
Enable
87/100
Peers 85
Harden
48/100
Peers 59
Accelerate
48/100
Peers 64
Recover
0/100
Peers 12
Priority fixes for kaldi.co.jp
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.
On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.
93% of Food & Grocery Delivery peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · 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.
59% of Food & Grocery Delivery peers do this.
Priority 3 · 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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
42% of Food & Grocery Delivery peers do this.
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 36 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
63% of Food & Grocery Delivery peers do this.
What kaldi.co.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.kaldi.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3
- Certificate
- GlobalSign, 199-day validity, expiring 2027-02-06
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- DMARC policy
- p=quarantine
- Homepage HTML
- 70 KB, gzip
- Images on homepage
- 36 (jpg 26, svg 7, webp 2, png 2)
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
Not observed 16
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- Reachable over IPv6
- Structured data present
- Nameservers spread across providers
Observed 15
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- HTML compressed
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own kaldi.co.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: kaldi.co.jp. This profile covers configuration only.