STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

td.com

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

Readiness index
67/100

Banking & Finance median 66

Ahead of
51%

of measured Banking & Finance sites

Practices observed
17/30

1 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:28:06 UTC from one location. How we measure

Readiness by lane

Green: td.com. Thin bar: Banking & Finance peer median.

Enable

79/100

Peers 78

Harden

71/100

Peers 64

Accelerate

53/100

Peers 55

Recover

0/100

Peers 21

Priority fixes for td.com

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 33 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.

  2. Priority 2 · Enable

    At most one redirect to the homepage

    Observed: The homepage was reached after 2 redirects.

    What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

    97% of Banking & Finance peers do this.

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

  4. Priority 4 · Accelerate

    Offscreen images lazy-loaded

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

What td.com already does well

Practices fewer than half of Banking & Finance peers use.

  • Static files cached for 30 days or moreLong-lived caching on static files.43% of peers

What we saw

Homepage checked
https://www.td.com/
Homepage response
HTTP 200, after 2 redirects
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 396-day validity, expiring 2026-11-14
Platform or framework
Adobe Experience Manager
DNS operators
Akamai Edge DNS
HSTS
max-age 730 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
235 KB, gzip
Images on homepage
33 (jpg 16, png 13, svg 4)

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

Observed 17

  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared

Not measured 1

  • HTTP requests move to HTTPS

Own td.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: td.com. This profile covers configuration only.

Compare with other Banking & Finance sites