Website readiness profile · Snapshot 23 October 2026
digicafe.jp
digicafe.jp's public homepage, certificate and DNS checked against 31 practices and compared with 218 Dating Apps sites.
- Readiness index
- 37/100
- Ahead of
- 9.6%
- Practices observed
- 10/31
- Popularity band
- Top 50K
Dating Apps median 58
of measured Dating Apps sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: digicafe.jp. Thin bar: Dating Apps peer median.
Enable
69/100
Peers 71
Harden
29/100
Peers 52
Accelerate
20/100
Peers 53
Recover
0/100
Peers 7
Priority fixes for digicafe.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.
83% of Dating Apps peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
79% of Dating Apps peers do this.
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.
82% of Dating Apps peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for digicafe.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.
42% of Dating Apps peers do this.
What we saw
- Homepage checked
- https://digicafe.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- Japan Registry Services Co., Ltd., 165-day validity, expiring 2027-01-31
- Platform or framework
- WordPress
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 41 KB, gzip
- Images on homepage
- 53 (gif 18, png 12)
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 21
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- 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
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Mobile viewport configured
- Structured data present
- Nameservers spread across providers
Observed 10
- 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
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own digicafe.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: digicafe.jp. This profile covers configuration only.