Website readiness profile · Snapshot 23 October 2026
bancoguayaquil.com
bancoguayaquil.com's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 67/100
- Ahead of
- 51%
- Practices observed
- 18/30
- Popularity band
- Top 50K
Banking & Finance median 66
of measured Banking & Finance sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: bancoguayaquil.com. Thin bar: Banking & Finance peer median.
Enable
87/100
Peers 78
Harden
51/100
Peers 64
Accelerate
72/100
Peers 55
Recover
100/100
Peers 21
Priority fixes for bancoguayaquil.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate has more than 14 days left
Observed: The certificate from DigiCert Inc was due to expire on 2026-11-01 (9 days after the check).
Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.
What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.
97% of Banking & Finance peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1200 seconds, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
43% of Banking & Finance peers do this.
Priority 3 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
69% of Banking & Finance peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
51% of Banking & Finance peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What bancoguayaquil.com already does well
Practices fewer than half of Banking & Finance peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, letsencrypt.org, pki.goog and others.20% of peers
- Nameservers spread across providersNameservers spread across more than one operator.21% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.36% of peers
What we saw
- Homepage checked
- https://www.bancoguayaquil.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2026-11-01
- CDN or edge
- Azure Front Door/CDN
- Platform or framework
- Astro
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 48 KB, gzip
- Images on homepage
- 5 (webp 4, svg 2, png 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
Not observed 12
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Reachable over IPv6
- Structured data present
Observed 18
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 1
- Offscreen images lazy-loaded
Own bancoguayaquil.com?
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: bancoguayaquil.com. This profile covers configuration only.