hsbc.com.mx

Readiness by lane

Green: hsbc.com.mx. Thin bar: Banking & Finance peer median.

Priority fixes for hsbc.com.mx

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

1. Priority 1 · Accelerate

   Modern image formats in use

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

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts 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.

   36% of Banking & Finance peers do this.

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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

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

   56% of Banking & Finance peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   49% of Banking & Finance peers do this.

   Guide: Structured Data Basics for Website Owners

What hsbc.com.mx already does well

Practices fewer than half of Banking & Finance peers use.

• Nameservers spread across providersNameservers spread across more than one operator.21% of peers
• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.43% of peers

What we saw

Homepage checked

https://www.hsbc.com.mx/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-03-18

CDN or edge

Amazon CloudFront

Platform or framework

Adobe Experience Manager

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

162 KB, gzip

Images on homepage

12 (jpg 44, 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 Banking & Finance sites

• homecredit.vn75
• hsbc.co.uk75
• hsbc.com.hk75
• inter.co75
• openbank.es75

Banking & Finance readiness benchmark