# BeaverCheck Audit Report — https://serebrokubachi.ru

**Date:** October 20, 2026  
**URL:** https://serebrokubachi.ru  
**Overall Grade:** B (83/100)  
**Report:** https://beavercheck.com/results/cabd0116-0ac9-4ab7-8f30-acaf7e80b995

## Top Findings

1. **[CRITICAL]** /.git/HEAD is publicly accessible — Security > Information Leakage
2. **[CRITICAL]** /.git/config is publicly accessible — Security > Information Leakage
3. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
4. **[CRITICAL]** HSTS header is missing — Security > Security Headers
5. **[WARNING]** 1 software version(s) disclosed in HTML: WordPress 7.1.3 — Security > HTML Version Disclosure

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 68 |
| Accessibility | 92 |
| Best Practices | 96 |
| SEO | 100 |

---

## Security

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

*2 of 10 headers properly configured*

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

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

*No enforcing CSP policy found*

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

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

*TLS 1.3, 8 checks passed*

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

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

*No cookies set — no cookie security risks*

- **[PASS]** No cookies set — no cookie security risks

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

*No cookies set -- cookie-hygiene check is N/A*

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

### security.txt (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

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

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

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

### CSP Inline-Style Readiness (C — 75/100)

*13 inline style attribute(s) detected*

- **[WARNING]** 13 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. 13 inline style(s) is moderate. Affected element types include: i, span, div, svg. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- **[WARNING]** SRI adoption: 0/3 third-party resources protected (0%) — Of 3 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 3 examples):
  - https://mc.yandex.com/metrika/tag.js
  - https://www.googletagmanager.com/gtag/js?id=G-R35CE3JWHQ&cx=c&gtm=4e6aj0
  - //www.googletagmanager.com/gtm.js?id=GTM-TVLPKZ9C

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)

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

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

### HTML Version Disclosure (C — 75/100)

*1 software version(s) disclosed in HTML*

- **[WARNING]** 1 software version(s) disclosed in HTML: WordPress 7.1.3 — Each disclosed version enables direct CVE lookup -- an attacker who knows you run WordPress 6.4.2 (or whatever specific version) can search the CVE database for known exploits and target accordingly. Remove via your CMS config: WordPress (`remove_action('wp_head', 'wp_generator')`); Drupal (System / Reports / Status report -> Hide generator); Joomla (Global Configuration -> Hide generator); Hugo/Jekyll (delete or override the {{ .Site.Generator }} template hook). For HTML comments, audit your template files directly.

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

- **[WARNING]** External script from mc.yandex.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.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 (D — 40/100)

*Critical exposure detected*

- **[CRITICAL]** /.git/HEAD is publicly accessible — Version control directory is accessible. This exposes source code and potentially secrets. Block access in your web server configuration.
- **[CRITICAL]** /.git/config is publicly accessible — Version control directory is accessible. This exposes source code and potentially secrets. Block access in your web server configuration.
- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.

### Email Security (D — 40/100)

*DMARC: none, SPF: -all*

- **[WARNING]** DMARC policy is none — monitoring only — This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject after monitoring DMARC reports.
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<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 (B — 84/100)

*1.1 MB transferred, 99 requests*

- **[PASS]** Page weighs 2.3 MB (1.1 MB transferred)
- **[INFO]** 99 HTTP requests
- **[INFO]** Estimated 0.22 g CO2 per page load

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

*37% third-party, 0 ms blocking*

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

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

*All text resources are compressed*

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

### Image Optimization (B — 75/100)

*65 images, 0 KB saveable*

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

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

*4320ms total JS execution*

- **[WARNING]** https://serebrokubachi.ru/: 2796ms CPU time
- **[WARNING]** Unattributable: 450ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-R35C...: 382ms CPU time
- **[INFO]** https://mc.yandex.com/metrika/tag.js: 243ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtm.js?id=GTM-TVL...: 200ms CPU time
- **[INFO]** Third-party scripts: 824ms (19% of total)

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

*5 fonts (64 KB)*

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

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

*14 scripts, 174 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-R35C...: 73 KB unused (39%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-TVL...: 64 KB unused (48%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://mc.yandex.com/metrika/tag.js: 37 KB unused (54%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 174 KB

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

*All resources properly cached*

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

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

*No render-blocking resources*

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

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

*20 hints, 0 missing preconnects*

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

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

*HTTP/3 advertised via Alt-Svc*

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

### Document Compression (B — 80/100)

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

### Asset Compression

*No text asset hosts to measure*

- **[INFO]** No third-party or subdomain host served enough text assets to measure — Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

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

*LCP preload audit not available*

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

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

*No Cache-Control header on main HTML response*

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

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

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

*99 resources · 1.1 MB · 174 KB savings available*

- **[WARNING]** Page weight 1.1 MB exceeds 1 MB target by 64 KB
- **[INFO]** ~174 KB of savings available
- **[INFO]** 17 third-party resources (37% 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 (B — 84/100)

*2 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.
- **[WARNING]** Total JS execution time is 4.3 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 (F — 38/100)

*159 links checked, 129 healthy, 29 broken*

- **[CRITICAL]** 129 of 159 links are healthy
- **[WARNING]** Broken link: https://serebrokubachi.ru/xmlrpc.php — Found in <link href>. Returns HTTP 405.
- **[WARNING]** Broken link: https://serebrokubachi.ru/wp-content/uploads/sk-home-420-... — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.googletagmanager.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://st.top100.ru — Found in <link href>. Returns HTTP 502.
- **[WARNING]** Broken link: https://www.googleadservices.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://serebrokubachi.ru/comments/feed — Found in <link href>. Returns HTTP 404.
- **[INFO]** Long redirect chain: https://maps.google.com/?q=55°46'00.5,37°36'09.2 (4 hops)
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/stolovoe-serebro/ — Found in <a href>. Get "https://serebrokubachi.ru/catalog/stolovoe-serebro/": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/stolovoe-serebro/serebr... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/stolovoe-serebro/serebryanye-stolovye-pribory/": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/?add-to-cart=310 — Found in <a href>. Get "https://serebrokubachi.ru/?add-to-cart=310": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/podarki/zhenshhine/sere... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/podarki/zhenshhine/serebryanoe-zerkalo": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/?add-to-cart=20157 — Found in <a href>. Get "https://serebrokubachi.ru/?add-to-cart=20157": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/podarki/zhenshhine/zhen... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/podarki/zhenshhine/zhenskie-serebrjanye-chasy": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/?add-to-cart=34733 — Found in <a href>. Get "https://serebrokubachi.ru/?add-to-cart=34733": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/stolovoe-serebro — Found in <a href>. Get "https://serebrokubachi.ru/catalog/stolovoe-serebro": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/stolovoe-serebro/serebr... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/stolovoe-serebro/serebryanye-stolovye-pribory/serebryanye-chajnye-lozhki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/gra... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/grafiny": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/kuv... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/kuvshiny": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/ser... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/serebryanye-bokaly-i-kubki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/sta... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/stakany-podstakanniki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/ryu... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/ryumki-stopki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/kru... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/kruzhki-chashki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/cha... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/chajniki-kofejniki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/vaz... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/vazy-konfetnitsy-saharnitsy": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/pod... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/podnosy-tarelki": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/serebryanaya-posuda/nab... — Found in <a href>. Get "https://serebrokubachi.ru/catalog/serebryanaya-posuda/nabory-servizy": context deadline exceeded
- **[CRITICAL]** Broken link: https://serebrokubachi.ru/catalog/podarki — Found in <a href>. Get "https://serebrokubachi.ru/catalog/podarki": context deadline exceeded
- **[WARNING]** Broken link: https://serebrokubachi.ru/wp-content/litespeed/js/13ccc68... — Found in <script src>. Returns HTTP 404.
- **[WARNING]** Broken link: https://serebrokubachi.ru/wp-content/litespeed/js/4d5bf67... — Found in <script src>. Returns HTTP 404.

### Mixed Content (D — 60/100)

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

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

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

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


### Open Graph / Twitter Card Depth (B — 80/100)

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

- **[INFO]** og:image aspect ratio 1.33:1 (320×240) is outside Facebook's recommended ~1.91:1 — Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 320×240 give a ratio of 1.33:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
- **[WARNING]** Twitter card is `summary_large_image` but OG image is 320×240 (ratio 1.33:1) -- closer to square — `twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (320×240, aspect ratio 1.33:1) are closer to square than wide. Twitter will crop the image to fit the wide format, often badly. Either: (1) provide a wider image (~2:1 ratio recommended; minimum 600×314, optimal 1200×630), or (2) change `twitter:card` to `summary` which uses a square thumbnail crop.

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

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

- **[PASS]** Custom type "Place" — unable to validate specific properties

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

*1 JSON-LD block(s) declaring 8 schema type(s)*

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

BlogPosting, ImageObject, Organization, Person, Place, Store, WebPage, WebSite

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

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

*5 issues found across 48 images*

- **[WARNING]** 4 images significantly larger than display size — Resizing to display dimensions could save approximately 13 KB.
- **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 21 of 48 images use legacy formats
- **[WARNING]** 2 above-fold image(s) marked loading="lazy" (LCP anti-pattern) — Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://serebrokubachi.ru/wp-content/uploads/logo_serebrokubachi-1.png, https://serebrokubachi.ru/wp-content/uploads/ikonka-bulavki-2.png.webp.
- **[INFO]** 1 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://serebrokubachi.ru/wp-content/uploads/nabor-stolovyh-priborov-1-283x318.webp.

### 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, 75 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]** 2 nameserver(s) configured
- **[PASS]** 3 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 75 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (C — 55/100)

*Zone signed but parent has no DS record*

- **[WARNING]** DNSSEC keys published but parent zone has no DS record — The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.

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

*1/1 IPs match cert SAN*

- **[PASS]** PTR for 193.247.73.16 matches certificate SAN: www.serebrokubachi.ru

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

*Mean 47ms across 3 resolvers (spread 44ms)*

- **[PASS]** Google: 27ms
- **[PASS]** Cloudflare: 44ms
- **[PASS]** Quad9: 71ms

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

*No redirects — direct access*

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

### IPv6 Readiness (C — 60/100)

*No IPv6 support*

- **[INFO]** No IPv6 (AAAA) records found — IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 4 URLs*

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

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

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

- **[CRITICAL]** HTTP version does not redirect to HTTPS

### Domain Intelligence

*Domain intelligence data not available*


---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (B — 80/100)

*No consent signals detected*

- **[WARNING]** No privacy policy found (page links and common paths checked) — No link matching the privacy-policy vocabulary was found in the rendered page, and the common privacy-policy paths returned nothing. A privacy policy page is recommended for transparency and may be legally required.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

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

*No consent-UX depth issues detected*

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

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

*2 known tracker(s) detected*

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

tag-manager: Google Tag Manager | analytics: Google Analytics 4

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

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

*Lang attribute present*

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

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

*No hreflang tags on this page*

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

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (D — 50/100)

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

- **[INFO]** GDPR Article 13 disclosures not assessed (policy language: ru-RU) — The privacy policy appears to be written in "ru-RU", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate.

### Third-Party Trackers (C — 55/100)

*3 trackers detected*

- **[INFO]** 3 third-party trackers detected — Found 2 analytics, 0 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 3 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

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

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

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

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

- **[PASS]** No cookies set on the page response

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*0 of 7 expected legal pages detected*

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

### Copyright Notice (A+ — 100/100)

*Copyright 2026 © SerebroKubachi*

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

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

*2 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]** 2 third-party services across 2 categories — 2 third-party services detected across 2 categories: Analytics (1), Tag Management (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.

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

*0 compliance badge(s) detected*

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

---

## Availability

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

*No CDN (document or assets)*

- **[WARNING]** No CDN (document or assets) — Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (F — 30/100)

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

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

*No status page link detected*

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

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

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

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

### Health Check Endpoint (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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

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

*6 landmarks*

- **[PASS]** <main> landmark present
- **[WARNING]** Multiple <main> landmarks (2 found) — A page should have only one <main> landmark.
- **[PASS]** 2 <nav> landmark(s) found
- **[WARNING]** 1 of 2 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[PASS]** Skip navigation link present

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

*18 headings*

- **[PASS]** Single H1 present

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

*All 18 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 48 images OK*

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

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

*All 5 controls labeled*

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

### Link & Button Quality (A+ — 97/100)

*161 links, 8 buttons — all OK*

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

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

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

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

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

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

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

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

*4/5 eligible field(s) missing autocomplete or inputmode*

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

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

*Lang attribute set to "ru-RU"*

- **[PASS]** <html lang="ru-RU"> 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 (B — 90/100)

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

- **[INFO]** 3 tap target(s) too small or too close to neighbors — WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

### Mobile-Readable Font Sizes (B — 90/100)

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

- **[INFO]** 13 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.0px ("8 (906) 056-00-55"); <a> 11.0px ("Заказать звонок"); <span> 10.5px ("Доставка"); <span> 10.5px ("и оплата"); <a> 11.0px ("Смотреть все →").

---

## UX

### 404 Error Page (C — 55/100)

*Could not test*

- **[INFO]** 404 page could not be tested — The 404 page check encountered an error. This may be due to a timeout or network issue.

### Favicon & Branding (B — 70/100)

*4 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 (D — 40/100)

*Not found*

- **[INFO]** No web manifest found — No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

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

*No PWA depth issues detected*

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

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

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

*No print styles*

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

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

*1 navigation pattern(s)*

- **[PASS]** Skip navigation link detected
- **[PASS]** 2 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 (A+ — 100/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200

### Meta Tags (A — 90/100)

*Title: 67 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 67 characters — may be truncated in search results
- **[INFO]** Meta description is 223 characters — truncated on mobile (~160 char limit)
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

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

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

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

*1239 words, Very Easy*

- **[PASS]** Page has 1239 words — good depth for search engines
- **[INFO]** Reading level: Very Easy (grade 4)

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

*160 internal, 1 external*

- **[PASS]** 160 internal links (99%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 160 internal / 1 external links

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

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

*Sitemap updated within 90 days (4/4 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: today

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

*No sitemap-vs-robots conflicts detected*

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

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

*Sitemap structure / size look healthy (4 URLs, 797 bytes)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*0.30g CO2 per view*

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

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

*Unknown*

- **[INFO]** Hosting provider could not be identified — Without knowing the provider, we cannot determine their energy sourcing. Check with your hosting provider about their renewable energy commitments.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*96% cached*

- **[PASS]** 96% reduction on repeat visits — Returning visitors download only 44 KB (vs 1087 KB first visit). 98 of 99 resources are served from browser cache, saving 0.29g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.30g)

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

*20th percentile*

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

### Transfer Efficiency (B — 80/100)

*84% efficient*

- **[INFO]** Transfer efficiency: 84% — An estimated 173 KB (16%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 173 KB of unused JavaScript. This wasted data produces 0.05g 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/cabd0116-0ac9-4ab7-8f30-acaf7e80b995*