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
Your mail setup has problems.
mercedes-blanche.com 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
1 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.
No H1 heading found
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
25 link(s) open in a new tab without rel=noopener
target="_blank" without rel="noopener" lets the destination tab navigate the original via window.opener -- a reverse-tabnabbing phishing primitive.
32 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
$792 investment → $5,476/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 ~27%.
- Page takes 12.4s to loadUsers abandon at ~3s — you're 9.9s 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 420ms after first paint→ Defer third-party scripts and split large bundles
- HSTS is enabled but max-age is short (15552000s)First-visit protection is in place, but browsers forget the policy sooner than recommended→ Raise Strict-Transport-Security max-age to at least 31536000 (1 year)
- 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
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 found (page links and common paths checked)CCPA/CPRA: USD 2,500 – USD 7,500
- Privacy Policy not detectedCCPA/CPRA: USD 2,500 – USD 7,500
- 3 of 3 <nav> elements are unlabeledADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$3,106 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: USD 1.16
Bandwidth Waste
$0.62 /mo
7730.4 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~773 KB per page loadSaves $0.62/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 3 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.25 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.37 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
420 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.070
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.32 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.
12.60 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
926 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
81 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.51 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.35 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
1 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 Cart Functionality sites score 85+ on Compliance; you're at 62 — closing this gap is the highest-leverage improvement.
Technology stack
Squarespace 7.1
Stack Architecture
Cart Functionality 
Squarespace Commerce 7.1 Squarespace 7.1
Modernizr 2.8.3
Open Graph 
Priority Hints 
Stimulus 
YUI 3.17.2
core-js 3.26.0parallax.js All Detected Technologies (11)
Squarespace provides Software-as-a-Service (SaaS) for website building and hosting, and allows users to use pre-built website templates.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
Squarespace Commerce is an ecommerce platform designed to facilitate the creation of websites and online stores, with domain registration and web hosting included.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Modernizr is a JavaScript library that detects the features available in a user's browser.
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.
A modest JavaScript framework for the HTML you already have.
YUI is a JavaScript and CSS library with more than 30 unique components including low-level DOM utilities and high-level user-interface widgets.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Simple parallax scrolling effect.
Observations (2)
No build tool detected
A framework (HSTS) 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
11 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/mercedes-blanche.com)<a href="https://beavercheck.com/sites/mercedes-blanche.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mercedes-blanche.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mercedes-blanche.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 · 8h total → projected B (86)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · No H1 heading found
- · 1 link(s) with no accessible text
- · 25 link(s) open in a new tab without rel=noopener
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · 32 inline style attribute(s) detected