# BeaverCheck Audit Report — https://cloudatlasinc.com

**Date:** September 20, 2026  
**URL:** https://cloudatlasinc.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/71b35f5e-ca15-483e-a178-9ad39c8ef1b1

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Page weighs 6.8 MB (5.1 MB transferred) — Performance > Page Weight Budget
3. **[CRITICAL]** 10 control(s) without accessible label — Accessibility > Form Accessibility
4. **[CRITICAL]** No <main> landmark found — Accessibility > Landmark Structure
5. **[WARNING]** 1 `@font-face` rule(s) without `font-display` -- causes FOIT — Performance > CSS Performance Depth

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 39 |
| Accessibility | 88 |
| Best Practices | 96 |
| SEO | 85 |

---

## Security

### Security Headers (C — 65/100)

*6 of 10 headers properly configured*

- **[PASS]** HSTS is enabled with preload
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[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, 9 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[PASS]** OCSP stapling enabled
- **[PASS]** Certificate is valid (expires in 33 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 6 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.

### Cross-Origin Tab Safety (D — 60/100)

*9 of 11 new-tab link(s) missing rel=noopener*

- **[WARNING]** 9 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

### CSP Inline-Style Readiness (D — 60/100)

*51 inline style attribute(s) detected*

- **[WARNING]** 51 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. 51 inline style(s) is high. Affected element types include: div, p, img, a, h4. 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

### 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/8 third-party resources)*

- **[WARNING]** SRI adoption: 0/8 third-party resources protected (0%) — Of 8 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 5 examples):
  - https://snap.licdn.com/li.lms-analytics/insight.min.js
  - https://www.google-analytics.com/analytics.js
  - https://www.gstatic.com/_/translate_http/_/ss/k=translate_http.tr.U15Ng4brvgw.R.W.O/am=BECAAQ/d=0/rs=AN8SPfo8A9OReyPR1DPnt-6UVhswhHJk_w/m=el_main_css
  - https://translate.googleapis.com/_/translate_http/_/js/k=translate_http.tr.fa.LDBZWYATitk.O/am=BECAAQ/d=1/ed=1/rs=AN8SPfoJIifaTibIK0xMwZfY1fGfRNRnjA/m=el_main
  - https://fonts.googleapis.com/css?family=Quicksand:400

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 (B — 70/100)

*60% high-risk feature coverage (6/10)*

- **[INFO]** Permissions-Policy covers 6/10 high-risk features (60%) — The Permissions-Policy header explicitly declares policies for 6/10 high-risk features.

Covered: camera, microphone, geolocation, midi, gyroscope, magnetometer

Not declared (default-allow): payment, usb, serial, accelerometer

The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

### Referrer-Policy Strictness (A+ — 100/100)

*Referrer-Policy is `strict-origin` (strict -- only origin sent, never on HTTPS-to-HTTP downgrade)*

- **[PASS]** Referrer-Policy: `strict-origin` -- strict -- only origin sent, never on HTTPS-to-HTTP downgrade — Sends only the origin (no path / query) on cross-origin requests, and sends nothing at all on HTTPS-to-HTTP downgrade. Privacy-safe; explicit and conservative.

### Source Map Exposure (A+ — 100/100)

*No source maps accessible (probed 10 candidate URL(s))*

- **[PASS]** No source maps accessible across 10 probed candidate(s)

### 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 8 external resources have SRI*

- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.google-analytics.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from translate.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from translate.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.zdassets.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*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[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 (A+ — 95/100)

*8 directives, 2 missing*

- **[PASS]** geolocation=() — blocked for all origins
- **[PASS]** midi=() — blocked for all origins
- **[PASS]** sync-xhr=() — blocked for all origins
- **[PASS]** microphone=() — blocked for all origins
- **[PASS]** camera=() — blocked for all origins
- **[PASS]** magnetometer=() — blocked for all origins
- **[PASS]** gyroscope=() — blocked for all origins
- **[INFO]** fullscreen=(self)
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (F — 0/100)

*5.1 MB transferred, 86 requests*

- **[CRITICAL]** Page weighs 6.8 MB (5.1 MB transferred)
- **[INFO]** Fonts are 2.8 MB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** Images are 1.7 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 606 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** 86 HTTP requests
- **[INFO]** Estimated 1.1 g CO2 per page load

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

*11% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 11% of page weight (552.2 KiB of 5.1 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 — 60/100)

*50 images, 0 KB saveable*

- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/uploads/2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (F — 20/100)

*3863ms total JS execution*

- **[WARNING]** https://www.cloudatlasinc.com/: 1776ms CPU time
- **[WARNING]** Unattributable: 621ms CPU time
- **[WARNING]** https://www.cloudatlasinc.com/wp-content/themes/on...: 408ms CPU time
- **[WARNING]** https://static.zdassets.com/web_widget/classic/lat...: 382ms CPU time
- **[INFO]** https://translate.googleapis.com/_/translate_http/...: 198ms CPU time
- **[INFO]** Third-party scripts: 1057ms (27% of total)

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

*4 fonts (2818 KB)*

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

### JS Bundles (C — 60/100)

*17 scripts, 281 KB unused*

- **[WARNING]** https://static.zdassets.com/web_widget/classic/lat...: 126 KB unused (91%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://static.zdassets.com/web_widget/classic/lat...: 96 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://translate.googleapis.com/_/translate_http/...: 59 KB unused (60%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 281 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.

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

*Document 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.

### Asset Compression (D — 50/100)

*2 of 2 asset hosts serve text uncompressed*

- **[WARNING]** fonts.googleapis.com serves text assets uncompressed (assets: 4) — The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
- **[WARNING]** www.gstatic.com serves text assets uncompressed (assets: 3) — The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.

### 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 (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 — 87/100)

*2 server-response signal(s) detected*

- **[WARNING]** Compressed response missing `Vary` header — The page is served with `Content-Encoding: br` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.
- **[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: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (C — 55/100)

*86 resources · 5.1 MB · 281 KB savings available*

- **[WARNING]** Page weight 5.1 MB exceeds 1 MB target by 4.1 MB
- **[INFO]** ~281 KB of savings available
- **[INFO]** 21 third-party resources (11% of weight)
- **[INFO]** 6 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 (B — 70/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 8 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
- **[WARNING]** Total JS execution time is 3.9 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

### CSS Performance Depth (B — 78/100)

*2 CSS depth issue(s) detected*

- **[WARNING]** 9 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.
- **[WARNING]** 1 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright.

---

## Content Quality

### Links (A — 90/100)

*109 links checked, 107 healthy, 2 broken*

- **[WARNING]** 107 of 109 links are healthy
- **[WARNING]** Broken link: https://www.cloudatlasinc.com/xmlrpc.php — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: about:blank — Found in <iframe src>. Get "about:blank": unsupported protocol scheme "about"

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

*1 HTTP resource(s) loaded on HTTPS page*

- **[CRITICAL]** HTTP link loaded on HTTPS page — Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

### Open Graph (A+ — 100/100)

*Open Graph tags are well configured for social sharing.*


### 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:
  - title: twitter="Azure Cloud Migration Tools & Management...", og="Azure Cloud Migration Assessment Tools -..."

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

### Structured Data (A+ — 100/100)

*2 JSON-LD block(s) found — structured data is well configured.*

- **[INFO]** Missing recommended property "description" for WebSite — Adding "description" can improve how search engines display your content.
- **[PASS]** 2 JSON-LD blocks found

### Rich Results Eligibility (A+ — 100/100)

*2 JSON-LD block(s) declaring 2 schema type(s)*

- **[PASS]** SiteLinks Search Box markup detected — The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
- **[PASS]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

Organization, WebSite

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (F — 35/100)

*5 issues found across 51 images*

- **[WARNING]** 17 images significantly larger than display size — Resizing to display dimensions could save approximately 918 KB.
- **[WARNING]** 49 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 25 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 39 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[WARNING]** Total image weight: 1854 KB (1.8 MB) — Consider compressing images, using modern formats, and serving appropriately sized images.

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

*No autoplay media on the page*

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

---

## Infrastructure

### DNS Records (B — 75/100)

*1 A records, 34 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[INFO]** No IPv6 (AAAA) records
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[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: 34 ms

### Subdomain Takeover (B — 80/100)

*CNAME points at managed service(s) — verify configuration*

- **[WARNING]** CNAME targets Azure App Service — verify ownership — CNAME targets Azure App Service. Azure has claim verification on custom-domain binding, but a deleted app frees its name for re-registration on the same Azure region. Confirm the Azure App Service is still deployed at this name.

### 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/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 20.119.8.33: lookup 20.119.8.33: 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 — 90/100)

*Mean 58ms across 3 resolvers (spread 92ms)*

- **[PASS]** Google: 20ms
- **[PASS]** Cloudflare: 44ms
- **[PASS]** Quad9: 112ms

### 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+ — 100/100)

*robots.txt present, sitemap with 6 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 6 entries
- **[PASS]** Sitemap index with 6 child sitemaps
- **[PASS]** robots.txt references sitemap

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

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

- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*cloudatlasinc.com — via GoDaddy.com, LLC, 11 years, 2 months old, hosted on AWS*

- **[PASS]** Domain registered until Sep 4, 2027 (11 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: GoDaddy.com, LLC
- **[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: AWS

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A+ — 100/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[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)

*2 known tracker(s) detected*

- **[PASS]** 2 known tracker(s) detected — Inventory of trackers loaded by the page (matched against a curated SDK URL registry):

analytics: Google Analytics (UA) | marketing: LinkedIn Insight

Each entry maps a script URL pattern to a known vendor SDK. This is purely informational -- consent posture / pre-consent firing is graded by the consent analyzer.

### 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. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

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

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 1 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 1 of 8 categories: Recipients of personal data. 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, 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+ — 95/100)

*5 trackers detected*

- **[INFO]** 5 third-party trackers detected — Found 3 analytics, 0 advertising, 1 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.

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

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

- **[INFO]** 5 third-party tracker(s) detected on page

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

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

### 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 navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

### Legal Page Ecosystem (C — 60/100)

*2 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://www.cloudatlasinc.com/privacy-policy/, linked from footer.
- **[PASS]** Terms of Service detected — Found at https://www.cloudatlasinc.com/terms-and-conditions/, linked from footer.
- **[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 (A+ — 100/100)

*© 2026 CloudAtlas Inc*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 CloudAtlas Inc
- **[PASS]** Copyright holder: CloudAtlas Inc

### 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]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .be; Text mentions: gdpr; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*3 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]** 3 third-party services across 3 categories — 3 third-party services detected across 3 categories: Analytics (1), Customer Support (1), Advertising (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Zendesk (Customer Support) — Detected via script URL. Typically collects: Support tickets, Chat transcripts, User identity. Privacy policy: https://www.zendesk.com/company/agreements-and-terms/privacy-policy/. Data Processing Agreement available.
- **[INFO]** LinkedIn Insight (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, Ad targeting, Professional demographics. Privacy policy: https://www.linkedin.com/legal/privacy-policy. Data Processing Agreement available.

### 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 (document or assets)*

- **[WARNING]** No CDN (document or assets) — Neither the HTML document nor the page's subresources are served through an edge network. 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 (includeSubDomains, preload)
- **[PASS]** HSTS preload enabled
- **[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

### Landmark Structure (C — 60/100)

*6 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[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 — 90/100)

*27 headings*

- **[WARNING]** Multiple H1 headings (2 found) — A page should have only one H1. Multiple H1s dilute the document outline.

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

*2 heading-text-quality issue(s) detected*

- **[WARNING]** 3 heading(s) are over 120 characters -- likely a misformatted paragraph — Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected:
  - H2: 199 chars
  - H2: 155 chars
  - H2: 199 chars
- **[INFO]** 5 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

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

*All 51 images OK*

- **[PASS]** 1 decorative image(s) correctly marked
- **[PASS]** 50 image(s) with good alt text

### Form Accessibility (D — 47/100)

*11 of 12 controls have issues*

- **[CRITICAL]** 10 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[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 (C — 68/100)

*6 issue(s) across 68 links and 3 buttons*

- **[WARNING]** 6 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 11 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 51 link(s) with descriptive text

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

*1 input(s) using type=text where a specific type would help*

- **[INFO]** Input "query" should use type="search" (currently type="text") — Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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

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

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

### Mobile Keyboard & Autofill (D — 60/100)

*2/2 eligible field(s) missing autocomplete or inputmode*

- **[WARNING]** 1 field(s) missing recommended autocomplete attribute — WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
- **[WARNING]** 1 field(s) would benefit from inputmode attribute — Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

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

*Lang attribute set to "en-US"*

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

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

*0 positive, 1 -1-on-focusable*

- **[INFO]** tabindex="-1" on naturally-focusable <input> — tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

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

*1/3 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (B — 90/100)

*3 tap target(s) too small or too close together*

- **[INFO]** 3 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)

*All 132 visible text node(s) render at >= 12 CSS pixels*

- **[PASS]** All text uses legible mobile font sizes (>= 12 CSS px)

---

## UX

### 404 Error Page (A — 90/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page
- **[PASS]** Navigation links present on 404 page
- **[PASS]** Homepage link present on 404 page
- **[PASS]** Search form present on 404 page

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

*1 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[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 (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 <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 — 15/100)

*No navigation patterns*

- **[PASS]** 1 navigation landmark(s) detected
- **[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+ — 97/100)

*1 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

---

## SEO

### Canonical URL (A+ — 95/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200
- **[INFO]** Canonical points to a different domain

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

*Title: 67 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 67 characters — may be truncated in search results
- **[PASS]** Meta description length (159 chars) is optimal
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

### 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 (A+ — 100/100)

*1277 words, Very Difficult*

- **[PASS]** Page has 1277 words — good depth for search engines
- **[INFO]** Reading level: Very Difficult (grade 22)

### Internal Links (A+ — 100/100)

*11 internal, 57 external*

- **[PASS]** 11 internal links (16%)
- **[PASS]** 91% of links use descriptive anchor text
- **[INFO]** 11 internal / 57 external links

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

*51 images, 51 descriptive filenames*

- **[PASS]** All images have descriptive filenames

### 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 (B — 80/100)

*Sitemap updated within the last year*

- **[INFO]** Newest sitemap lastmod is 6 months ago -- stale beyond 90 days — No URL in the sitemap has been updated in the last 90 days. The sitemap is technically valid but signals to crawlers that the site isn't actively changing.

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

*No sitemap-vs-robots conflicts detected*

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

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

*Sitemap structure / size look healthy (6 URLs, 1 KB)*

- **[PASS]** Sitemap structure / size look healthy (6 URLs)

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

*1 markup-quality issue(s) detected*

- **[INFO]** 3 redundant ARIA role attribute(s) on native semantic element(s) — The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*1.44g CO2 per view*

- **[WARNING]** 1.44g CO2 per page view — This page transfers 5.1 MB, producing an estimated 1.44g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.27g, network 0.25g, end-user device 0.93g.
- **[INFO]** At 10,000 monthly views: 173.3 kg CO2/year — With 10,000 page views per month, this page would generate approximately 173.3 kg of CO2 annually — equivalent to charging 21660 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)

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 21 KB (vs 5221 KB first visit). 85 of 86 resources are served from browser cache, saving 1.44g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 1.44g)

### Carbon Budget (F — 30/100)

*74th percentile*

- **[WARNING]** 1.44g CO2 — above the median website (0.60g) — Heavier than an estimated 26% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 74th 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 281 KB of potential savings identified. Your page is well-optimized for size.

### Web Font Weight Variants (A+ — 100/100)

*3 font weights loaded across 2 famil(y/ies) -- reasonable*

- **[PASS]** 3 font weight(s) loaded across 2 famil(y/ies)

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/71b35f5e-ca15-483e-a178-9ad39c8ef1b1*