digital-gift.jp

Readiness by lane

Green: digital-gift.jp. Thin bar: Online Payment & Wallets peer median.

Priority fixes for digital-gift.jp

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (112 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

   88% of Online Payment & Wallets peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   60% of Online Payment & Wallets peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   60% of Online Payment & Wallets peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 97 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   47% of Online Payment & Wallets peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What digital-gift.jp already does well

Practices fewer than half of Online Payment & Wallets peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.49% of peers

What we saw

Homepage checked

https://digital-gift.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-01

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

112 KB, uncompressed

Images on homepage

97 (png 50, svg 44, jpg 3)

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 Online Payment & Wallets sites

• billdesk.com47
• happypaytm.com50
• ipayimpact.co.uk47
• ponta.jp51
• westernunion.com51

Online Payment & Wallets readiness benchmark