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

**Date:** July 10, 2026  
**URL:** https://twitter.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/f818714b-535e-43c1-b21e-e7c16e1c9b24

## Top Findings

1. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
2. **[CRITICAL]** Page body has only 199 chars of text -- likely empty / placeholder — Security > Empty Page Detection
3. **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — Accessibility > 404 Error Page
4. **[WARNING]** 3 font preload(s) missing `crossorigin` -- font will be downloaded twice — Performance > Resource Hints
5. **[WARNING]** 93 third-party resources (100% of weight) — Performance > Page Weight Inventory

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 33 |
| Accessibility | 93 |
| Best Practices | 92 |
| SEO | 100 |

---

## Security

### Security Headers (B — 70/100)

*6 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured (consider adding preload)
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[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.
- **[PASS]** Content-Security-Policy is present
- **[INFO]** Cross-Origin-Opener-Policy is set but not 'same-origin'
- **[PASS]** Cross-Origin-Embedder-Policy is set
- **[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
- **[PASS]** Domain is in the Chrome HSTS preload list (status: preloaded)

### Content Security Policy (C — 60/100)

*5 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[PASS]** No 'unsafe-eval' in script source
- **[PASS]** No wildcard in script source
- **[PASS]** object-src is set to 'none'
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[PASS]** form-action directive is set
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

### 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 42 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 3 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

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

*6 cookies analyzed, 13 checks passed*

- **[PASS]** Cookie 'guest_id_marketing' has the Secure flag
- **[WARNING]** Cookie 'guest_id_marketing' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'guest_id_marketing' has SameSite=None
- **[PASS]** Cookie 'guest_id_ads' has the Secure flag
- **[WARNING]** Cookie 'guest_id_ads' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'guest_id_ads' has SameSite=None
- **[PASS]** Cookie 'personalization_id' has the Secure flag
- **[WARNING]** Cookie 'personalization_id' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'personalization_id' has SameSite=None
- **[PASS]** Cookie 'guest_id' has the Secure flag
- **[WARNING]** Cookie 'guest_id' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'guest_id' has SameSite=None
- **[PASS]** Cookie 'ct0' has the Secure flag
- **[WARNING]** Cookie 'ct0' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'ct0' has SameSite=Lax
- **[PASS]** Cookie '__cf_bm' has the Secure flag
- **[PASS]** Cookie '__cf_bm' has the HttpOnly flag
- **[PASS]** Cookie '__cf_bm' has SameSite=None

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

*1 hygiene issue(s) across 6 cookie(s)*

- **[INFO]** 4 cookie(s) live for more than 1 year — Cookies with Max-Age or Expires more than 1 year out are effectively permanent on the user's device. Most session and preference cookies don't need that lifetime. Long-lived tracking cookies also carry a heavier compliance load (GDPR / CCPA). Affected: guest_id_marketing, guest_id_ads, personalization_id (+1 more).

### WAF / Bot Protection (A — 90/100)

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a18f229e5b8a1d47-SIN

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

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt has expired — The Expires field is 2024-01-01T06:00:00.000Z, which is in the past. Update it.
- **[PASS]** security.txt is PGP signed

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

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

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

### CSP Inline-Style Readiness (B — 90/100)

*5 inline style attribute(s) detected*

- **[INFO]** 5 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. 5 inline style(s) is low. Affected element types include: body, div, button. 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) (B — 95/100)

*Trusted Types not enabled*

- **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

### 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)

*HTTP status is non-2xx -- soft-404 check is N/A*

- **[PASS]** HTTP status is non-2xx -- soft-404 check is N/A

### Empty Page Detection (F — 0/100)

*1 empty-page signal(s) detected -- page may be a placeholder or have content-rendering bugs*

- **[CRITICAL]** Page body has only 199 chars of text -- likely empty / placeholder — After HTML stripping, the page body contains 199 characters of text content. Below 200 chars almost always means: (1) the page is a placeholder that was never filled in, (2) JavaScript was supposed to render content but failed, (3) the page is a redirect / interstitial / wrapper that should have a real status code other than 200, or (4) it's a legitimately small page like a single-form login (in which case this finding is a false positive that confirms 'minimal content' is intentional).

Review the page in a browser. If content is missing, the most common root cause is a JS-rendering pipeline that needs prerendering or server-side rendering for crawlers / scanners to capture content.

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

- **[WARNING]** SRI adoption: 0/4 third-party resources protected (0%) — Of 4 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 4 examples):
  - https://abs.twimg.com/responsive-web/client-web/vendor.6f0bbb5a.js
  - https://abs.twimg.com/responsive-web/client-web/i18n/en.8f58303a.js
  - https://abs.twimg.com/responsive-web/client-web/main.4b8dc5fa.js
  - https://accounts.google.com/gsi/client

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

*Source-map probe didn't run on this scan*

- **[PASS]** Source-map probe didn't run on this scan

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

- **[WARNING]** External script from abs.twimg.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from abs.twimg.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from abs.twimg.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from accounts.google.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 (A — 90/100)

*DMARC: reject, SPF: -all, DKIM*

- **[PASS]** DMARC policy is reject — strongest protection
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[PASS]** DKIM configured (selectors: dkim, google, mandrill)
- **[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 (D — 42/100)

*2.5 MB transferred, 94 requests*

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

### Third-Party Impact (D — 50/100)

*100% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 100% of page weight (2.5 MiB of 2.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 (A+ — 95/100)

*3 images, 0 KB saveable*

- **[PASS]** All images are well-optimized

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

*7790ms total JS execution*

- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/on...: 3222ms CPU time
- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/ma...: 1978ms CPU time
- **[WARNING]** Unattributable: 717ms CPU time
- **[WARNING]** https://x.com/: 475ms CPU time
- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/on...: 271ms CPU time
- **[WARNING]** Third-party scripts: 7073ms (91% of total)

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

*4 fonts (200 KB)*

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

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

*74 scripts, 756 KB unused*

- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/ma...: 142 KB unused (50%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/ve...: 88 KB unused (47%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/on...: 73 KB unused (35%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://accounts.google.com/gsi/client: 72 KB unused (75%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://abs.twimg.com/responsive-web/client-web/mo...: 70 KB unused (99%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 756 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 — 85/100)

*35 hints, 0 missing preconnects*

- **[WARNING]** 3 font preload(s) missing `crossorigin` -- font will be downloaded twice — Fonts are always fetched as crossorigin=anonymous; a preload without the attribute creates a different cache key, so the browser refetches when the actual font request happens. Sample: https://abs.twimg.com/responsive-web/client-web/Chirp-Regular.80fda27a.woff2, https://abs.twimg.com/responsive-web/client-web/Chirp-Bold.ebb56aba.woff2, https://abs.twimg.com/responsive-web/client-web/Chirp-Medium.f8e2739a.woff2. Add `crossorigin` (or `crossorigin="anonymous"`) to each preload.
- **[PASS]** Page uses 35 resource hint(s)

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

*Main response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### 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 uses no-cache -- safe revalidate-on-request policy*

- **[PASS]** Main HTML uses no-cache -- safe revalidate-on-request policy

### 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)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept — 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).
- **[PASS]** `Last-Modified` present -- timestamp-based conditional GET supported — Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.

### Page Weight Inventory (F — 30/100)

*94 resources · 2.5 MB · 756 KB savings available*

- **[WARNING]** Page weight 2.5 MB exceeds 1 MB target by 1.5 MB
- **[INFO]** ~756 KB of savings available
- **[WARNING]** 93 third-party resources (100% 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 — 90/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** Total JS execution time is 7.8 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 (A+ — 100/100)

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (B — 83/100)

*55 links checked, 51 healthy, 3 broken*

- **[WARNING]** 51 of 55 links are healthy
- **[WARNING]** Broken link: https://abs.twimg.com — Found in <link href>. Returns HTTP 400.
- **[WARNING]** Broken link: https://api.x.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://pbs.twimg.com — Found in <link href>. Returns HTTP 400.
- **[INFO]** Long redirect chain: https://support.x.com/articles/20170514 (4 hops)

### 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]** og:title is short (24 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

*No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)*

- **[PASS]** No OG image / Twitter card to evaluate

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

*1 A records, 176 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
- **[PASS]** 8 nameserver(s) configured
- **[PASS]** 5 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 176 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/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 162.159.140.229: lookup 162.159.140.229: 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 1ms across 3 resolvers (spread 1ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Google: 1ms
- **[PASS]** Cloudflare: 2ms

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

*1 redirect(s), 437 ms total*

- **[PASS]** Single redirect
- **[INFO]** Cross-domain redirect detected

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

*robots.txt present, sitemap with 0 URLs*

- **[PASS]** robots.txt is present
- **[CRITICAL]** robots.txt blocks all crawlers — Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
- **[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 (B — 75/100)

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

- **[PASS]** www/non-www redirect configured correctly (preferred: non-www)
- **[CRITICAL]** HTTP version does not redirect to HTTPS

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

*twitter.com — via CSC Corporate Domains, Inc., 26 years, 10 months old, hosted on Cloudflare*

- **[PASS]** Domain registered until Jan 21, 2027 (6 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: CSC Corporate Domains, 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.
- **[PASS]** Hosting: Cloudflare

---

## Compliance

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

*No testable criteria*


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

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[CRITICAL]** 5 non-essential cookie(s) set without consent banner — Social-media: personalization_id, guest_id | Unrecognized (treated as non-essential): guest_id_marketing, guest_id_ads, ct0
- **[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 (C — 60/100)

*Viewport prevents zooming*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[CRITICAL]** Viewport prevents user zooming — user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.

### Accessibility Statement (A — 85/100)

*Statement found, no conformance level*

- **[INFO]** Accessibility statement found but lacks WCAG conformance level — Mature accessibility statements declare a target conformance level (e.g., WCAG 2.1 AA). Without a stated level, users and reviewers cannot tell what the statement actually commits to.

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

*3 trackers detected*

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

### Cookie & Tracker Inventory (C — 60/100)

*6 cookies · 3 trackers · 5 pre-consent*

- **[CRITICAL]** 5 tracking cookie(s) set before consent interaction — Under GDPR ePrivacy Art. 5(3), analytics and advertising cookies require explicit opt-in. These cookies appeared in the server response without any consent step — a likely violation.
- **[INFO]** 3 third-party tracker(s) detected on page

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

*5 cross-site cookie(s) (5 tracking-shaped, 0 essential)*

- **[WARNING]** 5 tracking-shaped cross-site cookie(s): __cf_bm, guest_id, guest_id_ads, guest_id_marketing, personalization_id — Cookies with SameSite=None travel in cross-site contexts (third-party iframes, cross-origin POSTs, embedded widgets). With third-party cookies dying in Chrome/Firefox, the legitimate use cases narrowed to SSO + payment widgets + federated auth. Each tracking-shaped cookie surfaced here is a cross-site analytics or ad-tech surface that needs explicit privacy-policy disclosure beyond basic cookie banner consent. Audit each: is it conditional on consent? Does the privacy policy name the recipient + purpose? Switching to SameSite=Lax disables the cross-site travel without breaking same-site analytics.

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

*4 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://x.com/privacy, linked from footer.
- **[PASS]** Terms of Service detected — Found at https://x.com/tos, linked from footer.
- **[PASS]** Cookie Policy detected — Found at https://support.x.com/articles/20170514, linked from footer.
- **[PASS]** Accessibility Statement detected — Found at https://help.x.com/resources/accessibility, linked from footer.
- **[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 X Corp*

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

### Regulatory Indicators

*2 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 (moderate confidence) — Indicators suggesting GDPR may be relevant: Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
- **[INFO]** ADA indicators detected (moderate confidence) — Indicators suggesting ADA may be relevant: Accessibility statement page found. Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.

### Third-Party Data Sharing

*1 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]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: CDN (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Cloudflare (CDN) — Detected via cookie name. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. 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 (A — 85/100)

*Cloudflare (DYNAMIC)*

- **[PASS]** Site is served via Cloudflare CDN (edge: SIN)
- **[INFO]** CDN cache status: DYNAMIC

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

*no-cache, private, must-revalidate, pre-check=0, post-check=0*

- **[PASS]** Cache-Control header is set
- **[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 — 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)
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*Health endpoint at https://twitter.com/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://twitter.com/health

### CDN Cache Observability (A+ — 100/100)

*Cache state: DYNAMIC*

- **[PASS]** CDN cache state observable via 2 header(s)

---

## Accessibility

### Landmark Structure (B — 75/100)

*2 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 1 <nav> landmark(s) found
- **[INFO]** No banner (header) landmark
- **[INFO]** No contentinfo (footer) landmark
- **[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+ — 100/100)

*1 headings*

- **[PASS]** Single H1 present

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

*All 1 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+ — 100/100)

*No form controls*

- **[PASS]** No form controls on this page

### Link & Button Quality (A — 88/100)

*12 links, 0 buttons — all OK*

- **[WARNING]** 12 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.

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

*No form controls on this page*

- **[PASS]** No form controls on this page

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

*No form controls on this page*

- **[PASS]** No form controls on this page

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

*No form controls -- mobile keyboard check is N/A*

- **[PASS]** No form controls on this page

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

*1/1 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 (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 (D — 60/100)

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

- **[WARNING]** 14 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> 11.2px ("Email or username"); <span> 11.0px ("About"); <span> 11.0px ("Get App"); <span> 11.0px ("Grok"); <span> 11.0px ("Help").

---

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

*7 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (A+ — 100/100)

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: X
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*No PWA depth issues detected*

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

### Dark Mode Support (B — 70/100)

*Dark mode detected*

- **[PASS]** Dark-specific theme-color detected — A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
- **[PASS]** prefers-color-scheme CSS detected in inline styles
- **[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+ — 100/100)

*2 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.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (32 chars) is optimal
- **[PASS]** Meta description length (109 chars) is optimal
- **[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 (F — 10/100)

*39 words, Standard*

- **[CRITICAL]** Page has only 39 words — nearly empty — Search engines need substantive text content to understand and rank a page.
- **[INFO]** Text-to-HTML ratio is 0% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Standard (grade 7)
- **[WARNING]** Thin content — only 39 words

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

*0 internal, 12 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 / 12 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 (F — 30/100)

*robots.txt blocks ALL crawling but sitemap.xml exists -- contradictory*

- **[CRITICAL]** robots.txt has 'Disallow: /' but sitemap.xml is published -- contradictory signals — Disallow: / for User-agent: * tells crawlers to skip the entire site, but the sitemap announces URLs to crawl. Either remove the Disallow: / (production sites) or remove the sitemap (intentional staging).

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

*2 markup-quality issue(s) detected*

- **[INFO]** `<meta charset>` declared at byte 3519 -- past the 1024-byte spec window — The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.
- **[INFO]** 14 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 (B — 70/100)

*0.59g CO2 per view*

- **[INFO]** 0.59g CO2 per page view — This page transfers 2.5 MB, producing an estimated 0.59g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.01g, network 0.12g, end-user device 0.45g.
- **[INFO]** At 10,000 monthly views: 71.0 kg CO2/year — With 10,000 page views per month, this page would generate approximately 71.0 kg of CO2 annually — equivalent to charging 8880 smartphones.
- **[PASS]** Green hosting reduces data center emissions

### Green Hosting (A+ — 100/100)

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Amazon Web Services: Verified by the Green Web Foundation
- **[INFO]** Cloudflare: 100% renewable energy for global network since 2019
- **[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)

*97% cached*

- **[PASS]** 97% reduction on repeat visits — Returning visitors download only 69 KB (vs 2561 KB first visit). 93 of 94 resources are served from browser cache, saving 0.58g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.02g CO2 (first visit: 0.59g)

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

*49th percentile*

- **[INFO]** 0.59g CO2 — below the median website (0.60g) — Better than an estimated 51% of websites, but above the sustainability target of 0.50g. Reducing page weight would help reach the target.
- **[INFO]** Estimated 49th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

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

*71% efficient*

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

### Web Font Weight Variants (B — 90/100)

*No detectable Google Fonts weights*

- **[INFO]** No detectable Google Fonts weights — The analyzer detects font weights via Google Fonts URL parameters (~70% of font-using sites). Self-hosted fonts and non-Google CDN fonts aren't visible to URL-based detection. If you self-host fonts, manually audit how many @font-face weights you ship -- 2-3 weights per family is typically enough; 5+ is usually unused payload.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/f818714b-535e-43c1-b21e-e7c16e1c9b24*