# BeaverCheck Audit Report — https://wikipedia.org

**Date:** July 9, 2026  
**URL:** https://wikipedia.org  
**Overall Grade:** B (85/100)  
**Report:** https://beavercheck.com/results/917c4fc3-3e90-41f0-872e-b180f75b9554

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
3. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality
4. **[WARNING]** 2 link(s) open in a new tab without rel=noopener — Security > Cross-Origin Tab Safety
5. **[WARNING]** 2 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 96 |
| Accessibility | 95 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*3 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[PASS]** Domain is in the Chrome HSTS preload list (status: preloaded)

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

*No enforcing CSP policy found*

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

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

*TLS 1.3, 7 checks passed*

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

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

*5 cookies analyzed, 10 checks passed*

- **[PASS]** Cookie 'WMF-Last-Access' has the Secure flag
- **[PASS]** Cookie 'WMF-Last-Access' has the HttpOnly flag
- **[WARNING]** Cookie 'WMF-Last-Access' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'WMF-Last-Access-Global' has the Secure flag
- **[PASS]** Cookie 'WMF-Last-Access-Global' has the HttpOnly flag
- **[WARNING]** Cookie 'WMF-Last-Access-Global' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'GeoIP' has the Secure flag
- **[WARNING]** Cookie 'GeoIP' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'GeoIP' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'NetworkProbeLimit' has the Secure flag
- **[WARNING]** Cookie 'NetworkProbeLimit' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'NetworkProbeLimit' has SameSite=None
- **[PASS]** Cookie 'WMF-Uniq' has the Secure flag
- **[PASS]** Cookie 'WMF-Uniq' has the HttpOnly flag
- **[PASS]** Cookie 'WMF-Uniq' has SameSite=None

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

*All 5 cookie(s) pass hygiene checks*

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

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

*No WAF detected via response headers*

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

### security.txt (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 (C — 75/100)

*2 of 4 new-tab link(s) missing rel=noopener*

- **[WARNING]** 2 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 (A+ — 100/100)

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

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

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

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

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

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

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

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

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

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

*Page has no third-party scripts or stylesheets -- SRI not applicable*

- **[PASS]** No third-party scripts or stylesheets to protect with SRI

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

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

- **[PASS]** No source maps accessible across 2 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 (A+ — 100/100)

*No external resources*

- **[PASS]** No external resources to protect

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

*No known vulnerabilities*

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

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

*No exposures*

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

### Email Security (C — 62/100)

*DMARC: reject, SPF: ~all*

- **[PASS]** DMARC policy is reject — strongest protection
- **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

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

*No header set*

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

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (A+ — 100/100)

*101 KB transferred, 7 requests*

- **[PASS]** Page weighs 231 KB (101 KB transferred)
- **[PASS]** 7 HTTP requests
- **[INFO]** Estimated 0.02 g CO2 per page load

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

*99% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 99% of page weight (99.6 KiB of 100.9 KiB)
- **[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 — 90/100)

*2 images, 0 KB saveable*

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

### JS Execution Cost (C — 60/100)

*1103ms total JS execution*

- **[WARNING]** https://www.wikipedia.org/: 878ms CPU time
- **[INFO]** Unattributable: 173ms CPU time
- **[INFO]** https://www.wikipedia.org/portal/wikipedia.org/ass...: 52ms CPU time
- **[WARNING]** Third-party scripts: 930ms (84% of total)

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

*No web fonts (system fonts)*

- **[PASS]** No web fonts loaded — system fonts are fastest

### JS Bundles (A+ — 100/100)

*2 scripts, 0 KB unused*


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

*All resources properly cached*

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

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

*No render-blocking resources*

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

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

*2 hints, 0 missing preconnects*

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

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

*Main response served uncompressed*

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

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

*LCP preload audit not available*

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

### Main HTML Cache-Control (B — 80/100)

*No Cache-Control header on main HTML response*

- **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

### Server-Timing Observability (A+ — 100/100)

*2 Server-Timing entries advertised*

- **[PASS]** Server-Timing header advertises 2 timing entries

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: X-Forwarded-Proto — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<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 (A — 85/100)

*7 resources · 101 KB · 0 KB savings available*

- **[PASS]** Within 1MB page-weight target
- **[WARNING]** 6 third-party resources (99% of weight)

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

*1 JS blocking issue(s) detected*

- **[WARNING]** 2 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.

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

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (F — 40/100)

*200 links checked, 142 healthy, 58 broken*

- **[CRITICAL]** 142 of 200 links are healthy
- **[CRITICAL]** Broken link: https://ceb.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://lb.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://li.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://lmo.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://mai.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://ml.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://xmf.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://mzn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://cdo.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://mn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://nap.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://frr.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://oc.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://mhr.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://or.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://pa.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://pnb.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://pms.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://nds.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://crh.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://rue.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://sa.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://skr.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://sah.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://sco.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://sn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://scn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://sd.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://szl.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://so.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://su.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://shi.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://shn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://zgh.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://tly.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://tum.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://bug.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://vec.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://vo.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://wa.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://zh-classical.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://wuu.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://yi.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://yo.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://diq.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://bat-smg.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://zu.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://ne.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://mni.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://lad.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://kbd.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://ang.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://smn.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://anp.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://ab.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://roa-rup.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://frp.wikipedia.org/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://atj.wikipedia.org/ — Found in <a href>. Returns HTTP 429.

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

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

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

### Open Graph (C — 75/100)

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

- **[CRITICAL]** og:image is not reachable — The og:image URL could not be fetched. Social platforms won't be able to display it.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social 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)

*OG image dimensions and Twitter card configuration look healthy*

- **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

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

*1 issues found across 1 images*

- **[WARNING]** All 1 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.

### 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, 29 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.
- **[PASS]** Has 1 IPv6 (AAAA) record(s)
- **[PASS]** 3 nameserver(s) configured
- **[PASS]** 2 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 29 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 (A+ — 100/100)

*issue: letsencrypt.org, pki.goog | iodef configured*

- **[PASS]** CAA issue tag present — authorized CA(s): letsencrypt.org, pki.goog
- **[PASS]** CAA iodef tag present (failed-issuance notifications enabled)

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

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 185.15.58.224 does not match any cert SAN: text-lb.drmrs.wikimedia.org — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a02:ec80:600:ed1a::1 does not match any cert SAN: text-lb.drmrs.wikimedia.org — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

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

*Mean 14ms across 3 resolvers (spread 25ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 17ms
- **[PASS]** Google: 26ms

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

*1 redirect(s), 207 ms total*

- **[PASS]** Single redirect
- **[INFO]** WWW normalization redirect

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (26 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a02:ec80:600:ed1a::1

### Crawlability (B — 80/100)

*robots.txt present, no sitemap*

- **[PASS]** robots.txt is present
- **[INFO]** No sitemap.xml found — A sitemap helps search engines discover and index your pages more efficiently.
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

### URL Variants (B — 75/100)

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

- **[CRITICAL]** Both www and non-www versions serve content
- **[PASS]** HTTP correctly 301-redirects to HTTPS

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

*wikipedia.org — via MarkMonitor Inc., 25 years, 10 months old*

- **[PASS]** Domain registered until Jan 13, 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: MarkMonitor Inc.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

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

*No testable criteria*


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

*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 — Unrecognized (treated as non-essential): WMF-Last-Access, WMF-Last-Access-Global, GeoIP, NetworkProbeLimit, WMF-Uniq
- **[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)

*1 i18n signal(s) detected*

- **[PASS]** Mixed-language content: 350 subtree language(s) declared (ja, de, ru, fr, es, zh, it, pl, pt, af, sq, ar, ast, az, bg, nan, bn, be, ca, cs, cy, da, et, el, eo, eu, fa, gl, ko, ha, hy, hi, hr, id, he, ka, lld, la, lv, lt, hu, mk, mg, mr, arz, ms, min, my, nl, nb, nn, ce, uz, kk, ro, ceb, sk, sl, sr, sh, fi, sv, sw, ta, tt, te, th, tg, azb, tr, uk, ur, vi, war, yue, no, kk-cyrl, kk-latn, kk-arab, ace, gsw, am, an, hyw, gor, ban, bjn, map-x-bms, ba, be-tarask, bcl, bpy, bar, bs, br, cv, dag, ary, nv, roa-x-eml, hif, fo, fy, ff, ga, gd, glk, gu, hak, hsb, io, ig, ilo, ia, ie, os, is, jv, kn, pam, km, ks, avk, ht, ku, ku-latn, ku-arab, ckb, ky, mjr, lb, lij, li, lmo, mai, ml, xmf, mzn, cdo, mn, nap, new, frr, oc, mhr, or, as, pa, pnb, ps, pms, nds, kaa, crh, qu, rue, sa, sat, skr, sah, sco, sn, scn, si, sd, szl, so, su, shi, tl, shn, zgh, tly, tum, bug, vec, vo, wa, lzh, wuu, yi, yo, diq, sgs, zu, ne, mni, lad, lad-latn, lad-hebr, kbd, ang, smn, anp, ab, rup, frp, atj, arc, gn, av, ay, bbc, bew, bh, bi, bo, bxr, cbk-x-zam, ny, co, za, dga, se, pdc, dv, dsb, myv, ext, ee, gur, fon, fur, gv, gag, inh, gpe, ki, gan, guw, got, xal, haw, igl, rw, iba, kbp, dtp, knc, kai, csb, kw, kv, koi, kg, gom, gcr, kge, kus, lo, lbe, ltg, lez, nia, ln, lfn, olo, jbo, lg, mad, mt, btm, mi, fat, mwl, mdf, mnw, mos, nqo, fj, nah, pcm, nds-nl, roa-x-nrm, nov, om, blk, pag, ami, pap, jam, pfl, pcd, krc, ksh, rm, rsk, szy, sm, sc, trv, stq, st, nso, tn, syl, cu, srn, ss, ty, kab, roa, tay, tet, tpi, tok, to, chr, chy, ts, tk, tw, kcg, tyv, udm, ug, vep, vro, vls, wo, xh, zea, alt, awa, dty, tcy, rki, bdr, bm, ch, dz, iu, ik, nr, kaj, ppl, nup, ann, pi, pwn, pnt, rmy, rn, sg, tdd, ti, din, ve, guc, ady) — The page has elements with `lang="X"` attributes that differ from the root `<html lang>`. Per WCAG 3.1.2 (Level AA), this is the correct way to mark language-of-parts: a screen reader switches pronunciation when entering a `lang="fr"` block on an English page. The catalog is informational -- presence of subtree lang attributes is a positive a11y signal.

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

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

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

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

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

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

*1 trackers detected*

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

### Cookie & Tracker Inventory (B — 84/100)

*5 cookies · 1 trackers · 2 pre-consent*

- **[CRITICAL]** 2 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 cookie(s) could not be classified
- **[INFO]** 1 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) (B — 85/100)

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

- **[INFO]** 2 tracking-shaped cross-site cookie(s): NetworkProbeLimit, WMF-Uniq — 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 (F — 35/100)

*1 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy, linked from footer.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

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

*No copyright notice detected*

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

### Regulatory Indicators

*0 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]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### Third-Party Data Sharing

*0 third-party service(s) detected*

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

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

*0 compliance badge(s) detected*

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

---

## Availability

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

*No CDN detected*

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

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

*Cache state: CP6016*

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

---

## Accessibility

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

*6 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 3 <nav> landmark(s) found
- **[PASS]** All <nav> elements are properly labeled
- **[INFO]** No banner (header) 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.
- **[PASS]** Search landmark present

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

*7 headings*

- **[PASS]** Single H1 present

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

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

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

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

*All 1 images OK*

- **[PASS]** 1 decorative image(s) correctly marked

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

*All 2 controls labeled*

- **[PASS]** 2 control(s) properly labeled

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

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

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

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

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

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

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

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

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

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

*No autofill-eligible form controls*

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

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

*Lang attribute set to "en"*

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

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

*No explicit tabindex attributes found*

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

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

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

### Mobile-Readable Font Sizes (A+ — 100/100)

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

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

---

## UX

### 404 Error Page (B — 80/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

### Favicon & Branding (C — 55/100)

*3 icon(s) detected*

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

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

*Dark mode detected*

- **[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 — 35/100)

*1 navigation pattern(s)*

- **[PASS]** Search functionality detected
- **[PASS]** 3 navigation landmark(s) detected

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

*Title: 5 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 5 characters — consider expanding
- **[PASS]** Meta description length (130 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 (B — 80/100)

*868 words, Very Difficult*

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

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

*1 internal, 375 external*

- **[PASS]** 1 internal links (0%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** Page has 376 links — consider reducing
- **[INFO]** 1 internal / 375 external links

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

*1 images, 1 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 (C — 75/100)

*No sitemap.xml found*

- **[INFO]** No sitemap.xml found — Sitemaps help search engines discover and prioritize URLs. Not strictly required for small sites where every page is linked from the homepage, but recommended once a site grows beyond a few dozen URLs.

### Sitemap × Robots Consistency (C — 75/100)

*Sitemap or robots.txt missing -- consistency check skipped*

- **[INFO]** Cross-check skipped (sitemap or robots.txt absent)

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

*No sitemap to evaluate -- depth check is N/A*

- **[PASS]** No sitemap fetched -- depth check skipped

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*0.03g CO2 per view*

- **[PASS]** 0.03g CO2 per page view — This page transfers 0.1 MB, producing an estimated 0.03g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.01g, network 0.00g, end-user device 0.02g.
- **[INFO]** At 10,000 monthly views: 3.3 kg CO2/year — With 10,000 page views per month, this page would generate approximately 3.3 kg of CO2 annually — equivalent to charging 418 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 (B — 80/100)

*69% cached*

- **[PASS]** 69% reduction on repeat visits — Returning visitors download only 31 KB (vs 100 KB first visit). 6 of 7 resources are served from browser cache, saving 0.02g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.03g)

### Carbon Budget (A+ — 100/100)

*10th percentile*

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

### Transfer Efficiency (A+ — 100/100)

*100% efficient*

- **[PASS]** Transfer efficiency: 100% — Only 0 KB of potential savings identified. Your page is well-optimized for size.

### 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/917c4fc3-3e90-41f0-872e-b180f75b9554*