fvn.no

Readiness by lane

Green: fvn.no. Thin bar: News & Media peer median.

Priority fixes for fvn.no

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.

   35% of News & Media 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 4 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 Nuxt: Nuxt Image can output WebP and AVIF.

   44% of News & Media peers do this.

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

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   76% of News & Media peers do this.

   Guide: Structured Data Basics for Website Owners

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

   42% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

What fvn.no already does well

Practices fewer than half of News & Media peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers

What we saw

Homepage checked

https://www.fvn.no/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

Platform or framework

Nuxt

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

73 KB, br

Images on homepage

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

Compare with other News & Media sites

• fortune.com68
• fox8.com68
• ftnews.jp68
• gazeta45.com68
• glavcom.ua68

News & Media readiness benchmark