livepocket.jp

Readiness by lane

Green: livepocket.jp. Thin bar: Events & Online Ticketing peer median.

Priority fixes for livepocket.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Events & Online Ticketing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for livepocket.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.

   44% of Events & Online Ticketing peers do this.

   Guide: A Practical Website Health Check for Owners

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

   43% of Events & Online Ticketing peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Enable

   Page language declared

   Observed: The homepage <html> element had no lang attribute.

   What to do: Set lang on the html element (for example lang="en") and on any sections in another language.

   88% of Events & Online Ticketing peers do this.

   Guide: Website Accessibility Checklist for Owners

What livepocket.jp already does well

Practices fewer than half of Events & Online Ticketing peers use.

• Referrer-Policy setReferrer-Policy present.28% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.35% of peers
• Modern image formats in useWebP or AVIF images detected.42% of peers

What we saw

Homepage checked

https://livepocket.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Cybertrust Japan Co., Ltd., 389-day validity, expiring 2027-03-09

CDN or edge

Amazon CloudFront

DNS operators

Akamai Edge DNS

DMARC policy

p=none

Homepage HTML

137 KB, br

Images on homepage

65 (webp 53, svg 6, png 4, jpg 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

Compare with other Events & Online Ticketing sites

• auctionzip.com66
• buschgardens.com67
• kino.kz66
• pathe.fr68
• raceroster.com68

Events & Online Ticketing readiness benchmark