Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
5High impact, low effort — start here.
Strategic
0High impact, requires investment.
Nothing in this quadrant — good news.
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)
Cookie 'bc_amplitude_experimentation' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
Cookie 'c_consent' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
Cookie 'originUrl' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
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.
No H1 heading found
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$108 investment → $7,568/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
8 barrier(s) likely increasing bounce by ~33%.
- Page takes 5.0s to loadUsers abandon at ~3s — you're 2.5s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 4.4sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- Severe layout shift during page loadUsers mis-click when content jumps — converting intent into frustration→ Reserve space for images, ads, and embeds with explicit width/height
- 57 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
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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
- No <main> landmark foundADA Title III: USD 25,000 – USD 150,000
- 3 of 3 <nav> elements are unlabeledADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$3,804 /mo
+32.8pp bounce · ~3,279 lost visitors/mo
CPC: USD 1.16
Bandwidth Waste
$0.67 /mo
8393.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~839 KB per page loadSaves $0.67/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.
1.54 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.00 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4.41 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
1.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.98 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.
13.37 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
399 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.51 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.65 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.009
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.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.
5.08 s
Categories
8Performance
All checks pass
Security
Cookie 'bc_amplitude_experimentation' is missing the Secure flag
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 Cart Functionality sites score 95+ on Content; you're at 78 — closing this gap is the highest-leverage improvement.
Technology stack
Makeswift, on Emotion, hosted on Next.js, with Cloudflare CDN
Stack Architecture
All Detected Technologies (16)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Next.js is a React framework for developing single page Javascript applications.
Vercel is a cloud platform for static frontends and serverless functions.
Emotion is a library designed for writing CSS styles with JavaScript.
Makeswift is a no-code website builder with the power and detail of a design tool.
BigCommerce is a hosted ecommerce platform that allows business owners to set up an online store and sell their products online.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Radix UI is a React-based user interface component library that offers accessible, responsive, and customisable components for building web applications.
React is an open-source JavaScript library for building user interfaces or UI components.
Segment is a customer data platform (CDP) that helps you collect, clean, and control your customer data.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
Webpack is an open-source JavaScript module bundler.
Observations (2)
No build tool detected
A framework (Cloudflare Bot Management) 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
16 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/e1b5d271-d8c4-4693-a415-ec5f55d5ace0)<a href="https://beavercheck.com/results/e1b5d271-d8c4-4693-a415-ec5f55d5ace0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.bigcommerce.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.bigcommerce.comFix Plan
Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.
Three-week fix plan
1 sprints · 1h total → projected B (85)
Sprint 1: Quick Wins
+9Highest ROI — low effort, high impact
- · No <main> landmark found
- · No H1 heading found
- · Cookie 'bc_amplitude_experimentation' is missing the Secure flag
- · Cookie 'c_consent' is missing the Secure flag
- · Cookie 'originUrl' is missing the Secure flag


