# BeaverCheck Audit Report — https://global-shayari-ai.ai.studio

**Date:** August 21, 2026  
**URL:** https://global-shayari-ai.ai.studio  
**Overall Grade:** C (79/100)  
**Report:** https://beavercheck.com/results/68ab8151-c885-48b8-96d8-7aaabbfeaf1a

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Cookie 'GAESA' is missing the Secure flag — Security > Cookie Security
3. **[CRITICAL]** HSTS header is missing — Security > Security Headers
4. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
5. **[CRITICAL]** 5 button(s) with no accessible text — Accessibility > Link & Button Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 55 |
| Accessibility | 92 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

### Security Headers (F — 5/100)

*1 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 0/100)

*No enforcing CSP policy found*

- **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 68 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (B — 75/100)

*1 cookies analyzed, 0 checks passed*

- **[CRITICAL]** Cookie 'GAESA' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'GAESA' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'GAESA' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

### Cookie Hygiene (A+ — 100/100)

*All 1 cookie(s) pass hygiene checks*

- **[PASS]** All 1 cookie(s) pass hygiene checks

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

### security.txt (B — 70/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt: Missing required 'Contact' field
- **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116)

### Cross-Origin Tab Safety (A+ — 100/100)

*All 1 new-tab link(s) carry rel=noopener*

- **[PASS]** All 1 new-tab link(s) carry rel=noopener

### CSP Inline-Style Readiness (A+ — 100/100)

*No inline style attributes -- strict CSP is feasible*

- **[PASS]** No inline style attributes detected

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

*No CSP header -- Trusted Types check is N/A*

- **[PASS]** No CSP header found -- Trusted Types check is N/A

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/1 third-party resources)*

- **[WARNING]** SRI adoption: 0/1 third-party resources protected (0%) — Of 1 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 1 examples):
  - https://fonts.googleapis.com/css2?family=Amiri:ital,wght@0,400;0,700;1,400&family=Cinzel:wght@500;700;900&family=Gulzar&family=Hind+Siliguri:wght@400;500;600;700&family=Noto+Nastaliq+Urdu:wght@400;600;700&family=Noto+Serif+Bengali:wght@400;600;700&family=Noto+Serif+Devanagari:wght@400;600;700&family=Playfair+Display:ital,wght@0,400;0,600;0,700;1,400;1,600&family=Plus+Jakarta+Sans:wght@300;400;500;600;700;800&display=swap

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

### Source Map Exposure (C — 70/100)

*1 publicly-accessible source map(s) -- full source code leaked*

- **[WARNING]** 1 publicly-accessible JavaScript source map(s) — Source maps (.js.map files) reveal the original source code -- variable names, comments, file structure, and sometimes secrets that were stripped from the bundled output. They're shipped to production by mistake almost universally; the standard fix is a build-tool config flag (Webpack: `devtool: false` or `'hidden-source-map'`; Vite: `build.sourcemap: false`; Next.js: `productionBrowserSourceMaps: false`). Once removed, audit your CDN/edge cache to evict any previously-cached .map URLs. Sample accessible URLs: https://global-shayari-ai.ai.studio/assets/index-DjkHOdVX.js.map.

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (A+ — 100/100)

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 1 external resources have SRI*

- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[PASS]** security.txt is present — good practice
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (C — 64/100)

*1.7 MB transferred, 18 requests*

- **[INFO]** Page weighs 2.0 MB (1.7 MB transferred)
- **[WARNING]** JavaScript is 1.3 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** Fonts are 307 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[PASS]** 18 HTTP requests
- **[INFO]** Estimated 0.36 g CO2 per page load

### Third-Party Impact (A — 85/100)

*25% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 25% of page weight (444.4 KiB of 1.7 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (A+ — 100/100)

*No images on this page*

- **[PASS]** No images on this page

### JS Execution Cost (D — 40/100)

*2077ms total JS execution*

- **[WARNING]** https://global-shayari-ai.ai.studio/: 948ms CPU time
- **[WARNING]** Unattributable: 553ms CPU time
- **[WARNING]** https://global-shayari-ai.ai.studio/assets/index-D...: 504ms CPU time
- **[INFO]** https://apis.google.com/_/scs/abc-static/_/js/k=ga...: 72ms CPU time
- **[INFO]** Third-party scripts: 72ms (3% of total)

### Font Loading (A+ — 100/100)

*4 fonts (307 KB)*

- **[INFO]** 4 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (F — 10/100)

*4 scripts, 584 KB unused*

- **[WARNING]** https://global-shayari-ai.ai.studio/assets/index-D...: 584 KB unused (48%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://global-shayari-ai.ai.studio/assets/index-D...: unminified — 164 KB could be saved
- **[INFO]** Total unused JavaScript: 584 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*2 hints, 0 missing preconnects*

- **[PASS]** Page uses 2 resource hint(s)

### HTTP/3 (QUIC) (A+ — 100/100)

*HTTP/3 advertised via Alt-Svc*

- **[PASS]** HTTP/3 (QUIC) is supported — First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.

### Compression Algorithm (C — 70/100)

*Main response served uncompressed*

- **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=0 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 100/100)

*1 server-response signal(s) detected*

- **[PASS]** Both `ETag` and `Last-Modified` present -- efficient revalidation supported — The page returns both `ETag` (content hash) and `Last-Modified` (timestamp) headers. Browsers can issue conditional GETs with `If-None-Match` or `If-Modified-Since`; the server returns 304 Not Modified for unchanged content, saving bandwidth. ETag is the more reliable of the two (timestamps fail in DST transitions and clock skew).

### Page Weight Inventory (D — 45/100)

*18 resources · 1.7 MB · 584 KB savings available*

- **[WARNING]** Page weight 1.7 MB exceeds 1 MB target by 737 KB
- **[INFO]** ~584 KB of savings available
- **[INFO]** 14 third-party resources (25% of weight)
- **[INFO]** 2 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (A+ — 100/100)

*No render-blocking JS or document.write usage detected*

- **[PASS]** No JavaScript blocking issues detected

### CSS Performance Depth (A+ — 100/100)

*No CSS performance depth issues detected*

- **[PASS]** No CSS performance depth issues detected

---

## Content Quality

### Links (A — 90/100)

*6 links checked, 4 healthy, 2 broken*

- **[WARNING]** 4 of 6 links are healthy
- **[WARNING]** Broken link: https://fonts.googleapis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://fonts.gstatic.com — Found in <link href>. Returns HTTP 404.

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (B — 80/100)

*Open Graph tags are partially configured — some improvements recommended.*

- **[WARNING]** Missing og:image — The og:image tag provides a preview image for social sharing.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.

### Open Graph / Twitter Card Depth (A — 95/100)

*1 OG/Twitter depth issue(s) detected*

- **[INFO]** 1 Twitter Card field(s) differ from Open Graph counterparts — Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches:
  - description: twitter="Multilingual AI poetry companion to tran...", og="Understand classical and contemporary Ur..."

Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.

### Structured Data (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

### Image Optimization (A+ — 100/100)

*No images to analyze*


### Autoplay Media (A+ — 100/100)

*No autoplay media on the page*

- **[PASS]** No autoplay media on the page

---

## Infrastructure

### DNS Records (A — 90/100)

*8 A records, 30 ms lookup*

- **[PASS]** Resolves to 8 IPv4 address(es)
- **[PASS]** Has 8 IPv6 (AAAA) record(s)
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 30 ms

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** No CNAME record present

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (C — 60/100)

*0/16 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 34.143.74.2: lookup 34.143.74.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.77.2: lookup 34.143.77.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.72.2: lookup 34.143.72.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.78.2: lookup 34.143.78.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.73.2: lookup 34.143.73.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.79.2: lookup 34.143.79.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.75.2: lookup 34.143.75.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 34.143.76.2: lookup 34.143.76.2: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4244:200::: lookup 2600:1900:4244:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4245:200::: lookup 2600:1900:4245:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4241:200::: lookup 2600:1900:4241:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1901:81d4:200::: lookup 2600:1901:81d4:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4242:200::: lookup 2600:1900:4242:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1901:81d5:200::: lookup 2600:1901:81d5:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4240:200::: lookup 2600:1900:4240:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 2600:1900:4243:200::: lookup 2600:1900:4243:200::: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (A+ — 100/100)

*Mean 24ms across 3 resolvers (spread 7ms)*

- **[PASS]** Google: 22ms
- **[PASS]** Cloudflare: 23ms
- **[PASS]** Quad9: 29ms

### Redirect Chain (A+ — 100/100)

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (F — 30/100)

*IPv6 records exist but unreachable*

- **[WARNING]** IPv6 DNS records exist but server is not reachable — Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
- **[INFO]** IPv6 connection error

### Crawlability (B — 70/100)

*robots.txt present, sitemap with 0 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[WARNING]** sitemap.xml contains invalid XML — Search engines may not be able to parse the sitemap. Fix XML validation errors.
- **[WARNING]** sitemap.xml is empty — no URLs found — An empty sitemap provides no value. Add <url> entries for your pages.
- **[PASS]** robots.txt references sitemap

### URL Variants (A — 90/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[WARNING]** HTTP→HTTPS redirect is not permanent

### Domain Intelligence (A+ — 100/100)

*ai.studio — via MarkMonitor Inc., 2 years, 11 months old*

- **[PASS]** Domain registered until Sep 21, 2029 (3 years, 1 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: MarkMonitor Inc.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (C — 60/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — A privacy policy page is recommended for transparency and may be legally required.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[CRITICAL]** 1 non-essential cookie(s) set without consent banner — Unrecognized (treated as non-essential): GAESA
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (A+ — 100/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y.

### GDPR Article 13 Disclosures (F — 25/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

### Third-Party Trackers (A+ — 100/100)

*No third-party trackers detected*

- **[PASS]** No third-party trackers detected

### Cookie & Tracker Inventory (A+ — 100/100)

*1 cookies · 0 trackers · 0 pre-consent*

- **[INFO]** 1 cookie(s) could not be classified

### Tracking Pixel Inventory (A+ — 100/100)

*No image data to inspect for tracking pixels*

- **[PASS]** No image data to inspect for tracking pixels

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No SameSite=None cookies -- no cross-site travel surface*

- **[PASS]** No cookies opted in to cross-site travel (SameSite=None)

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 0/100)

*0 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** HIPAA indicators detected (weak confidence) — Indicators suggesting HIPAA may be relevant: Text mentions: phi. Health Insurance Portability and Accountability Act — protects sensitive patient health information.

### Third-Party Data Sharing

*0 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## Availability

### CDN & Delivery (D — 50/100)

*No CDN detected*

- **[WARNING]** No CDN detected — A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (B — 80/100)

*private, max-age=0*

- **[PASS]** Cache-Control header is set
- **[PASS]** ETag present — enables conditional (304) responses
- **[PASS]** Last-Modified header present

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (A — 85/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (A+ — 100/100)

*Health endpoint at https://global-shayari-ai.ai.studio/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://global-shayari-ai.ai.studio/health

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Landmark Structure (A — 85/100)

*4 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 1 <nav> landmark(s) found
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (A — 85/100)

*7 headings, 1 skip(s)*

- **[PASS]** Single H1 present
- **[WARNING]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

### Heading Text Quality (A+ — 100/100)

*All 7 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (A+ — 100/100)

*No images*

- **[PASS]** No images on this page

### Form Accessibility (A — 92/100)

*1 of 2 controls have issues*

- **[WARNING]** 1 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 1 control(s) properly labeled

### Link & Button Quality (B — 77/100)

*5 issue(s) across 1 links and 62 buttons*

- **[WARNING]** 1 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 5 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.

### Form Input Types (A+ — 100/100)

*2 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (A+ — 100/100)

*2 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "en"*

- **[PASS]** <html lang="en"> is set and valid

### Tabindex Anti-Patterns (A+ — 100/100)

*No explicit tabindex attributes found*

- **[PASS]** No explicit tabindex attributes found

### Iframe Accessibility (A+ — 100/100)

*No iframes on this page*

- **[PASS]** No iframes on this page

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (C — 75/100)

*72% of visible text renders at >= 12 CSS px (41 below threshold)*

- **[WARNING]** 41 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 9.0px ("PRO"); <span> 11.0px ("Day"); <span> 11.0px ("Translate to:"); <span> 11.0px ("Instant full breakdown"); <span> 10.0px ("Urdu").

---

## UX

### 404 Error Page (F — 20/100)

*Soft 404 detected*

- **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

### Favicon & Branding (F — 15/100)

*1 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

### Web Manifest (F — 30/100)

*Invalid JSON*

- **[WARNING]** Manifest contains invalid JSON — Manifest at https://global-shayari-ai.ai.studio/manifest.json contains invalid JSON. Browsers cannot parse it.

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (D — 45/100)

*Theme color only*

- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (F — 20/100)

*No navigation patterns*

- **[PASS]** 1 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)
- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

### Mobile UX Depth (A+ — 100/100)

*1 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

---

## SEO

### Canonical URL (B — 80/100)

*Minor issues*

- **[WARNING]** No canonical tag found — Search engines will determine the canonical URL themselves, which may cause duplicate content issues.

### Meta Tags (A+ — 95/100)

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (42 chars) is optimal
- **[INFO]** Meta description is 204 characters — truncated on mobile (~160 char limit)
- **[PASS]** Title and H1 are well-aligned

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

### Content Depth (B — 80/100)

*799 words, Very Difficult*

- **[PASS]** Page has 799 words of content
- **[INFO]** Reading level: Very Difficult (grade 17)

### Internal Links (B — 70/100)

*0 internal, 1 external*

- **[WARNING]** No internal links found — Internal links help search engines discover and rank your other pages.
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 0 internal / 1 external links
- **[WARNING]** Dead-end page — no outgoing internal links

### Image SEO (A+ — 100/100)

*No images*

- **[PASS]** No images on this page

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (C — 70/100)

*Sitemap exists but no <lastmod> entries*

- **[INFO]** Sitemap has no <lastmod> entries — Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts detected*

- **[PASS]** Sitemap URLs are not blocked by robots.txt

### Sitemap Hygiene (B — 75/100)

*1 hygiene issue(s) on a 0-URL sitemap*

- **[WARNING]** Sitemap is empty -- 0 URLs listed — The sitemap file is reachable and parses as valid XML, but contains no `<url>` entries. Common causes: a templated sitemap that didn't iterate the URL set during build, a static placeholder shipped to production, or a CMS that lost its URL index. Search engines fetch and discard empty sitemaps.

### Markup Quality (A+ — 100/100)

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

### CO2 Per Page Load (A — 85/100)

*0.49g CO2 per view*

- **[PASS]** 0.49g CO2 per page view — This page transfers 1.7 MB, producing an estimated 0.49g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.09g, network 0.08g, end-user device 0.31g.
- **[INFO]** At 10,000 monthly views: 58.5 kg CO2/year — With 10,000 page views per month, this page would generate approximately 58.5 kg of CO2 annually — equivalent to charging 7307 smartphones.

### Green Hosting (D — 40/100)

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 3 KB (vs 1761 KB first visit). 16 of 18 resources are served from browser cache, saving 0.49g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.49g)

### Carbon Budget (B — 70/100)

*38th percentile*

- **[PASS]** 0.49g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 62% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 38th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (C — 60/100)

*67% efficient*

- **[WARNING]** Transfer efficiency: 67% — An estimated 584 KB (33%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 584 KB of unused JavaScript. This wasted data produces 0.16g of unnecessary CO2 per page view.

### Web Font Weight Variants (C — 70/100)

*28 font weights loaded across 9 famil(y/ies)*

- **[WARNING]** 28 font weights loaded -- likely 100+ KB of unused payload — Loading 28 font weights typically transfers 200-400 KB just for fonts. Most pages legitimately use 2-3 weights (regular + bold, maybe medium). Audit which weights your stylesheet actually applies and trim the Google Fonts URL accordingly. Affected families: Amiri, Cinzel, Gulzar, Hind Siliguri, Noto Nastaliq Urdu, Noto Serif Bengali, Noto Serif Devanagari, Playfair Display, Plus Jakarta Sans.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/68ab8151-c885-48b8-96d8-7aaabbfeaf1a*