azki.com

Readiness by lane

Green: azki.com. Thin bar: Insurance & Financial Planning peer median.

Priority fixes for azki.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   60% of Insurance & Financial Planning 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

   Modern image formats in use

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

   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.

   On Next.js: The next/image component serves optimized formats automatically.

   43% of Insurance & Financial Planning peers do this.

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

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

   On Next.js: Add it in next.config.js headers().

   69% of Insurance & Financial Planning peers do this.

   Guide: A Practical Website Health Check for Owners

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

   On Next.js: Next.js documents nonce-based CSP with middleware.

   51% of Insurance & Financial Planning peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What azki.com already does well

Practices fewer than half of Insurance & Financial Planning peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked

https://www.azki.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Asseco Data Systems S.A., 198-day validity, expiring 2027-02-13

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

262 KB, br

Images on homepage

71 (svg 54)

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 Insurance & Financial Planning sites

• lincolnfinancial.com67
• misentinel.com.pe68
• nestpensions.org.uk68
• sura.co67
• utua.id68

Insurance & Financial Planning readiness benchmark