Global Performance
6/6 locations ✓High global latency — average 589ms across 6 locations, fastest from Amsterdam (110ms), slowest from Singapore (1234ms). No CDN detected. Cache-Control disables caching (no-store). 3 locations above the 500ms target.
Audit overview
Compliance 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
Your mail setup has problems.
ai.studio 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)
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
Cookie 'GAESA' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
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.
Cookie 'GAESA' has no SameSite attribute
Without SameSite, cookies ride along on cross-site requests — enabling CSRF attacks that SameSite=Lax blocks for free.
Cookie 'GAESA' is missing the HttpOnly flag
Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€616 investment → €11,041/month returns + EUR 120,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 ~25%.
- Page takes 4.1s to loadUsers abandon at ~3s — you're 1.6s 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 472ms after first paint→ Defer third-party scripts and split large bundles
- 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
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
- 2 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
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
€120.500.000
- 2 non-essential cookie(s) set without consent bannerGDPR: EUR 5.000 – EUR 10.000.000
- 2 non-essential cookie(s) set without consent bannerGDPR: EUR 10.000 – EUR 20.000.000
- 2 non-essential cookie(s) set without consent bannerePrivacy Directive: EUR 5.000 – EUR 100.000.000
Bounce-Rate Cost
€8.660 /mo
+24.6pp bounce · ~2,461 lost visitors/mo
CPC: EUR 3.52
Bandwidth Waste
€0,10 /mo
1377.6 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~138 KB per page loadSaves €0,10/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.62 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.07 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
472 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.
6.62 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.
5.65 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.70 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.82 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.
3.01 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.82 s
Categories
8Performance
All checks pass
Security
'unsafe-inline' found in script source
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 Google Font API sites score 85+ on Compliance; you're at 65 — closing this gap is the highest-leverage improvement.
Technology stack
Google Cloud Load Balancing, on Node.js, hosted on Express
Stack Architecture
Google Cloud Load Balancing 
Google Font API HSTS 
HTTP/3 
Lucide 
Open Graph 
Tailwind CSS 
Node.js 
Express Google Cloud All Detected Technologies (10)
Express is a web application framework for Node.js, released as free and open-source software under the MIT License. It is designed for building web applications and APIs.
Google Cloud is a suite of cloud computing services.
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Google Cloud Load Balancing is a scalable, fully managed global load balancing service using Google Frontend.
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.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Observations (2)
No build tool detected
A framework (Google Cloud Load Balancing) 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
10 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/ai.studio)<a href="https://beavercheck.com/sites/ai.studio"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fglobal-shayari-ai.ai.studio" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fglobal-shayari-ai.ai.studioExport & 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 A (91)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Cookie 'GAESA' is missing the Secure flag
- · 1 button(s) with no accessible text
- · Cookie 'GAESA' has no SameSite attribute
- · Cookie 'GAESA' is missing the HttpOnly flag
Sprint 3: Strategic Improvements
+1Higher effort, long-term payoff
- · 'unsafe-inline' found in script source