Skip to content
Recent Trends
Performance degrading ↓
70
TTFB improving ↑
169ms
FCP degrading ↓
1.9s
LCP degrading ↓
5.8s
Scanned
2026-05-07 16:27 UTC
Worker
🇺🇸 New York
Duration
40.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 404ms across 6 locations, fastest from Amsterdam (149ms), slowest from Sao Paulo (747ms). No CDN detected. 2 locations above the 500ms target.

United Stated - New York
Full audit
223ms
DNS 9ms · TLS 39ms
Spain - Madrid
231ms
DNS 21ms · TLS 130ms
Netherlands - Amsterdam
149ms
DNS 15ms · TLS 108ms
United States - Santa Clara
392ms
DNS 9ms · TLS 78ms
Singapore - Singapore
684ms
DNS 8ms · TLS 500ms
Brazil - Sao Paulo
747ms
DNS 13ms · TLS 328ms
CDN: No CDN · Avg TTFB: 404ms · Cache: max-age=0, private, 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
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

'unsafe-eval' 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

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

HSTS is missing includeSubDomains

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

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

€1,148 investment → €7,891/month returns + EUR 120,500,000 risk avoided

Investment
€1,148
13.5 h · 5 findings
Monthly returns
€7,891
€94,695/yr
Payback
0.1 mo
+8152% Y1
Regulatory risk avoided EUR 120,500,000
Or — fix only the top 3 findings
€1,1050.1 mo payback · +8470% 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.
€43 — 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

6 barrier(s) likely increasing bounce by ~24%.

Barriers
6
1 crit 5 warn
Bounce delta
+24pp
added vs baseline
Score
75
B
Speed
1
Trust
2
Usability
0
Content
2
Nav
1
  • Page takes 5.2s to load
    Users abandon at ~3s — you're 2.7s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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 structured data
    No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
    → Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
  • Thin content
    Under 300 words — visitors bounce looking for substance, search engines rank competitors first
    → Add a substantive FAQ, product detail, or case-study section

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

Remediation cost

€1,148 13.5 developer hours at €85/hr
Quick wins
€43 2 fixes in ~30 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

Cost of inaction

€10,047,019 / month at risk ~€120,564,231 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • 1 non-essential cookie(s) set without consent banner
    GDPR: EUR 5,000 – EUR 10,000,000
  • 1 non-essential cookie(s) set without consent banner
    GDPR: EUR 10,000 – EUR 20,000,000
  • 1 non-essential cookie(s) set without consent banner
    ePrivacy Directive: EUR 5,000 – EUR 100,000,000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000

Bounce-Rate Cost

€5,352 /mo

+24.3pp bounce · ~2,433 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0.18 /mo

2474.5 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~247 KB per page load
    Saves €0.18/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

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

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

5.15 s

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

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

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

5.16 s

Desktop

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

316 ms

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

957 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.014

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

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

959 ms

Categories

8
Avg score 81.8

How you compare

Where this site stands against peers running the same stack.

HSTS · 2418 peers
You 81
·
Avg 75
+6 above average
0 50 100
Performance P94Sustainability P94Accessibility P90Compliance P12SEO P16Security P64Content P57Infrastructure P47

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

Better than 89% of HSTS sites See full HSTS benchmark →
Open Graph · 3295 peers
You 81
·
Avg 74
+7 above average
0 50 100
SEO P2Performance P97Compliance P5Sustainability P95Accessibility P91Security P80Content P38Infrastructure P53

Top 10% of Open Graph sites score 96+ on SEO; you're at 77 — closing this gap is the highest-leverage improvement.

Better than 92% of Open Graph sites See full Open Graph benchmark →

Technology stack

HSTS, on Elixir, hosted on Fly.io

8 technologies detected 3 stack layers 1 with CPE identifier Complex

Stack Architecture

Framework
HSTS Open Graph Phoenix Framework Phoenix LiveView Tailwind CSS
Runtime
Elixir Erlang
Hosting
Fly.io

All Detected Technologies (8)

Fly is a platform for running full stack apps and databases.

Categories PaaS Website https://fly.io Detected by BeaverCheck Evidence Header: fly-request-id

Elixir is a dynamic, functional language designed for building scalable and maintainable applications.

Categories Programming languages Website https://elixir-lang.org Detected by BeaverCheck

Erlang is a general-purpose, concurrent, functional programming language, and a garbage-collected runtime system.

Categories Programming languages Website https://www.erlang.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

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

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

Phoenix Framework is an open-source web application framework built using the Elixir programming language.

Categories Web frameworks Website https://www.phoenixframework.org Detected by BeaverCheck

Phoenix LiveView is a library that brings live, interactive, real-time user experiences to your Phoenix applications.

Categories Web frameworks Website https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html Detected by BeaverCheck
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 57 unique Tailwind utility classes in HTML

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.

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%2Fpotentialspouse.com)](https://beavercheck.com/results/5d28ad8e-b453-42f3-be6a-a59db2b00a5c)
<a href="https://beavercheck.com/results/5d28ad8e-b453-42f3-be6a-a59db2b00a5c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpotentialspouse.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fpotentialspouse.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 · 14h total → projected B (87)

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

2 findings 0h → B (83)
  • · Cross-Origin-Opener-Policy header is missing
  • · HSTS is missing includeSubDomains

Sprint 2: Core Fixes

Medium effort, high structural impact

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

Sprint 3: Strategic Improvements

+4

Higher effort, long-term payoff

2 findings 12h → B (87)
  • · 'unsafe-eval' found in script source
  • · 'unsafe-inline' found in script source

Send Feedback