Skip to content
Scanned
2026-06-09 13:52 UTC
Worker
🇳🇱 Amsterdam
Duration
1.4m
Vs prev

Global Performance

6/6 locations

Excellent global latency — average 37ms across 6 locations, fastest from New York (19ms), slowest from Santa Clara (80ms). Akamai in front. Cache-Control header is missing.

Netherlands - Amsterdam
Full audit
21ms
DNS 4ms · TLS 5ms
United Stated - New York
19ms
DNS 5ms · TLS 4ms
Spain - Madrid
57ms
DNS 45ms · TLS 3ms
United States - Santa Clara
80ms
DNS 8ms · TLS 14ms
Brazil - Sao Paulo
23ms
DNS 8ms · TLS 4ms
Singapore - Singapore
21ms
DNS 6ms · TLS 4ms
CDN: Akamai · Avg TTFB: 37ms · Cache: No cache headers

Audit overview

Compliance and Sustainability need attention; the other categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

5

High impact, low effort — start here.

Strategic

0

High impact, requires investment.

Nothing in this quadrant — good news.

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
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

Cookie 'nok_ip_locale' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 2

Cookie 'nok_ip_region' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 3

Page weighs 23.8 MB (15.6 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
Critical: 4

Scan returned a Akamai Bot Manager bot-protection interstitial, not the actual page

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

Security › Bot Challenge Detection
Critical: 5

Missing <html lang> attribute (WCAG 3.1.1)

Missing <html lang> attribute -- screen readers default to the user's system language and pronounce content with the wrong phonetics.

Accessibility › Document Language
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 9.1s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 9.1s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.

Business case

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

Return on investment

€87 investment → €13,712/month returns + EUR 120,500,000 risk avoided

Investment
€87
1.1 h · 4 findings
Monthly returns
€13.712
€164.542/yr
Payback
0.0 mo
+189756% Y1
Regulatory risk avoided EUR 120.500.000
Or — fix only the top 3 findings
€800.0 mo payback · +205577% 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.

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 ~38%.

Barriers
9
3 crit 6 warn
Bounce delta
+38pp
added vs baseline
Score
52
D
Speed
2
Trust
1
Usability
1
Content
4
Nav
1
  • Page takes 9.1s to load
    Users abandon at ~3s — you're 6.6s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 3.4s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • 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

€87 1.1 developer hours at €80/hr
Quick wins
€87 4 fixes in ~65 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.

/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

€8.380 / month at risk ~€100.560 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€120.500.000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10.000 – EUR 20.000.000
  • 2 non-essential cookie(s) set without consent banner
    GDPR: EUR 5.000 – EUR 10.000.000
  • 2 non-essential cookie(s) set without consent banner
    GDPR: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€8.376 /mo

+38.1pp bounce · ~3,807 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€3,64 /mo

49183.8 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~4.9 MB per page load
    Saves €3,64/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 5 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

Mobile

29
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

5.79 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.11 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.39 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.013

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

7.48 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

13.69 s

Desktop

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

912 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.78 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

624 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.025

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.76 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.88 s

Categories

8
Avg score 74.1

How you compare

Where this site stands against peers running the same stack.

HSTS · 2556 peers
You 78
·
Avg 75
At average
0 50 100
Compliance P1Sustainability P11Security P87Accessibility P82SEO P22Performance P70Infrastructure P31Content P35

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

Better than 71% of HSTS sites See full HSTS benchmark →
HTTP/3 · 1498 peers
You 78
·
Avg 75
At average
0 50 100
Compliance P1Sustainability P4Security P89Accessibility P83Infrastructure P23SEO P29Performance P62Content P40

Top 10% of HTTP/3 sites score 85+ on Compliance; you're at 53 — closing this gap is the highest-leverage improvement.

Better than 70% of HTTP/3 sites See full HTTP/3 benchmark →

Technology stack

HSTS

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
HSTS HTTP/3

All Detected Technologies (2)

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

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck

Observations (2)

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.

Minimal technology footprint

Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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.nokia.com)](https://beavercheck.com/results/1f0f3e74-5c91-4843-a23f-d63a3b98fcec)
<a href="https://beavercheck.com/results/1f0f3e74-5c91-4843-a23f-d63a3b98fcec"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.nokia.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.nokia.com

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

1 sprints · 1h total → projected B (87)

Sprint 1: Quick Wins

+9

Highest ROI — low effort, high impact

5 findings 1h → B (87)
  • · Page weighs 23.8 MB (15.6 MB transferred)
  • · Missing <html lang> attribute (WCAG 3.1.1)
  • · Cookie 'nok_ip_locale' is missing the Secure flag
  • · Cookie 'nok_ip_region' is missing the Secure flag
  • · Scan returned a Akamai Bot Manager bot-protection interstitial, not the actual page

Send Feedback