Global Performance
6/6 locations ✓Acceptable global latency — average 303ms across 6 locations, fastest from Singapore (34ms), slowest from Sao Paulo (655ms). Document and assets on Cloudflare. 2 locations above the 500ms target.
Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
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.
sitiscommesse.com fails 1 mail check: DMARC policy is none — monitoring only. 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.
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.
is missing width/height — may cause layout shift
Performance issues directly impact user engagement and conversion rates.
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.
93 third-party resources (100% 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
€460 investment → €6,231/month returns + EUR 500,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
7 barrier(s) likely increasing bounce by ~29%.
- 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
- 26 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 453ms after first paint→ Defer third-party scripts and split large bundles
- 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
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
€500.000
- No <main> landmark foundEAA: EUR 1.000 – EUR 500.000
- 2 of 3 <nav> elements are unlabeledEAA: EUR 1.000 – EUR 500.000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€3.113 /mo
+29.0pp bounce · ~2,898 lost visitors/mo
CPC: EUR 1.07
Bandwidth Waste
€0,14 /mo
1832.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~183 KB per page loadSaves €0,14/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 2 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.
2.71 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.
453 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.104
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.96 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.42 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.18 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.95 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.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.38 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.96 s
Categories
8Performance
is missing width/height — may cause layout shift
Security
Content-Security-Policy header is missing
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 80 — closing this gap is the highest-leverage improvement.
Top 10% of WordPress sites score 96+ on Content; you're at 80 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, with Cloudflare CDN
Stack Architecture
Cart Functionality 
WordPress 
Cloudflare Bot Management HSTS 
HTTP/3 
LazySizes 
Open Graph 
core-js 3.6.5 Cloudflare All Detected Technologies (9)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
Open Graph is a protocol that is used to integrate any web page into the social graph.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Observations (3)
WordPress detected — review security configuration
WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.
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
9 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/sitiscommesse.com)<a href="https://beavercheck.com/sites/sitiscommesse.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsitiscommesse.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsitiscommesse.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 · 5h total → projected A (92)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · No <main> landmark found
- · 93 third-party resources (100% of weight)
- · 25 link(s) open in a new tab without rel=noopener
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · is missing width/height — may cause layout shift