Global Performance
6/6 locations ✓High global latency — average 732ms across 6 locations, fastest from Madrid (247ms), slowest from Sao Paulo (1222ms). AWS CloudFront edge cache (Miss from cloudfront). 4 locations above the 500ms target.
Audit overview
Sustainability needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High 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.
party-schlaudt.de 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)
Page weighs 13.6 MB (9.6 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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.
105 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
12 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
6 `@font-face` rule(s) without `font-display` -- causes FOIT
Performance issues directly impact user engagement and conversion rates.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€735 investment → €2,642/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
6 barrier(s) likely increasing bounce by ~28%.
- Page takes 18.8s to loadUsers abandon at ~3s — you're 16.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.0sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 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
- 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
- No skip-to-content linkKeyboard and screen-reader users must tab through the entire header on every page→ Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
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
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€2.639 /mo
+27.8pp bounce · ~2,778 lost visitors/mo
CPC: EUR 0.95
Bandwidth Waste
€2,24 /mo
30286.7 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~3.0 MB per page loadSaves €2,24/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.
5.10 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
18.80 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.00 s
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.28 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.
19.00 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
764 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.89 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
33 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.133
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.20 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.03 s
Categories
8Performance
Page weighs 13.6 MB (9.6 MB transferred)
Security
All checks pass
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 87+ on Sustainability; you're at 62 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, hosted on AWS, with AWS CloudFront CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
PayPal 
Cart Functionality 
plentyShop LTS 
plentymarkets 
Bootstrap 4.4.1
DHL 
Font Awesome HSTS 
HTTP/3 
Open Graph 
Tailwind CSS 
Vue.js 2.6.12 Vuex 3.6.2
Webpack 
core-js 3.9.0
jQuery 3.5.1
AWS CloudFront Amazon CloudFront 
AWS Amazon Web Services All Detected Technologies (23)
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 Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
The official template plugin developed by plentymarkets. plentyShop LTS is the default template for plentymarkets online stores.
plentymarkets is a cloud-based all-in-one ecommerce ERP solution.
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS and JavaScript-based design templates for typography, forms, buttons, navigation, and other interface components.
DHL is an international courier, package delivery and express mail service, which is a division of the German logistics firm Deutsche Post.
Font Awesome is a font and icon toolkit based on CSS and Less.
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.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Vuex is a state management pattern + library for Vue.js applications.
Webpack is an open-source JavaScript module bundler.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
PayPal is an online payments system that supports online money transfers and serves as an electronic alternative to traditional paper methods like checks and money orders.
Observations (5)
jQuery loaded alongside a modern framework
Both jQuery and Vue.js are loaded. Modern frameworks handle DOM manipulation natively. jQuery may be unnecessary and adds ~30KB to the page weight. Check the Performance tab for bundle analysis.
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.
Bootstrap version may be outdated
Detected Bootstrap 4.4.1. The current major version is 5. Consider updating for security patches and new features.
Vue.js version may be outdated
Detected Vue.js 2.6.12. The current major version is 3. Consider updating for security patches and new features.
Complex technology stack detected
23 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/party-schlaudt.de)<a href="https://beavercheck.com/sites/party-schlaudt.de"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.party-schlaudt.de" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.party-schlaudt.deExport & 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 (88)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Page weighs 13.6 MB (9.6 MB transferred)
- · No <main> landmark found
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 12 render-blocking <script src> tag(s) without async/defer
- · 6 `@font-face` rule(s) without `font-display` -- causes FOIT
- · 105 HTTP requests — consider bundling or reducing