Global Performance
6/6 locations ✓High global latency — average 776ms across 6 locations, fastest from New York (212ms), slowest from Sao Paulo (1310ms). Netlify edge cache ("Netlify Edge"; fwd=miss; fwd-status=200; stored). 4 locations above the 500ms target.
Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High 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
Your mail setup has problems.
qorvexaa.netlify.app fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.
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.
2 publicly-accessible JavaScript source map(s)
Source maps reveal original source code (variable names, comments, file structure) and are shipped to production by mistake almost universally. The standard fix is a one-line build-tool config change.
Images are 1.1 MB — compress or use modern formats
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
No DMARC record found
Without DMARC, anyone can send phishing emails using your domain name.
No SPF record found
Security gaps expose your site and users to attacks, eroding trust.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$950 investment → $9,253/month returns + USD 150,000 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
4 barrier(s) likely increasing bounce by ~22%.
- Severe layout shift during page loadUsers mis-click when content jumps — converting intent into frustration→ Reserve space for images, ads, and embeds with explicit width/height
- 3 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.0sEvery additional 100ms above 2.5s costs conversions — you're 549ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- No skip-to-content linkKeyboard 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
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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.
Rates reflect fully-loaded developer cost including overhead
Warning:Cost of inaction
Compliance Risk
$150,000
- Multiple <main> landmarks (2 found)ADA Title III: USD 25,000 – USD 150,000
- Skip navigation link is missing (WCAG 2.4.1)ADA Title III: USD 25,000 – USD 150,000
- Heading level skipped: H1 → H3 (missing H2)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$8,219 /mo
+21.6pp bounce · ~2,163 lost visitors/mo
CPC: USD 3.80
Bandwidth Waste
$0.45 /mo
5651.8 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~565 KB per page loadSaves $0.45/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.
2.69 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.05 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
172 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.860
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.61 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.51 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
725 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
931 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.359
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.13 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.
933 ms
Categories
8Performance
Images are 1.1 MB — compress or use modern formats
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 Google Font API sites score 85+ on Compliance; you're at 75 — closing this gap is the highest-leverage improvement.
Technology stack
Angular 20.3.34, on TypeScript, with Netlify CDN
Stack Architecture
Angular 20.3.34
Google Font API HSTS 
Open Graph Zone.js 
TypeScript 
Netlify Netlify CDN All Detected Technologies (8)
Netlify providers hosting and server-less backend services for web applications and static websites.
TypeScript is an open-source language which builds on JavaScript by adding static type definitions.
Angular is a TypeScript-based open-source web application framework led by the Angular Team at Google.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Observations (2)
No build tool detected
A framework (Angular) 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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/sites/qorvexaa.netlify.app)<a href="https://beavercheck.com/sites/qorvexaa.netlify.app"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fqorvexaa.netlify.app" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fqorvexaa.netlify.appExport & 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
3 sprints · 10h total → projected A (91)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · 2 publicly-accessible JavaScript source map(s)
- · No SPF record found
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · No DMARC record found
- · Images are 1.1 MB — compress or use modern formats
Sprint 3: Strategic Improvements
Higher effort, long-term payoff
- · 'unsafe-inline' found in script source