Global Performance
6/6 locations ✓Acceptable global latency — average 469ms across 6 locations, fastest from Amsterdam (63ms), slowest from Sao Paulo (873ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.
Audit overview
Content needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
4High impact, low effort — start here.
Strategic
1High 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
Top Priorities (5)
1 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.
2 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.
4 image(s) missing alt attribute
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
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
€255 investment → €5,657/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 ~29%.
- Page takes 6.8s to loadUsers abandon at ~3s — you're 4.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- No Open Graph tagsLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop→ Add og:title, og:description, og:image, og:url to the page head
- No structured dataNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
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
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
- No H1 heading foundEAA: EUR 1,000 – EUR 500,000
- Heading level skipped: H2 → H4 (missing H3)EAA: EUR 1,000 – EUR 500,000
- 4 image(s) missing alt attributeEAA: EUR 1,000 – EUR 500,000
- 2 image(s) with generic alt textEAA: EUR 1,000 – EUR 500,000
Bounce-Rate Cost
€1,449 /mo
+29.0pp bounce · ~2,898 lost visitors/mo
CPC: EUR 0.50
Bandwidth Waste
€0.52 /mo
7018.9 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~702 KB per page loadSaves €0.52/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.95 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.83 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
13 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.633
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.95 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.
7.09 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
442 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.66 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.407
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
683 ms
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.68 s
Categories
8Performance
All checks pass
Security
All checks pass
Accessibility
1 button(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 Bootstrap sites score 96+ on SEO; you're at 87 — closing this gap is the highest-leverage improvement.
Technology stack
Animate.css, on Apache, hosted on Apache HTTP Server
Stack Architecture
Animate.css 
Bootstrap 3.3.7
Font Awesome HSTS 
Hugo 0.123.7
OWL Carousel 
RSS 
Ubuntu 
jQuery 3.3.1
Apache 2.4.58 Apache HTTP Server 2.4.58All Detected Technologies (11)
Apache is a free and open-source cross-platform web server software.
Animate.css is a ready-to-use library collection of CSS3 animation effects.
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.
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.
Hugo is an open-source static site generator written in Go.
OWL Carousel is an enabled jQuery plugin that lets you create responsive carousel sliders.
RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
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.
Observations (4)
Server version exposed in headers
The Server header reveals 'Apache 2.4.58'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
No build tool detected
A framework (Animate.css) 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 3.3.7. The current major version is 5. Consider updating for security patches and new features.
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/results/c5deaafb-7de1-4706-826e-35c9e4a52cdb)<a href="https://beavercheck.com/results/c5deaafb-7de1-4706-826e-35c9e4a52cdb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpop-i.de" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpop-i.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 · 3h total → projected B (87)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · No <main> landmark found
- · No H1 heading found
- · 1 button(s) with no accessible text
- · 2 link(s) with no accessible text
Sprint 2: Core Fixes
Medium effort, high structural impact
- · 4 image(s) missing alt attribute