Audit overview
Compliance needs attention; the rest of the 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
Your mail setup has problems.
sayfanicoffeehouse.com 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)
6 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.
No H1 heading found
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
177 inline style attribute(s) detected
Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.
5 `@font-face` rule(s) without `font-display` -- causes FOIT
Performance issues directly impact user engagement and conversion rates.
7 render-blocking stylesheet(s) -- recommended: <=3
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$667 investment → $8,004/month returns + USD 157,500 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
2 barrier(s) likely increasing bounce by ~19%.
- Page takes 5.0s to loadUsers abandon at ~3s — you're 2.5s 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 467ms after first paint→ Defer third-party scripts and split large bundles
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
$157,500
- No privacy policy found (page links and common paths checked)CCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no privacy policy foundCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$5,016 /mo
+18.6pp bounce · ~1,865 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.33 /mo
4141.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~414 KB per page loadSaves $0.33/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.
1.52 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.96 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
467 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.43 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.
10.03 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
693 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.51 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
121 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.24 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.
3.27 s
Categories
8Performance
5 `@font-face` rule(s) without `font-display` -- causes FOIT
Security
177 inline style attribute(s) detected
Accessibility
6 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.
Technology stack
Duda production_6900, on styled-components, hosted on Snowplow Analytics, wit...
Stack Architecture
Duda production_6900
AudioEye HSTS 
Lodash 4.18.1
MobX 
Open Graph 
PhotoSwipe 
Priority Hints 
React 
Tailwind CSS 
core-js 3.49.0
jQuery 3.7.0 jQuery Migrate 3.5.2
styled-components 5.3.11
Nginx 
Snowplow Analytics All Detected Technologies (16)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Snowplow is an open-source behavioral data management platform for businesses.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
Duda is a user-friendly website builder and CMS platform that enables businesses and individuals to create responsive, mobile-friendly websites without extensive coding knowledge.
AudioEye is an accessibility overlay which claims to provide ADA and WCAG accessibility compliance.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.
Open Graph is a protocol that is used to integrate any web page into the social graph.
PhotoSwipe is an open-source gallery to support JavaScript-based image zooming.
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.
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.
Query Migrate is a javascript library that allows you to preserve the compatibility of your jQuery code developed for versions of jQuery older than 1.9.
Observations (4)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 5.3.11'. Remove this header in production to reduce information leakage.
jQuery loaded alongside a modern framework
Both jQuery and React 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 (AudioEye) 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
16 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/sayfanicoffeehouse.com)<a href="https://beavercheck.com/sites/sayfanicoffeehouse.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sayfanicoffeehouse.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sayfanicoffeehouse.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 · 7h total → projected B (88)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · No H1 heading found
- · 6 button(s) with no accessible text
- · 7 render-blocking stylesheet(s) -- recommended: <=3
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 5 `@font-face` rule(s) without `font-display` -- causes FOIT
- · 177 inline style attribute(s) detected