Website readiness profile · Snapshot 23 October 2026
iex.nl
iex.nl's public homepage, certificate and DNS checked against 31 practices and compared with 241 Stock & Crypto Trading sites.
- Readiness index
- 63/100
- Ahead of
- 32%
- Practices observed
- 18/31
- Popularity band
- Top 50K
Stock & Crypto Trading median 69
of measured Stock & Crypto Trading sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: iex.nl. Thin bar: Stock & Crypto Trading peer median.
Enable
74/100
Peers 82
Harden
71/100
Peers 61
Accelerate
43/100
Peers 67
Recover
0/100
Peers 6
Priority fixes for iex.nl
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
94% of Stock & Crypto Trading peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · 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.
44% of Stock & Crypto Trading peers do this.
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
78% of Stock & Crypto Trading peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 14 days, 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.
What iex.nl already does well
Practices fewer than half of Stock & Crypto Trading peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.10% of peers
- CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org, sectigo.com.15% of peers
- Content Security Policy presentContent-Security-Policy present.40% of peers
What we saw
- Homepage checked
- https://www.iex.nl/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3
- Certificate
- Sectigo, 198-day validity, expiring 2027-01-06
- DNS operators
- 1 self-run or other nameserver domain
- DMARC policy
- p=quarantine
- Homepage HTML
- 269 KB, gzip
- Images on homepage
- 101 (jpg 132, svg 40, gif 17, png 17)
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 13
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- security.txt published
- X-Content-Type-Options: nosniff
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Nameservers spread across providers
Observed 18
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- HTML compressed
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own iex.nl?
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: iex.nl. This profile covers configuration only.