Skip to content
https://adamnordling.se Export & share
SE · SEK (kr) · Estimated Applicable regulations: GDPR · ePrivacy Directive · EAA Dev cost: SEK 850/hr How jurisdiction is detected
Recent Trends
Performance stable →
100
TTFB stable →
137ms
FCP stable →
1.3s
LCP stable →
1.3s
Scanned
2026-09-23 06:02 UTC
Worker
🇪🇸 Madrid
Duration
32.00s
Vs prev
Improved by +1

Global Performance

6/6 locations

Strong global performance — average 113ms across 6 locations, fastest from Sao Paulo (55ms), slowest from Singapore (148ms). Cloudflare edge cache (DYNAMIC).

Spain - Madrid
Full audit
137ms
DNS 31ms · TLS 24ms
Netherlands - Amsterdam
136ms
DNS 7ms · TLS 13ms
United States - Santa Clara
127ms
DNS 10ms · TLS 14ms
United Stated - New York
73ms
DNS 6ms · TLS 10ms
Singapore - Singapore
148ms
DNS 15ms · TLS 15ms
Brazil - Sao Paulo
55ms
DNS 5ms · TLS 9ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 113ms · 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

3

High impact, low effort — start here.

Strategic

2

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

Top Priorities (5)

Sorted by impact
Critical: 1

'unsafe-inline' found in script source

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Security › Content Security Policy
Warning: 2

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

https://adamnordling.se/: 716ms CPU time

Informational: CPU time spent on this resource. Total >1s is a perf budget violation.

Performance › JS Execution Cost
Critical: 4

Both www and non-www versions serve content

Serving both www and non-www splits SEO signals between two URLs and creates session-cookie scope confusion.

Infrastructure › URL Variants
Warning: 5

11 link(s) open in new tab without warning

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Accessibility › Link & Button Quality
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. The 1 performance issue below shapes how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.
2 security gaps detected — browsers may warn visitors about your site.
1 performance issue — Akamai's research found 53% of mobile users abandon pages over 3s.
1 infrastructure issue creates a performance ceiling no frontend fix can overcome.

Business case

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

Return on investment

SEK 6,800 investment → SEK 3,791/month returns + EUR 120,500,000 risk avoided

Investment
SEK 6.800
8.0 h · 4 findings
Monthly returns
SEK 3.791
SEK 45.495/yr
Payback
1.8 mo
+569% Y1
Regulatory risk avoided EUR 120.500.000
Or — fix only the top 3 findings
SEK 6.3751.7 mo payback · +614% 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.
SEK 850 — 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

3 barrier(s) likely increasing bounce by ~7%.

Barriers
3
3 warn
Bounce delta
+7pp
added vs baseline
Score
91
A
Speed
0
Trust
0
Usability
0
Content
1
Nav
2
  • Content is hard to read
    Graduate-level reading difficulty — limits the addressable audience for product or blog pages
    → Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
  • 1 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab

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

Remediation cost

kr6,800 8.0 developer hours at kr850/hr
Quick wins
kr850 2 fixes in ~60 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

Warning:Cost of inaction

SEK 3.791 / month at risk ~SEK 45.495 / 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 found (page links and common paths checked)
    GDPR: EUR 10.000 – EUR 20.000.000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5.000 – EUR 10.000.000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

SEK 3.791 /mo

+7.2pp bounce · ~720 lost visitors/mo

CPC: SEK 5.26

Bandwidth Waste

SEK 0,20 /mo

233.6 MB/mo × 0.842 SEK/GB

  • Optimize transfer: save ~23 KB per page load
    Saves SEK 0,20/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 2 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

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
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.

1.29 s

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

1.29 s

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

0 ms

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

0.000

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

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

1.29 s

Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
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.

349 ms

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

469 ms

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

0 ms

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

0.000

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

363 ms

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

469 ms

Categories

8
Avg score 89.6

How you compare

Where this site stands against peers running the same stack.

Bootstrap · 1049 peers
You 91
·
Avg 75
+16 above average
0 50 100
Performance P99Security P99Accessibility P98SEO P97Compliance P4Sustainability P94Content P91Infrastructure P67

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

Better than 99% of Bootstrap sites See full Bootstrap benchmark →
Google Search Console · 4289 peers
You 91
·
Avg 75
+16 above average
0 50 100
Compliance P4Performance P96Security P96SEO P96Accessibility P93Sustainability P90Content P87Infrastructure P61

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

Better than 96% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Bootstrap, with Cloudflare CDN

8 technologies detected 2 stack layers 1 with CPE identifier Complex

Stack Architecture

Framework
Bootstrap Google Search Console HSTS HTTP/3 Open Graph Priority Hints Tailwind CSS
CDN
Cloudflare

All Detected Technologies (8)

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

Categories CDN Website https://www.cloudflare.com Detected by BeaverCheck Evidence Server header in redirect: cloudflare
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Framework Website https://getbootstrap.com Detected by BeaverCheck · Medium Evidence Found 3 Bootstrap class patterns in HTML
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=gTQrzzuuje5-RZY3P6XVo9SOJO9A_HcoEN2OvZVAeuE

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

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 15 unique Tailwind utility classes in HTML

Observations (2)

No build tool detected

A framework (Bootstrap) 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.

Complex technology stack detected

8 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

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%2Fadamnordling.se)](https://beavercheck.com/sites/adamnordling.se)
<a href="https://beavercheck.com/sites/adamnordling.se"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fadamnordling.se" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fadamnordling.se

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

3 sprints · 8h total → projected A (95)

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

3 findings 1h → A (93)
  • · Both www and non-www versions serve content
  • · https://adamnordling.se/: 716ms CPU time
  • · 11 link(s) open in new tab without warning

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

1 findings 1h → A (94)
  • · Cross-Origin-Embedder-Policy header is missing

Sprint 3: Strategic Improvements

+1

Higher effort, long-term payoff

1 findings 6h → A (95)
  • · 'unsafe-inline' found in script source

Send Feedback