Skip to content
NO · NOK (kr) · Estimated Applicable regulations: GDPR · ePrivacy Directive · EAA Dev cost: NOK 900/hr How jurisdiction is detected
Scanned
2026-05-10 13:33 UTC
Worker
🇪🇸 Madrid
Duration
33.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 869ms across 6 locations, fastest from Amsterdam (135ms), slowest from Singapore (2420ms). Vercel edge cache (HIT). 3 locations above the 500ms target.

Spain - Madrid
Full audit
190ms
DNS 82ms · TLS 58ms
Netherlands - Amsterdam
135ms
DNS 58ms · TLS 22ms
United Stated - New York
263ms
DNS 193ms · TLS 23ms
United States - Santa Clara
793ms
DNS 715ms · TLS 14ms
Brazil - Sao Paulo
1414ms
DNS 456ms · TLS 12ms
Singapore - Singapore
2420ms
DNS 360ms · TLS 25ms
CDN: Vercel (HIT) · Avg TTFB: 869ms · Cache: public, max-age=0, must-revalidate

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers
Critical: 2

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy
Critical: 3

Page body has only 168 chars of text -- likely empty / placeholder

Security gaps expose your site and users to attacks, eroding trust.

Security › Empty Page Detection
Warning: 4

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
Warning: 5

Cross-Origin-Opener-Policy header is missing

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Security › Security Headers
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
5 security gaps detected — browsers may warn visitors about your site.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

NOK 6,975 investment → NOK 107,709/month returns + EUR 20,500,000 risk avoided

Investment
NOK 6,975
7.8 h · 5 findings
Monthly returns
NOK 107,709
NOK 1,292,509/yr
Payback
0.1 mo
+18431% Y1
Regulatory risk avoided EUR 20,500,000
Or — fix only the top 3 findings
NOK 5,8500.1 mo payback · +21994% Y1
Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.
NOK 675 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Conversion barriers

9 barrier(s) likely increasing bounce by ~29%.

Barriers
9
1 crit 8 warn
Bounce delta
+29pp
added vs baseline
Score
66
C
Speed
2
Trust
2
Usability
0
Content
4
Nav
1
  • Page takes 5.3s to load
    Users abandon at ~3s — you're 2.8s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • High main-thread blocking time
    Page is non-interactive for 466ms after first paint
    → Defer third-party scripts and split large bundles
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • No Content-Security-Policy header
    Higher XSS blast radius — one compromised script can exfiltrate the checkout form
    → Ship a reporting-only CSP first, then enforce once violations are clean
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

kr6,975 7.8 developer hours at kr900/hr
Quick wins
kr675 2 fixes in ~45 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Team composition

Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.

kr /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Cost of inaction

NOK 1,780,792 / month at risk ~NOK 21,369,501 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€20,500,000

GDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Privacy Policy not detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • No <nav> landmark found
    EAA: EUR 1,000 – EUR 500,000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000
  • No headings found
    EAA: EUR 1,000 – EUR 500,000

Bounce-Rate Cost

NOK 72,456 /mo

+29.0pp bounce · ~2,898 lost visitors/mo

CPC: NOK 25.00

Bandwidth Waste

NOK 2.24 /mo

2605.1 MB/mo × 0.860 NOK/GB

  • Optimize transfer: save ~261 KB per page load
    Saves NOK 2.24/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Categories

8
Avg score 82.0

How you compare

Where this site stands against peers running the same stack.

HSTS · 2429 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P3Accessibility P96Sustainability P93Performance P89Security P86Infrastructure P23SEO P29Content P36

Top 10% of HSTS sites score 86+ on Compliance; you're at 63 — closing this gap is the highest-leverage improvement.

Better than 91% of HSTS sites See full HSTS benchmark →
Vercel Edge · 82 peers
You 82
·
Avg 76
+6 above average
0 50 100
Better than 79% of Vercel Edge sites See full Vercel Edge benchmark →

Technology stack

HSTS, hosted on Vercel, with Vercel Edge CDN

3 technologies detected 3 stack layers Standard

Stack Architecture

Framework
HSTS
CDN
Vercel Edge
Hosting
Vercel

All Detected Technologies (3)

Categories CDN Website https://vercel.com Detected by BeaverCheck Evidence x-vercel-id: cdg1::lzhtv-1778420003424-b0ec7be91d71

Vercel is a cloud platform for static frontends and serverless functions.

Categories PaaS Website https://vercel.com Detected by BeaverCheck Evidence Header: x-vercel-id, Server: Vercel

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (HSTS) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.

Show your score

Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.lyon-industries.no)](https://beavercheck.com/results/0df7269d-68f4-471e-8f0f-1bb86c1e1194)
<a href="https://beavercheck.com/results/0df7269d-68f4-471e-8f0f-1bb86c1e1194"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.lyon-industries.no" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.lyon-industries.no

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

Fix Plan

Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.

Three-week fix plan

2 sprints · 8h total → projected B (88)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 1h → B (86)
  • · Page body has only 168 chars of text -- likely empty / placeholder
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

3 findings 7h → B (88)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback