STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

pex.jp

pex.jp's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.

Readiness index
49/100

Banking & Finance median 66

Ahead of
11%

of measured Banking & Finance sites

Practices observed
13/30

1 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:51:44 UTC from one location. How we measure

Readiness by lane

Green: pex.jp. Thin bar: Banking & Finance peer median.

Enable

51/100

Peers 78

Harden

63/100

Peers 64

Accelerate

24/100

Peers 55

Recover

0/100

Peers 21

Priority fixes for pex.jp

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

  1. 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.

    95% of Banking & Finance peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. 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.

    On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.

    73% of Banking & Finance peers do this.

  3. Priority 3 · Harden

    DMARC policy enforces quarantine or reject

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

    70% of Banking & Finance peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

    Observed: The homepage had 36 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.

    37% of Banking & Finance peers do this.

What pex.jp already does well

Practices fewer than half of Banking & Finance peers use.

  • Referrer-Policy setReferrer-Policy present.36% of peers

What we saw

Homepage checked
https://pex.jp/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
Amazon, 394-day validity, expiring 2027-03-06
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
HSTS
max-age 730 days, includeSubDomains
DMARC policy
p=none
Homepage HTML
45 KB, gzip
Images on homepage
36 (png 35, 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.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 13

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Referrer-Policy set
  • HTML compressed
  • robots.txt published
  • XML sitemap discoverable
  • Meta description written
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own pex.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: pex.jp. This profile covers configuration only.

Compare with other Banking & Finance sites