Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
5High impact, low effort — start here.
Strategic
0High impact, requires investment.
Nothing in this quadrant — good news.
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)
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
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.
5 image-only link(s) without alt text
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
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.
63 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
€120 investment → €9,072/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 ~28%.
- Page takes 4.9s to loadUsers abandon at ~3s — you're 2.4s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 40 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
- 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
- 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
- 5 image-only link(s) without alt textEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€6.057 /mo
+27.5pp bounce · ~2,753 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,17 /mo
2279.7 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~228 KB per page loadSaves €0,17/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.
2.18 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.89 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
117 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.
2.18 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.16 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
886 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.24 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.033
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
942 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.25 s
Categories
8Performance
63 third-party resources (100% of weight)
Security
HSTS header is missing
Accessibility
2 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 WordPress sites score 97+ on SEO; you're at 84 — closing this gap is the highest-leverage improvement.
Technology stack
Prismic, on PHP, hosted on Next.js, with Cloudflare CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
Prismic 
WordPress 
MySQL 
Open Graph 
Priority Hints 
React 
Tailwind CSS 
Webpack 
PHP 8.2.30
Cloudflare 
Next.js 14.0.3 Next.js App Router All Detected Technologies (14)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Next.js is a React framework for developing single page Javascript applications.
The Next.js App Router is a new paradigm for building applications using React's latest features.
PHP is a general-purpose scripting language used for web development.
Prismic is a headless CMS for Jamstack.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
MySQL is an open-source relational database management system.
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.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
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 (4)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'PHP 8.2.30'. Remove this header in production to reduce information leakage.
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 (MySQL) 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
14 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/01b2dc27-738f-4fca-a265-874c6b9b8081)<a href="https://beavercheck.com/results/01b2dc27-738f-4fca-a265-874c6b9b8081"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjquery.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fjquery.orgExport & 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
1 sprints · 1h total → projected B (87)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · No <main> landmark found
- · HSTS header is missing
- · 2 link(s) with no accessible text
- · 5 image-only link(s) without alt text
- · 63 third-party resources (100% of weight)