Audit overview
Security and Accessibility need attention; the other 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
Top Priorities (5)
29 image-in-link without alt text
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
3 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.
31 image-only link(s) without alt text
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
34 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.
Cross-Origin-Embedder-Policy header is missing
COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€340 investment → €4,964/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
5 barrier(s) likely increasing bounce by ~23%.
- Page takes 16.7s to loadUsers abandon at ~3s — you're 14.2s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- High main-thread blocking timePage is non-interactive for 200ms after first paint→ Defer third-party scripts and split large bundles
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
- 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, …)
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
- Heading level skipped: H1 → H4 (missing H2)EAA: EUR 1.000 – EUR 500.000
- 34 image(s) missing alt attributeEAA: EUR 1.000 – EUR 500.000
- 29 image-in-link without alt textEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€4.963 /mo
+22.6pp bounce · ~2,256 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,60 /mo
8143.6 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~814 KB per page loadSaves €0,60/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 4 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.
7.32 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.70 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
200 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.
7.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.
16.86 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
980 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.01 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.08 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.02 s
Categories
8Performance
All checks pass
Security
Cross-Origin-Embedder-Policy header is missing
Accessibility
29 image-in-link without alt 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 Cloudflare sites score 73+ on Accessibility; you're at 60 — closing this gap is the highest-leverage improvement.
Top 10% of Facebook sites score 95+ on SEO; you're at 90 — closing this gap is the highest-leverage improvement.
Technology stack
Cloudflare, on Ruby, hosted on Heroku, with Fastly CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
Cloudflare Facebook Google Search Console Google Workspace HSTS 
Honeybadger 
InstantClick 
Open Graph 
RSS 
React 
Ruby on Rails 
Tailwind CSS 
Varnish 
YouTube 
Ruby 
Fastly 
Heroku All Detected Technologies (20)
Ruby is an open-source object-oriented programming language.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Honeybadger provides exception and uptime monitoring to keep your web apps error-free.
InstantClick is a JavaScript library that speeds up your website, making navigation faster.
Open Graph is a protocol that is used to integrate any web page into the social graph.
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.
React is an open-source JavaScript library for building user interfaces or UI components.
Ruby on Rails is a server-side web application framework written in Ruby under the MIT License.
Varnish is a reverse caching proxy.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
Ahoy is a Ruby gem that provides simple and powerful analytics for Ruby on Rails applications.
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.
Observations (2)
No build tool detected
A framework (Cloudflare) 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
20 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/1dab06f6-8d65-4e53-a4db-9f9b461535fa)<a href="https://beavercheck.com/results/1dab06f6-8d65-4e53-a4db-9f9b461535fa"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdev.to" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fdev.toExport & 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 · 4h total → projected B (82)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · 29 image-in-link without alt text
- · 3 link(s) with no accessible text
- · 31 image-only link(s) without alt text
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 34 image(s) missing alt attribute
- · Cross-Origin-Embedder-Policy header is missing