interactivebrokers.co.uk

Readiness by lane

Green: interactivebrokers.co.uk. Thin bar: Stock & Crypto Trading peer median.

Priority fixes for interactivebrokers.co.uk

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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.

   44% of Stock & Crypto Trading 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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 0 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.

   55% of Stock & Crypto Trading peers do this.

   Guide: Browser Caching Guide for Website Owners

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

   51% of Stock & Crypto Trading peers do this.

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

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   36% of Stock & Crypto Trading peers do this.

   Guide: CDN Guide for Website Owners

What interactivebrokers.co.uk already does well

Practices fewer than half of Stock & Crypto Trading peers use.

• Referrer-Policy setReferrer-Policy present.38% of peers
• Content Security Policy presentContent-Security-Policy present.40% of peers
• Modern image formats in useWebP or AVIF images detected.48% of peers

What we saw

Homepage checked

https://www.interactivebrokers.co.uk/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-13

CDN or edge

Akamai

DNS operators

Akamai Edge DNS

HSTS

max-age 0 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

162 KB, gzip

Images on homepage

21 (webp 15, svg 14, jpg 12, png 10)

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 Stock & Crypto Trading sites

• groww.in72
• interactivebrokers.com71
• interactivebrokers.ie71
• ramzinex.com72
• screener.in72

Stock & Crypto Trading readiness benchmark