Audit overview
Accessibility and Content 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)
'unsafe-eval' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
'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.
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.
Soft 404: server returns HTTP 200 for non-existent pages
Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.
5 third-party resources (98% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$1,267 investment → $9,679/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
7 barrier(s) likely increasing bounce by ~20%.
- Page loads in 3.7sEvery additional 100ms above 2.5s costs conversions — you're 1.2s over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
- No Open Graph tagsLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop→ Add og:title, og:description, og:image, og:url to the page head
- 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, …)
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
- 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
Bounce-Rate Cost
$7,476 /mo
+19.7pp bounce · ~1,967 lost visitors/mo
CPC: USD 3.80
Bandwidth Waste
$0.09 /mo
1174.0 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~117 KB per page loadSaves $0.09/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.
3.67 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.67 s
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.
3.67 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.67 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.26 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.26 s
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.
1.26 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.
1.26 s
Categories
8Performance
5 third-party resources (98% of weight)
Security
'unsafe-eval' found in script source
Accessibility
No <main> landmark found
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 96+ on Content; you're at 68 — closing this gap is the highest-leverage improvement.
Top 10% of Apple sites score 95+ on Content; you're at 68 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, hosted on Amazon Web Services, with Amazon S3 CDN
Stack Architecture
Optimizely 
Varnish 
Amazon S3 
Fastly 
Amazon Web Services All Detected Technologies (12)
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.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Varnish is a reverse caching proxy.
Optimizely is an experimentation platform that helps developers build and run A/B tests on websites.
Observations (2)
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
12 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/9e48cd4c-8cdb-4d0d-b0c2-7011913f93d0)<a href="https://beavercheck.com/results/9e48cd4c-8cdb-4d0d-b0c2-7011913f93d0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgoodrx.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgoodrx.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 · 13h total → projected B (87)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · No <main> landmark found
- · Soft 404: server returns HTTP 200 for non-existent pages
- · 5 third-party resources (98% of weight)
Sprint 3: Strategic Improvements
+5Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source