pagbank.com.br

Readiness by lane

Green: pagbank.com.br. Thin bar: Online Payment & Wallets peer median.

Priority fixes for pagbank.com.br

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   60% of Online Payment & Wallets 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 pagbank.com.br 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

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 52 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 Cloudflare: Cloudflare Polish can convert images to WebP.

   47% of Online Payment & Wallets peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 52 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 Online Payment & Wallets peers do this.

   Guide: Lazy Loading Without Broken Pages

What pagbank.com.br already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.6.4% of peers
• Referrer-Policy setReferrer-Policy present.37% of peers
• Structured data presentJSON-LD structured data found.38% of peers

What we saw

Homepage checked

https://pagbank.com.br/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-01

CDN or edge

Cloudflare, Amazon CloudFront

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 180 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

286 KB, br

Images on homepage

52 (png 31, gif 7, svg 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 Online Payment & Wallets sites

• invoicecloud.com70
• lastlink.com69
• nagad.com.bd66
• paytr.com70
• pointtown.com69

Online Payment & Wallets readiness benchmark