asaas.com

Readiness by lane

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

Priority fixes for asaas.com

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.

   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 asaas.com 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 70 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 Next.js: The next/image component serves optimized formats automatically.

   47% of Online Payment & Wallets peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   49% of Online Payment & Wallets peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What asaas.com already does well

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

• Static files cached for 30 days or moreLong-lived caching on static files.32% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• Structured data presentJSON-LD structured data found.38% of peers

What we saw

Homepage checked

https://www.asaas.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-04

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

119 KB, gzip

Images on homepage

70 (svg 57)

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

• linkt.com.au64
• mydigipay.com64
• nagad.com.bd66
• pagbank.com.br69
• pointtown.com69

Online Payment & Wallets readiness benchmark