Global Performance
6/6 locations ✓High global latency — average 620ms across 6 locations, fastest from New York (401ms), slowest from Santa Clara (882ms). No CDN detected. 5 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
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)
10 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.
5 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.
8 image(s) missing alt attribute
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
8 image-in-link without alt text
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
119 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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$700 investment → $12,098/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
6 barrier(s) likely increasing bounce by ~28%.
- Page takes 10.7s to loadUsers abandon at ~3s — you're 8.2s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- High main-thread blocking timePage is non-interactive for 252ms after first paint→ Defer third-party scripts and split large bundles
- 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, …)
- 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
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
$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 (2 found)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$7,407 /mo
+27.5pp bounce · ~2,753 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.48 /mo
5980.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~598 KB per page loadSaves $0.48/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 4 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.
9.38 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.73 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
252 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.
9.38 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.
11.65 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.00 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.22 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
22 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.00 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.
2.48 s
Categories
8Performance
All checks pass
Security
119 inline style attribute(s) detected
Accessibility
10 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 Amazon Route 53 sites score 86+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Top 10% of Apple sites score 85+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, hosted on Amazon Web Services, with Amazon S3 CDN
Stack Architecture
Open Graph 
Priority Hints 
React 
React Router 8.3.0
Tailwind CSS 
lit-html 1.1.2
Amazon S3 
Amazon Web Services 
GitHub Pages All Detected Technologies (19)
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.
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.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
React is an open-source JavaScript library for building user interfaces or UI components.
React Router provides declarative routing for React.
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
19 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/github.com)<a href="https://beavercheck.com/sites/github.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.com%2F007revad%2FSynology_Docker_Export" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.com%2F007revad%2FSynology_Docker_ExportExport & 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 B (85)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 10 link(s) with no accessible text
- · 5 button(s) with no accessible text
- · 8 image-in-link without alt text
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 8 image(s) missing alt attribute
- · 119 inline style attribute(s) detected