Global Performance
6/6 locations ✓High global latency — average 2644ms across 6 locations, fastest from Santa Clara (846ms), slowest from Singapore (5055ms). Cloudflare edge cache (DYNAMIC). Cache-Control header is missing. 6 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
3High impact, low effort — start here.
Strategic
2High 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Page weighs 18.4 MB (19.7 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
8 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$667 investment → $7,344/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
7 barrier(s) likely increasing bounce by ~27%.
- Page takes 19.0s to loadUsers abandon at ~3s — you're 16.5s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.5sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 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
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
- 8 link(s) with generic text ("click here", "read more")Screen-reader users navigating by link list see no context — and search engines can't infer relevance→ Rewrite with descriptive phrases that identify the destination
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
Cost of inaction
Compliance Risk
$150,000
- No <main> landmark foundADA 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: H2 → H4 (missing H3)ADA Title III: USD 25,000 – USD 150,000
- Heading level skipped: H2 → H4 (missing H3)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$7,339 /mo
+27.3pp bounce · ~2,728 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$4.96 /mo
61957.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~6.2 MB per page loadSaves $4.96/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 5 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.
11.37 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
19.00 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.49 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.034
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
23.56 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.
19.92 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.82 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.00 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
187 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.92 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.
3.72 s
Categories
8Performance
Page weighs 18.4 MB (19.7 MB transferred)
Security
Content-Security-Policy header is missing
Accessibility
8 link(s) with no accessible text
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 Search Console sites score 95+ on Infrastructure; you're at 85 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 95+ on Infrastructure; you're at 85 — closing this gap is the highest-leverage improvement.
Technology stack
Google Search Console, with Cloudflare CDN
Stack Architecture
HTTP/3 Microsoft 365 
Nuxt UI Nuxt.js 
Open Graph 
Pinia 
Priority Hints 
Vue.js 
Cloudflare All Detected Technologies (11)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Nuxt UI is a customizable UI library designed for Nuxt.
Nuxt is a Vue framework for developing modern web applications.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Pinia is a state management library for Vue.js.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Observations (2)
No build tool detected
A framework (Google Search Console) 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
11 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/a455da9f-c9b9-4f49-b9b8-63457bb11b59)<a href="https://beavercheck.com/results/a455da9f-c9b9-4f49-b9b8-63457bb11b59"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnorriq.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fnorriq.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 · 7h total → projected A (92)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 18.4 MB (19.7 MB transferred)
- · No <main> landmark found
- · 8 link(s) with no accessible text
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found