Global Performance
6/6 locations ✓Acceptable global latency — average 204ms across 6 locations, fastest from New York (31ms), slowest from Singapore (435ms). AWS CloudFront edge cache (Miss from cloudfront).
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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Page body has only 183 chars of text -- likely empty / placeholder
Security gaps expose your site and users to attacks, eroding trust.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$725 investment → $12,991/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
9 barrier(s) likely increasing bounce by ~31%.
- Page takes 6.3s to loadUsers abandon at ~3s — you're 3.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- 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
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
- No privacy policy link detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Privacy Policy not detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Skip navigation link is missing (WCAG 2.4.1)ADA Title III: USD 25,000 – USD 150,000
- No headings foundADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$8,219 /mo
+30.6pp bounce · ~3,056 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.25 /mo
3075.8 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~308 KB per page loadSaves $0.25/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.
4.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.33 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
88 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.206
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.39 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.
6.96 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
921 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.40 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.011
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.50 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.41 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
Soft 404: server returns HTTP 200 for non-existent pages
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 69 — closing this gap is the highest-leverage improvement.
Top 10% of Google Font API sites score 96+ on SEO; you're at 82 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, hosted on AWS, with AWS CloudFront CDN
Stack Architecture
Google Font API 
HTTP/3 
Lucide 
React 
React Router 6
Tailwind CSS 
AWS CloudFront Amazon CloudFront 
Amazon S3 
AWS Amazon Web Services All Detected Technologies (12)
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
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.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.
React is an open-source JavaScript library for building user interfaces or UI components.
React Router provides declarative routing for React.
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/b987c1c2-66da-4b4f-977f-2055946a22fe)<a href="https://beavercheck.com/results/b987c1c2-66da-4b4f-977f-2055946a22fe"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpullitpacks.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpullitpacks.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 B (88)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · HSTS header is missing
- · Page body has only 183 chars of text -- likely empty / placeholder
- · Soft 404: server returns HTTP 200 for non-existent pages
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found