# BeaverCheck Audit Report — https://tournamayeshgah.com **Date:** August 18, 2026 **URL:** https://tournamayeshgah.com **Overall Grade:** C (76/100) **Report:** https://beavercheck.com/results/82a3171b-0d28-40ba-ac49-87109bbd6476 ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy 3. **[WARNING]** 16 inline style attribute(s) detected — Security > CSP Inline-Style Readiness 4. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers 5. **[WARNING]** Cross-Origin-Opener-Policy header is missing — Security > Security Headers --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 70 | | Accessibility | 72 | | Best Practices | 100 | | SEO | 77 | --- ## Security ### Security Headers (F — 20/100) *1 of 10 headers properly configured* - **[WARNING]** HSTS is missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP. - **[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, 7 checks passed* - **[PASS]** TLS 1.3 is used - **[PASS]** Strong cipher suite is used - **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance. - **[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 198 days) - **[PASS]** Certificate chain has 4 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 2 domain(s) - **[PASS]** Certificate is issued by a trusted CA ### Cookie Security (A+ — 100/100) *No cookies set — no cookie security risks* - **[PASS]** No cookies set — no cookie security risks ### Cookie Hygiene (A+ — 100/100) *No cookies set -- cookie-hygiene check is N/A* - **[PASS]** No cookies set ### 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 (C — 60/100) *No security.txt file found* - **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field. ### CSP Inline-Style Readiness (C — 75/100) *16 inline style attribute(s) detected* - **[WARNING]** 16 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 16 inline style(s) is moderate. Affected element types include: body, img, button, div, p. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win. ### 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 ### 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. ### 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 (A+ — 100/100) *No external resources* - **[PASS]** No external resources to protect ### JS Library Vulnerabilities (A+ — 100/100) *No known vulnerabilities* - **[PASS]** No known JavaScript library vulnerabilities detected ### Information Leakage (A+ — 100/100) *No exposures* - **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt. - **[PASS]** No sensitive files exposed ### Email Security (C — 57/100) *DMARC: quarantine, SPF: -all* - **[PASS]** DMARC policy is quarantine — good protection - **[INFO]** DMARC configured without rua= aggregate reporting — Without rua=, you have no visibility into spoof attempts or auth failures from your own legitimate senders. Add rua=mailto:dmarc@ (or a managed inbox at a reporting service). - **[PASS]** SPF ends in -all (hard fail) — strongest setting - **[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. and a policy file at https://mta-sts./.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.. - **[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 (B — 72/100) *1.5 MB transferred, 43 requests* - **[PASS]** Page weighs 2.6 MB (1.5 MB transferred) - **[INFO]** Fonts are 264 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks. - **[PASS]** 43 HTTP requests - **[INFO]** Estimated 0.30 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *10% third-party, 0 ms blocking* - **[INFO]** Third-party code accounts for 10% of page weight (150.4 KiB of 1.5 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 (C — 65/100) *18 images, 0 KB saveable* - **[WARNING]** https://tournamayeshgah.com/Content/images/yellow-... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. - **[WARNING]** https://tournamayeshgah.com/css/WhatsApp-logo.svg is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. ### JS Execution Cost (F — 20/100) *6863ms total JS execution* - **[WARNING]** https://tournamayeshgah.com/: 5224ms CPU time - **[WARNING]** https://tournamayeshgah.com/js/home-modern.js?v=10...: 648ms CPU time - **[WARNING]** Unattributable: 635ms CPU time - **[INFO]** https://tournamayeshgah.com/js/jquery.min.js?v=10A...: 243ms CPU time - **[INFO]** https://www.googletagmanager.com/gtag/js?id=UA-102...: 114ms CPU time - **[INFO]** Third-party scripts: 114ms (2% of total) ### Font Loading (A+ — 100/100) *4 fonts (264 KB)* - **[INFO]** 4 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (B — 80/100) *8 scripts, 67 KB unused* - **[WARNING]** https://www.googletagmanager.com/gtag/js?id=UA-102...: 67 KB unused (52%) — Consider code splitting or tree shaking to reduce unused code. - **[INFO]** Total unused JavaScript: 67 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) *No optimization needed* - **[PASS]** No resource hint issues ### HTTP/3 (QUIC) (B — 75/100) *HTTP/3 not advertised* - **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads. ### Compression Algorithm (A+ — 100/100) *Main response uses brotli* - **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it. ### 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 (B — 80/100) *No Cache-Control header on main HTML response* - **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift. ### Server-Timing Observability (A+ — 100/100) *1 Server-Timing entries advertised* - **[PASS]** Server-Timing header advertises 1 timing entries ### Server Response Intelligence (A+ — 95/100) *2 server-response signal(s) detected* - **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class). - **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: ""` (or `Last-Modified: `) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth. ### Page Weight Inventory (C — 60/100) *43 resources · 1.5 MB · 67 KB savings available* - **[WARNING]** Page weight 1.5 MB exceeds 1 MB target by 465 KB - **[INFO]** ~67 KB of savings available - **[INFO]** 3 third-party resources (10% of weight) --- ## Infrastructure ### DNS Records (A+ — 100/100) *2 A records, 53 ms lookup* - **[PASS]** Resolves to 2 IPv4 address(es) - **[INFO]** No IPv6 (AAAA) records - **[PASS]** 2 nameserver(s) configured - **[PASS]** 1 mail exchanger(s) configured - **[PASS]** SPF record present in TXT - **[PASS]** DNS resolution time: 53 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 (B — 75/100) *0/2 IPs match cert SAN* - **[INFO]** PTR for 185.226.142.42 does not match any cert SAN: 185-226-142-42.cdn-by.mizbancloud.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree. - **[INFO]** PTR for 185.226.140.40 does not match any cert SAN: 185-226-140-40.cdn-by.mizbancloud.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree. ### Multi-Resolver DNS Speed (A+ — 100/100) *Mean 39ms across 3 resolvers (spread 36ms)* - **[PASS]** Google: 20ms - **[PASS]** Quad9: 41ms - **[PASS]** Cloudflare: 56ms ### Redirect Chain (A+ — 100/100) *No redirects — direct access* - **[PASS]** No redirects — direct access ### IPv6 Readiness (C — 60/100) *No IPv6 support* - **[INFO]** No IPv6 (AAAA) records found — IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity. ### Crawlability (A+ — 95/100) *robots.txt present, sitemap with 298 URLs* - **[PASS]** robots.txt is present - **[PASS]** sitemap.xml is present - **[PASS]** sitemap.xml is valid XML - **[PASS]** sitemap.xml contains 298 entries - **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap. ### URL Variants (D — 50/100) *www/non-www, trailing slash, HTTP→HTTPS* - **[CRITICAL]** Both www and non-www versions serve content - **[CRITICAL]** HTTP version does not redirect to HTTPS ### Domain Intelligence (A+ — 100/100) *tournamayeshgah.com — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 12 years, 4 months old, hosted on SABA-HOST - Saba Abr Mizban LLC, IR* - **[PASS]** Domain registered until Jun 14, 2027 (10 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: CSL Computer Service Langenbach GmbH d/b/a joker.com - **[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. - **[PASS]** Hosting: SABA-HOST - Saba Abr Mizban LLC, IR --- ## Compliance ### WCAG Compliance (A+ — 100/100) *No testable criteria* ### Cookie Consent & Privacy (B — 80/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 - **[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 script URLs to scan -- tracker inventory is N/A* - **[PASS]** No script URLs to scan -- tracker inventory is N/A ### Language & i18n (A — 90/100) *Lang attribute present* - **[PASS]** attribute is present - **[PASS]** value is valid - **[INFO]** No Content-Language HTTP header - **[INFO]** Language signals are inconsistent — The 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 HTML captured -- i18n extras check is N/A* - **[PASS]** No HTML captured -- i18n extras check is N/A ### Readability & Typography (A+ — 100/100) *Font sizes and tap targets checked* ### Viewport Configuration (F — 30/100) *No viewport meta tag* - **[CRITICAL]** No viewport meta tag found — Without a viewport meta tag, the page will not render correctly on mobile devices. ### 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: . 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 (C — 55/100) *1 trackers detected* - **[INFO]** 1 third-party trackers detected — Found 1 analytics, 0 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers. - **[WARNING]** Trackers detected but no cookie policy found — This page loads 1 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies. - **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers. ### Cookie & Tracker Inventory (A+ — 100/100) *0 cookies · 1 trackers · 0 pre-consent* - **[INFO]** 1 third-party tracker(s) detected on page ### 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 cookies on the page* - **[PASS]** No cookies set on the page response ### Beacon Tracking (sendBeacon) (A+ — 100/100) *No HTML captured -- beacon-tracking check is N/A* - **[PASS]** No HTML captured -- beacon-tracking check is N/A --- ## 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 (F — 30/100) *No cache headers* - **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers. ### 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 — 90/100) *HTTP/3, HSTS, and TLS version analysis* - **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it. - **[PASS]** HSTS enabled (base policy) - **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain. - **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT) ### Health Check Endpoint (B — 80/100) *No conventional health endpoint found* - **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404. ### 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 ### Tap Target Adequacy (C — 75/100) *7 tap target(s) too small or too close together* - **[WARNING]** 7 tap target(s) too small or too close to neighbors — WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel. ### Mobile-Readable Font Sizes (A+ — 100/100) *Font-size measurement not available for this scan* - **[PASS]** Font-size measurement not available for this scan --- ## UX ### 404 Error Page (C — 55/100) *HTTP 404, custom page* - **[PASS]** Correct 404 status code returned - **[PASS]** Custom styled 404 page ### 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 . ### Web Manifest (D — 40/100) *Not found* - **[INFO]** No web manifest found — No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display. ### PWA Depth (A+ — 100/100) *No PWA depth issues detected* - **[PASS]** No PWA depth issues detected ### Dark Mode Support (D — 40/100) *No dark mode signals* - **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and . - **[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 — 0/100) *No navigation patterns* - **[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) *No HTML captured -- mobile-depth check is N/A* - **[PASS]** No HTML captured -- mobile-depth check is N/A --- ## SEO ### SEO Audit Unavailable *Content probe data missing -- see finding for details* - **[INFO]** SEO checks could not run for this scan — Content probe data is missing for this scan -- SEO checks need the rendered DOM (canonical tag, meta description, hreflang, etc.). Common causes: bot-detection block (Akamai/Cloudflare/Imperva served the worker a challenge instead of the page), worker timeout, or the site redirected to an unrelated host. --- ## Sustainability ### CO2 Per Page Load (A — 85/100) *0.41g CO2 per view* - **[PASS]** 0.41g CO2 per page view — This page transfers 1.5 MB, producing an estimated 0.41g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.08g, network 0.07g, end-user device 0.26g. - **[INFO]** At 10,000 monthly views: 49.4 kg CO2/year — With 10,000 page views per month, this page would generate approximately 49.4 kg of CO2 annually — equivalent to charging 6176 smartphones. ### Green Hosting (D — 50/100) *Unknown* - **[INFO]** Hosting provider could not be identified — Without knowing the provider, we cannot determine their energy sourcing. Check with your hosting provider about their renewable energy commitments. - **[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) *99% cached* - **[PASS]** 99% reduction on repeat visits — Returning visitors download only 20 KB (vs 1488 KB first visit). 42 of 43 resources are served from browser cache, saving 0.41g CO2 per repeat visit. - **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.41g) ### Carbon Budget (B — 70/100) *31th percentile* - **[PASS]** 0.41g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 69% of websites analyzed. This page meets the Web Sustainability Guidelines target. - **[INFO]** Estimated 31th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view. ### Transfer Efficiency (A+ — 100/100) *95% efficient* - **[PASS]** Transfer efficiency: 95% — Only 67 KB of potential savings identified. Your page is well-optimized for size. --- --- *Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/82a3171b-0d28-40ba-ac49-87109bbd6476*