Global Performance
6/6 locations ✓Excellent global latency — average 49ms across 6 locations, fastest from Singapore (13ms), slowest from Madrid (110ms). No CDN detected.
Audit overview
Compliance and Sustainability need attention; the other categories are in good shape.
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)
Page weighs 13.5 MB (4.4 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
1 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
2 button(s) with no accessible text
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
1 font preload(s) missing `crossorigin` -- font will be downloaded twice
Performance issues directly impact user engagement and conversion rates.
1 link(s) open in a new tab without rel=noopener
target="_blank" without rel="noopener" lets the destination tab navigate the original via window.opener -- a reverse-tabnabbing phishing primitive.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$375 investment → $13,210/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
5 barrier(s) likely increasing bounce by ~28%.
- Page takes 9.5s to loadUsers abandon at ~3s — you're 7.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 4.0sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 1 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
- No structured dataNo 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, …)
- 2 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
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
$157,500
- 3 non-essential cookie(s) set without consent bannerCCPA/CPRA: USD 2,500 – USD 7,500
- 1 tracking cookie(s) set before consent interactionCCPA/CPRA: USD 2,500 – USD 7,500
- Multiple H1 headings (4 found)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
- 1 control(s) without accessible labelADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$7,473 /mo
+27.8pp bounce · ~2,778 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$1.11 /mo
13872.6 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~1.4 MB per page loadSaves $1.11/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 3 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.
3.83 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.49 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.95 s
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.
7.72 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.
32.59 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
962 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.83 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
218 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.
2.15 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.54 s
Categories
8Performance
Page weighs 13.5 MB (4.4 MB transferred)
Security
1 link(s) open in a new tab without rel=noopener
Accessibility
1 control(s) without accessible label
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 Amazon Route 53 sites score 86+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
Contentful, hosted on Amazon Web Services, with Amazon S3 CDN
Stack Architecture
All Detected Technologies (21)
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
GitHub Pages is a static site hosting service.
Contentful is an API-first content management platform to create, manage and publish content on any digital channel.
GSAP is an animation library that allows you to create animations with JavaScript.
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.
React is an open-source JavaScript library for building user interfaces or UI components.
React Router provides declarative routing for React.
Three.js is a cross-browser JavaScript library and application programming interface used to create and display animated 3D computer graphics in a web browser using WebGL.
lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.
Observations (3)
Hosted on GitHub Pages
GitHub Pages provides free static hosting with automatic HTTPS. Limitations: no server-side code, 1GB site size limit, 100GB/month bandwidth.
No build tool detected
A framework (Amazon Route 53) 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
21 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/0ea743af-7e94-4add-b78b-a589792c6f2c)<a href="https://beavercheck.com/results/0ea743af-7e94-4add-b78b-a589792c6f2c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.comFix Plan
Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.
Three-week fix plan
2 sprints · 4h total → projected B (87)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 13.5 MB (4.4 MB transferred)
- · 2 button(s) with no accessible text
- · 1 link(s) open in a new tab without rel=noopener
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 1 control(s) without accessible label
- · 1 font preload(s) missing `crossorigin` -- font will be downloaded twice


