Global Performance
6/6 locations ✓Acceptable global latency — average 428ms across 6 locations, fastest from New York (202ms), slowest from Sao Paulo (796ms). Vercel edge cache (STALE). 2 locations above the 500ms target.
Audit overview
Compliance needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
0High impact, low effort — start here.
Nothing in this quadrant — good news.
Strategic
5High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
'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.
1 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
25 inline style attribute(s) detected
Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.
3 font preload(s) missing `crossorigin` -- font will be downloaded twice
Performance issues directly impact user engagement and conversion rates.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$1,500 investment → $5,289/month returns + USD 157,500 risk avoided
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 ~15%.
- 41 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- Page loads in 3.1sEvery additional 100ms above 2.5s costs conversions — you're 616ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- No Content-Security-Policy headerHigher XSS blast radius — one compromised script can exfiltrate the checkout form→ Ship a reporting-only CSP first, then enforce once violations are clean
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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.
Rates reflect fully-loaded developer cost including overhead
Cost of inaction
Compliance Risk
$157,500
- No privacy policy link detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no privacy policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Privacy Policy not detectedCCPA/CPRA: USD 2,500 – USD 7,500
- 1 of 2 <nav> elements are unlabeledADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$4,129 /mo
+15.3pp bounce · ~1,535 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.17 /mo
2123.8 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~212 KB per page loadSaves $0.17/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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 1 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
Your data stays in your browser — nothing is sent to our servers
Lighthouse
Mobile
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.17 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.12 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
92 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.45 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.
4.34 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
450 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
783 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.
450 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.
783 ms
Categories
8Performance
1 render-blocking <script src> tag(s) without async/defer
Security
'unsafe-inline' found in script source
Accessibility
All checks pass
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of Cloudflare sites score 85+ on Compliance; you're at 65 — closing this gap is the highest-leverage improvement.
Top 10% of Google Search Console sites score 85+ on Compliance; you're at 65 — closing this gap is the highest-leverage improvement.
Technology stack
Cloudflare, on Turbopack, hosted on Next.js, with Vercel Edge CDN
Stack Architecture
Cloudflare Google Search Console HSTS 
Lucide 
Open Graph 
Priority Hints 
RSS 
React 
Tailwind CSS 
Webpack 
Turbopack 
Vercel Edge 
Next.js 16.2.6 Next.js App Router Vercel All Detected Technologies (15)
Next.js is a React framework for developing single page Javascript applications.
The Next.js App Router is a new paradigm for building applications using React's latest features.
Vercel is a cloud platform for static frontends and serverless functions.
Turbopack is an incremental bundler for JavaScript and TypeScript, written in Rust and integrated into the Next.js framework for optimized build performance.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
Observations (2)
No build tool detected
A framework (Cloudflare) 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
15 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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/4577201b-9440-44de-b818-a38c556fa728)<a href="https://beavercheck.com/results/4577201b-9440-44de-b818-a38c556fa728"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FGonenativeva.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2FGonenativeva.comExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
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 · 15h total → projected A (92)
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
- · 1 render-blocking <script src> tag(s) without async/defer
- · 3 font preload(s) missing `crossorigin` -- font will be downloaded twice
- · 25 inline style attribute(s) detected
Sprint 3: Strategic Improvements
+1Higher effort, long-term payoff
- · 'unsafe-inline' found in script source