fiken.no

Readiness by lane

Green: fiken.no. Thin bar: Accounting & Tax peer median.

Priority fixes for fiken.no

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   35% of Accounting & Tax peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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

   28% of Accounting & Tax peers do this.

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

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

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   16% of Accounting & Tax peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Referrer-Policy set

   Observed: The homepage response did not include a Referrer-Policy header.

   What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.

   42% of Accounting & Tax peers do this.

   Guide: A Practical Website Health Check for Owners

What fiken.no already does well

Practices fewer than half of Accounting & Tax peers use.

• security.txt publishedsecurity.txt with a contact found.9.9% of peers
• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
• DNSSEC signedDNSSEC delegation (DS record) present.14% of peers

What we saw

Homepage checked

https://fiken.no/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-03

CDN or edge

Vercel

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

225 KB, br

Images on homepage

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

Compare with other Accounting & Tax sites

• bizimhesap.com80
• cleartax.in82
• invoice-generator.com85
• skatteetaten.no85
• vyaparapp.in79

Accounting & Tax readiness benchmark