STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

macro.com.ar

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

Readiness index
39/100

Banking & Finance median 66

Ahead of
3.3%

of measured Banking & Finance sites

Practices observed
11/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:25:58 UTC from one location. How we measure

Readiness by lane

Green: macro.com.ar. Thin bar: Banking & Finance peer median.

Enable

59/100

Peers 78

Harden

52/100

Peers 64

Accelerate

0/100

Peers 55

Recover

0/100

Peers 21

Priority fixes for macro.com.ar

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (873 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.

    89% of Banking & Finance peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  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.

    73% of Banking & Finance peers do this.

  3. Priority 3 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    86% of Banking & Finance peers do this.

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

    62% of Banking & Finance peers do this.

What macro.com.ar 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://www.macro.com.ar/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.2
Certificate
DigiCert, 198-day validity, expiring 2027-04-25
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=reject
Homepage HTML
873 KB, uncompressed
Images on homepage
136 (svg 59, png 55, jpg 18)

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

Own macro.com.ar?

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: macro.com.ar. This profile covers configuration only.

Compare with other Banking & Finance sites