Skip to content
Scanned
2026-09-26 14:42 UTC
Worker
🇺🇸 Santa Clara
Duration
1.1m
Vs prev
—

Global Performance

6/6 locations ✓

High global latency — average 588ms across 6 locations, fastest from Amsterdam (81ms), slowest from Sao Paulo (1080ms). No CDN (document or assets). Cache-Control header is missing. 3 locations above the 500ms target.

United States - Santa Clara
Full audit
819ms
DNS 352ms · TLS 157ms
Spain - Madrid
164ms
DNS 70ms · TLS 33ms
Netherlands - Amsterdam
81ms
DNS 39ms · TLS 17ms
Singapore - Singapore
896ms
DNS 404ms · TLS 166ms
United Stated - New York
486ms
DNS 206ms · TLS 96ms
Brazil - Sao Paulo
1080ms
DNS 459ms · TLS 209ms
CDN: No CDN (document or assets) · Avg TTFB: 588ms · Cache: No cache headers

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

Your mail setup has problems.

nabdz.com fails 1 mail check: No DMARC record found. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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
Critical: 2

Soft 404: server returns HTTP 200 for non-existent pages

Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.

Accessibility › 404 Error Page
Warning: 3

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

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
Warning: 5

External link from fonts.googleapis.com lacks integrity attribute

External resource without SRI — if the third-party CDN is compromised, your site executes attacker-controlled code.

Security › Subresource Integrity
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.
4 security gaps detected — browsers may warn visitors about your site.
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

€743 investment → €6,113/month returns + EUR 500,000 risk avoided

Investment
€743
8.3 h · 5 findings
Monthly returns
€6.113
€73.354/yr
Payback
0.1 mo
+9779% Y1
Regulatory risk avoided EUR 500.000
Or — fix only the top 3 findings
€675 → 0.1 mo payback · +10767% 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.
€113 — 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

5 barrier(s) likely increasing bounce by ~28%.

Barriers
5
2 crit 3 warn
Bounce delta
+28pp
added vs baseline
Score
71
B
Speed
2
Trust
0
Usability
1
Content
0
Nav
2
  • Page takes 14.7s to load
    Users abandon at ~3s — you're 12.2s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Severe layout shift during page load
    Users mis-click when content jumps — converting intent into frustration
    → Reserve space for images, ads, and embeds with explicit width/height
  • High main-thread blocking time
    Page is non-interactive for 292ms after first paint
    → Defer third-party scripts and split large bundles
  • 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
  • 2 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

€743 8.3 developer hours at €90/hr
Quick wins
€113 3 fixes in ~75 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

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

Compliance Risk

€500.000

EAA
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1.000 – EUR 500.000

Bounce-Rate Cost

€6.112 /mo

+27.8pp bounce · ~2,778 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,83 /mo

11254.7 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves €0,83/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

42
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
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.

3.45 s

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

14.73 s

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

292 ms

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

0.334

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

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

16.05 s

Desktop

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

933 ms

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

2.73 s

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

69 ms

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

0.085

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

1.82 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.74 s

Categories

8
Avg score 81.4

How you compare

Where this site stands against peers running the same stack.

Google Font API · 1313 peers
You 84
·
Avg 75
+9 above average
0 50 100
Security P98Accessibility P91Compliance P12Infrastructure P14Performance P81SEO P66Sustainability P38Content P55

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

Better than 92% of Google Font API sites See full Google Font API benchmark →
HSTS · 3139 peers
You 84
·
Avg 77
+7 above average
0 50 100
Infrastructure P10Compliance P10Security P87Accessibility P80Sustainability P30Performance P70SEO P67Content P57

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

Better than 82% of HSTS sites See full HSTS benchmark →

Technology stack

Google Font API

8 technologies detected 1 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
Google Font API HSTS HTTP/3 Open Graph Priority Hints Svelte SvelteKit Vite

All Detected Technologies (8)

Google Font API is a web service that supports open-source font files that can be used on your web designs.

Categories Font scripts Website https://fonts.google.com/ Detected by BeaverCheck

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

Svelte is a free and open-source front end compiler created by Rich Harris and maintained by the Svelte core team members.

Categories JavaScript frameworks Website https://svelte.dev Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

SvelteKit is the official Svelte framework for building web applications with a flexible filesystem-based routing.

Categories UI frameworks Website https://kit.svelte.dev Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Vite is a rapid development tool for modern web projects.

Categories Miscellaneous Website https://vitejs.dev Detected by BeaverCheck

Observations (2)

No build tool detected

A framework (Google Font API) 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%2Fportfolio.nabdz.com)](https://beavercheck.com/sites/nabdz.com)
<a href="https://beavercheck.com/sites/nabdz.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fportfolio.nabdz.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fportfolio.nabdz.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

3 sprints · 8h total → projected B (89)

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

3 findings 1h → B (87)
  • · Soft 404: server returns HTTP 200 for non-existent pages
  • · Cross-Origin-Opener-Policy header is missing
  • · External link from fonts.googleapis.com lacks integrity attribute

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

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

Sprint 3: Strategic Improvements

+1

Higher effort, long-term payoff

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

Send Feedback