Global Performance
6/6 locations ✓Strong global performance — average 131ms across 6 locations, fastest from Sao Paulo (42ms), slowest from Singapore (254ms). GitHub Pages edge cache (HIT).
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.
mohammed0912474-source.github.io 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
Page body has only 87 chars of text -- likely empty / placeholder
Security gaps expose your site and users to attacks, eroding trust.
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.
32 third-party resources (68% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
6 render-blocking <script src> tag(s) without async/defer
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
$567 investment → $11,766/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
8 barrier(s) likely increasing bounce by ~31%.
- Page takes 4.7s to loadUsers abandon at ~3s — you're 2.2s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 2.9sClicks 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
- 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, …)
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
- Privacy Policy not detectedCCPA/CPRA: USD 2,500 – USD 7,500
- No <main> landmark foundADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$8,391 /mo
+31.2pp bounce · ~3,119 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.13 /mo
1596.5 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~160 KB per page loadSaves $0.13/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 3 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.
3.10 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.72 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.85 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.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.
6.75 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
725 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
964 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
522 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.
3.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.
1.66 s
Categories
8Performance
32 third-party resources (68% of weight)
Security
Content-Security-Policy header is missing
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 Google Font API sites score 97+ on SEO; you're at 85 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 87+ on Compliance; you're at 69 — closing this gap is the highest-leverage improvement.
Technology stack
Google Font API, on Firebase, hosted on GitHub Pages, with Fastly CDN
Stack Architecture
Google Font API HSTS 
PWA 
Priority Hints 
Varnish 
Firebase 10.14.1
Fastly 
jsDelivr 
GitHub Pages All Detected Technologies (9)
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
JSDelivr is a free public CDN for open-source projects. It can serve web files directly from the npm registry and GitHub repositories without any configuration.
GitHub Pages is a static site hosting service.
Firebase is a Google-backed application development software that enables developers to develop iOS, Android and Web apps.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Progressive Web Apps (PWAs) are web apps built and enhanced with modern APIs to deliver enhanced capabilities, reliability, and installability while reaching anyone, anywhere, on any device, all with a single codebase.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Varnish is a reverse caching proxy.
Observations (4)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'Firebase 10.14.1'. Remove this header in production to reduce information leakage.
Hosted on GitHub Pages
GitHub Pages provides free static hosting with automatic HTTPS. Limitations: no server-side code, 1GB site size limit, 100GB/month bandwidth.
No build tool detected
A framework (Google Font API) 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
9 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/mohammed0912474-source.github.io)<a href="https://beavercheck.com/sites/mohammed0912474-source.github.io"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmohammed0912474-source.github.io%2Fqa-supply-chain-app%2F" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmohammed0912474-source.github.io%2Fqa-supply-chain-app%2FExport & 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 · 6h total → projected A (90)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · No <main> landmark found
- · Page body has only 87 chars of text -- likely empty / placeholder
- · 32 third-party resources (68% of weight)
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · 6 render-blocking <script src> tag(s) without async/defer