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
Your mail setup has problems.
murti-hub-neon.vercel.app fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.
Top Priorities (5)
'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.
Page weighs 11.4 MB (9.7 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.
3 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.
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
$800 investment → $3,282/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
6 barrier(s) likely increasing bounce by ~28%.
- Page takes 46.3s to loadUsers abandon at ~3s — you're 43.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 4 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
- 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
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
- 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
$150,000
- Multiple <main> landmarks (2 found)ADA 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: H1 → H3 (missing H2)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$3,279 /mo
+28.3pp bounce · ~2,827 lost visitors/mo
CPC: USD 1.16
Bandwidth Waste
$2.44 /mo
30449.7 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~3.0 MB per page loadSaves $2.44/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.59 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
46.32 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
149 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.
6.83 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.
46.32 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
674 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.69 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
200 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.036
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.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.
8.70 s
Categories
8Performance
Page weighs 11.4 MB (9.7 MB transferred)
Security
'unsafe-inline' found in script source
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 Cart Functionality sites score 85+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Top 10% of Google Font API sites score 85+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
GSAP, hosted on Vercel, with Vercel Edge CDN
Stack Architecture
Cart Functionality 
GSAP 
Google Font API HSTS 
Lenis 1.3.27
Lucide 
Open Graph 
PWA 
Priority Hints 
Tailwind CSS 
Vercel Edge Vercel All Detected Technologies (12)
Vercel is a cloud platform for static frontends and serverless functions.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
GSAP is an animation library that allows you to create animations with JavaScript.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Lenis is a smooth scroll library to normalise the scrolling experience across devices.
Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Progressive Web Apps (PWAs) are web apps built and enhanced with modern APIs to deliver enhanced capabilities, reliability, and installability while reaching anyone, anywhere, on any device, all with a single codebase.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Observations (2)
No build tool detected
A framework (GSAP) 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/sites/murti-hub-neon.vercel.app)<a href="https://beavercheck.com/sites/murti-hub-neon.vercel.app"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmurti-hub-neon.vercel.app%2F%3Fpage%3Dshop-all%26category%3DGajanan%2BMaharaj" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmurti-hub-neon.vercel.app%2F%3Fpage%3Dshop-all%26category%3DGajanan%2BMaharajExport & 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
3 sprints · 8h total → projected A (91)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 11.4 MB (9.7 MB transferred)
- · 3 button(s) with no accessible text
- · Soft 404: server returns HTTP 200 for non-existent pages
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 1 control(s) without accessible label
Sprint 3: Strategic Improvements
+2Higher effort, long-term payoff
- · 'unsafe-inline' found in script source