# BeaverCheck Audit Report — https://ukrspecsystems.ua

**Date:** September 20, 2026  
**URL:** https://ukrspecsystems.ua  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/7ff65cbc-fee8-4f2f-8cd2-f3f57061ccd9

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Page weighs 15.8 MB (8.4 MB transferred) — Performance > Page Weight Budget
3. **[CRITICAL]** 10 button(s) with no accessible text — Accessibility > Link & Button Quality
4. **[CRITICAL]** No <main> landmark found — Accessibility > Landmark Structure
5. **[CRITICAL]** No H1 heading found — Accessibility > Heading Hierarchy

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 27 |
| Accessibility | 90 |
| Best Practices | 96 |
| SEO | 92 |

---

## Security

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

*3 of 10 headers properly configured*

- **[WARNING]** HSTS is enabled but max-age is short (2592000s, should be >= 31536000s) — The header is present and enforced, so first-visit protection is already in place; a short max-age just means the browser forgets it sooner. Set max-age to at least 31536000 (1 year).
- **[PASS]** X-Content-Type-Options is properly configured
- **[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, 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 35 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 1 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 32 new-tab link(s) carry rel=noopener*

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

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

*4% SRI adoption (1/22 third-party resources)*

- **[WARNING]** SRI adoption: 1/22 third-party resources protected (4%) — Of 22 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (4%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://www.googletagmanager.com/gtag/destination?id=AW-590550794&cx=c&gtm=4e69g1
  - https://www.google-analytics.com/analytics.js
  - https://www.googletagmanager.com/gtag/js?id=G-8ELM7F4F04&cx=c&gtm=4e69g1
  - https://connect.facebook.net/signals/config/1359747677958660?v=2.9.403&r=stable&domain=ukrspecsystems.com&hme=ecef7557496abce7ebfd30d9fec7f02b78383ffbf3f454783aea671f0dea1dfc&ex_m=117%2C234%2C168%2C27%2C81%2C82%2C160%2C77%2C76%2C11%2C178%2C101%2C20%2C152%2C140%2C46%2C84%2C89%2C148%2C173%2C180%2C8%2C4%2C5%2C7%2C6%2C3%2C102%2C114%2C32%2C17%2C31%2C18%2C33%2C34%2C35%2C37%2C55%2C161%2C86%2C125%2C22%2C24%2C51%2C47%2C49%2C48%2C94%2C103%2C107%2C123%2C159%2C162%2C53%2C124%2C29%2C26%2C132%2C78%2C43%2C164%2C163%2C165%2C156%2C154%2C30%2C42%2C66%2C122%2C175%2C79%2C21%2C127%2C92%2C75%2C23%2C96%2C97%2C129%2C95%2C150%2C149%2C153%2C108%2C174%2C177%2C41%2C56%2C126%2C54%2C182%2C109%2C181%2C201%2C248%2C83%2C262%2C261%2C260%2C14%2C25%2C28%2C40%2C62%2C116%2C68%2C10%2C72%2C110%2C111%2C112%2C118%2C143%2C38%2C36%2C145%2C146%2C147%2C142%2C141%2C169%2C85%2C172%2C170%2C171%2C57%2C67%2C136%2C19%2C176%2C52%2C311%2C312%2C313%2C310%2C326%2C351%2C241%2C230%2C69%2C231%2C229%2C354%2C345%2C59%2C242%2C120%2C144%2C91%2C134%2C61%2C133%2C139%2C138%2C65%2C73%2C71%2C166%2C87%2C88%2C128%2C44%2C39%2C60%2C63%2C113%2C179%2C1%2C137%2C16%2C135%2C12%2C2%2C64%2C104%2C15%2C74%2C70%2C131%2C100%2C99%2C184%2C185%2C105%2C106%2C9%2C115%2C183%2C58%2C157%2C98%2C90%2C80%2C130%2C119%2C50%2C158%2C0%2C93%2C151%2C155%2C167%2C45%2C121%2C13%2C186
  - https://connect.facebook.net/en_US/fbevents.js

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

*1 CORS depth signal(s) detected*

- **[INFO]** CORS allows any origin (`Access-Control-Allow-Origin: *`) — Any website can fetch this URL via JavaScript and read the response body. Acceptable for genuinely public APIs (e.g. CDN-served static assets). Risky if the URL returns user-specific or session-derived data, since other origins can scrape it via the user's browser without needing credentials. Narrow Allow-Origin to a specific origin allow-list when the response is sensitive.

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

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

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

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

### HTML Version Disclosure (B — 90/100)

*1 generator tag(s) without version info*

- **[INFO]** 1 generator tag(s) without version info: Weblium, effortless website builder — Generator tags reveal the CMS / build tool but no version specifics. Attackers can't directly cross-reference CVEs but can probe known weaknesses for the named platform. Removing the tag entirely is preferable; most CMSes have a one-config-flag option to suppress it.

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

*1 of 22 external resources have SRI*

- **[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.google-analytics.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 connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from connect.facebook.net 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 snap.licdn.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 link from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from leadbooster-chat.pipedrive.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ajax.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdnjs.cloudflare.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 wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from wl-apps.yourwebsite.life lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from webforms.pipedrive.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from static.cloudflareinsights.com has SRI protection

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

*No known vulnerabilities*

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

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

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

### Permissions-Policy (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 (C — 60/100)

*Origin: **

- **[INFO]** Access-Control-Allow-Origin: * — unrestricted — Any website can read this resource's response. Appropriate for public APIs but not for user-specific content.
- **[INFO]** Origin reflection not testable with a single request — Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header.

---

## Performance

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

*8.4 MB transferred, 118 requests*

- **[CRITICAL]** Page weighs 15.8 MB (8.4 MB transferred)
- **[WARNING]** Images are 5.1 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 2.5 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** CSS is 537 KB — consider purging unused styles — Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.
- **[WARNING]** 118 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 1.8 g CO2 per page load

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

*100% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 100% of page weight (8.4 MiB of 8.4 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 — 70/100)

*38 images, 0 KB saveable*

- **[WARNING]** https://res2.weblium.site/res/5dfe007809892000216e... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*10576ms total JS execution*

- **[WARNING]** https://ukrspecsystems.com/: 2182ms CPU time
- **[WARNING]** https://ukrspecsystems.com/site/6aaa691de0ae6081a3...: 2008ms CPU time
- **[WARNING]** Unattributable: 1441ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-8ELM...: 751ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/destination?...: 714ms CPU time
- **[WARNING]** Third-party scripts: 9135ms (86% of total)

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

*5 fonts (183 KB)*

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

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

*35 scripts, 730 KB unused*

- **[WARNING]** https://ukrspecsystems.com/site/6aaa691de0ae6081a3...: 168 KB unused (51%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://cdn.lon-2.pipedriveassets.com/leadbooster-...: 142 KB unused (62%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-M5C...: 76 KB unused (48%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-8ELM...: 73 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/destination?...: 68 KB unused (42%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 730 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)

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

### Document Compression (C — 70/100)

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

### Asset Compression (A — 90/100)

*1 of 2 asset hosts still on gzip*

- **[INFO]** wl-apps.yourwebsite.life serves assets with gzip; brotli would be ~20% smaller (assets: 12) — Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
- **[PASS]** www.googletagmanager.com serves assets with brotli (assets: 5)

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

*1 server-response signal(s) detected*

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

*118 resources · 8.4 MB · 730 KB savings available*

- **[WARNING]** Page weight 8.4 MB exceeds 1 MB target by 7.4 MB
- **[INFO]** ~730 KB of savings available
- **[WARNING]** 117 third-party resources (100% of weight)
- **[INFO]** 15 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

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

*No third-party resources detected*


### JavaScript Blocking (A — 90/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** Total JS execution time is 10.6 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 — 88/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 9 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (B — 80/100)

*89 links checked, 85 healthy, 4 broken*

- **[CRITICAL]** 85 of 89 links are healthy
- **[WARNING]** Broken link: https://www.googletagmanager.com/gtm.js?id=GTM-WG3C9GG — Found in <script src>. Returns HTTP 404.
- **[WARNING]** Broken link: https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/g... — Found in <link href>. Get "https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/google-fonts-5c2dfa623dbc4a0023e12261.css": net/http: HTTP/1.x transport connection broken: too many transfer encodings: ["chunked" "chunked"]
- **[WARNING]** Broken link: https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/c... — Found in <link href>. Get "https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/core-theme-5c2dfa623dbc4a0023e12261.css": net/http: HTTP/1.x transport connection broken: too many transfer encodings: ["chunked" "chunked"]
- **[WARNING]** Broken link: https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/m... — Found in <script src>. Get "https://ukrspecsystems.ua/site/6aaa691de0ae6081a355dc95/main.js": net/http: HTTP/1.x transport connection broken: too many transfer encodings: ["chunked" "chunked"]

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

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

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

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

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

- **[INFO]** og:title is short (14 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[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 (A — 90/100)

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

- **[WARNING]** Missing required property "name" for Organization — The "name" property is required for the Organization schema type.
- **[INFO]** Missing recommended property "url" for Organization — Adding "url" can improve how search engines display your content.
- **[INFO]** Missing recommended property "logo" for Organization — Adding "logo" can improve how search engines display your content.
- **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content.
- **[PASS]** 2 JSON-LD blocks found

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

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

- **[PASS]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

LocalBusiness, Organization

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

*5 issues found across 29 images*

- **[WARNING]** 21 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 26 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 26 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** 1 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://res2.weblium.site/res/5dfe007809892000216e9925/673373f7f3887c2c855c8752_optimized_495.webp.
- **[INFO]** 10 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://res2.weblium.site/res/5dfe007809892000216e9925/65e5c8007a8ef1000f90f03b_optimized, https://res2.weblium.site/res/5dfe007809892000216e9925/61a6910512003700235b5041_optimized_1473_e1554x930-40x24, https://res2.weblium.site/res/5dfe007809892000216e9925/679b4a3d8177f1610239389c_optimized_1082 (+7 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

### DNS Records (A — 90/100)

*1 A records, 22 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]** 4 nameserver(s) configured
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 22 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

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

*0/1 IPs match cert SAN*

- **[INFO]** PTR for 35.187.82.108 does not match any cert SAN: 108.82.187.35.bc.googleusercontent.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

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

*Mean 9ms across 3 resolvers (spread 9ms)*

- **[PASS]** Quad9: 6ms
- **[PASS]** Cloudflare: 8ms
- **[PASS]** Google: 15ms

### Redirect Chain (B — 70/100)

*1 redirect(s), 1427 ms total*

- **[PASS]** Single redirect
- **[INFO]** Uses 302 (temporary) redirect — If permanent, use 301 instead.
- **[WARNING]** Redirect overhead: 1427 ms total
- **[INFO]** Cross-domain redirect detected

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

*No IPv6 support*

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

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

*robots.txt present, sitemap with 2 URLs*

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

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

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

- **[PASS]** www/non-www redirect configured correctly (preferred: non-www)
- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*ukrspecsystems.ua — via BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD', 3 years, 1 months old, hosted on Google Cloud*

- **[PASS]** Domain registered until Aug 31, 2027 (11 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD'
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
- **[PASS]** Hosting: Google Cloud

---

## Compliance

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

*No testable criteria*


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

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

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

*No consent-UX depth issues detected*

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

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

*5 known tracker(s) detected*

- **[PASS]** 5 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 (UA), Google Analytics 4 | marketing: Meta Pixel, LinkedIn Insight

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

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

*Lang attribute present*

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

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

*1 hreflang issue(s) across 2 tag(s)*

- **[INFO]** No `x-default` hreflang tag — Google recommends including `<link rel="alternate" hreflang="x-default" href="...">` so search engines have a fallback URL for users whose language / region doesn't match any specific hreflang entry. Typically points to a language-selection page or your default locale.

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

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

### GDPR Article 13 Disclosures (F — 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)

*6 trackers detected*

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

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

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

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

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*2 of 7 expected legal pages detected*

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

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

*© 2026 All Rights Reserved Terms of Use and Privacy Polic*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 All Rights Reserved Terms of Use and Privacy Polic

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

*4 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]** 4 third-party services across 3 categories — 4 third-party services detected across 3 categories: Analytics (1), Tag Management (1), Advertising (2). 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.
- **[INFO]** Facebook Pixel (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, User behavior, Ad targeting. Privacy policy: https://www.facebook.com/privacy/policy. Data Processing Agreement available.
- **[INFO]** LinkedIn Insight (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, Ad targeting, Professional demographics. Privacy policy: https://www.linkedin.com/legal/privacy-policy. Data Processing Agreement available.

### Compliance Badges (B — 70/100)

*1 compliance badge(s) detected*

- **[PASS]** TRUSTe / TrustArc badge detected — Found via body text: 'truste'. Note: the presence of a badge does not verify the certification is current or valid.

---

## Availability

### CDN & Delivery (C — 65/100)

*Assets on Google Cloud CDN (host blog-api.getblog.app, 3 assets); document served directly from origin*

- **[WARNING]** Document not behind existing CDN (Google Cloud CDN serves the assets) — The page's subresources are delivered by Google Cloud CDN (blog-api.getblog.app, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
- **[PASS]** Assets on Google Cloud CDN: blog-api.getblog.app (assets: 3)

### 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 (B — 75/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.
- **[WARNING]** HSTS max-age is short: 30 days — HSTS max-age should be at least 1 year (31536000 seconds).
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

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

*14 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[PASS]** 6 <nav> landmark(s) found
- **[PASS]** All <nav> elements are properly labeled
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (B — 75/100)

*12 headings*

- **[CRITICAL]** No H1 heading found — Every page should have one H1 that describes the page content.

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

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

- **[INFO]** 2 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

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

*25 of 29 images have issues*

- **[WARNING]** 25 image(s) with generic alt text
- **[PASS]** 4 image(s) with good alt text

### Form Accessibility (B — 84/100)

*2 of 2 controls have issues*

- **[WARNING]** 2 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.

### Link & Button Quality (C — 68/100)

*10 issue(s) across 125 links and 22 buttons*

- **[WARNING]** 32 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 10 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 93 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 (D — 60/100)

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

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

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

*Lang attribute set to "en"*

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

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

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

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

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

*All 2 iframe(s) have descriptive titles*

- **[PASS]** All 2 iframe(s) have title attributes

### 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 72 visible text node(s) render at >= 12 CSS pixels*

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

---

## UX

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

*HTTP 404, custom page*

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

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

*7 icon(s) detected*

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

*1 PWA signal(s) surfaced*

- **[PASS]** Service worker registration detected — The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

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

*Dark mode detected*

- **[PASS]** color-scheme meta tag present — The site declares support for light and dark color schemes via <meta name='color-scheme'>.
- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[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 — 20/100)

*No navigation patterns*

- **[PASS]** 6 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)
- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

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

*1 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

---

## SEO

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

*Properly configured*

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

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

*Title: 14 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 14 characters — consider expanding
- **[INFO]** Meta description is 195 characters — truncated on mobile (~160 char limit)

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

*739 words, Difficult*

- **[PASS]** Page has 739 words of content
- **[INFO]** Text-to-HTML ratio is 1% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Difficult (grade 14)

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

*91 internal, 34 external*

- **[PASS]** 91 internal links (73%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 91 internal / 34 external links

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

*7 images, 4 descriptive filenames*

- **[INFO]** 3 image(s) have hash/generic 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 (2/2 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: 4 days ago

### 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 (2 URLs, 407 bytes)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (F — 30/100)

*2.39g CO2 per view*

- **[CRITICAL]** 2.39g CO2 per page view — This page transfers 8.4 MB, producing an estimated 2.39g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.44g, network 0.41g, end-user device 1.54g.
- **[INFO]** At 10,000 monthly views: 287.0 kg CO2/year — With 10,000 page views per month, this page would generate approximately 287.0 kg of CO2 annually — equivalent to charging 35880 smartphones.

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

*Unknown*

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

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

*99% cached*

- **[PASS]** 99% reduction on repeat visits — Returning visitors download only 115 KB (vs 8649 KB first visit). 115 of 118 resources are served from browser cache, saving 2.36g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.03g CO2 (first visit: 2.39g)

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

*95th percentile*

- **[WARNING]** 2.39g CO2 — above the median website (0.60g) — Heavier than an estimated 5% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 95th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

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

*92% efficient*

- **[PASS]** Transfer efficiency: 92% — Only 729 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/7ff65cbc-fee8-4f2f-8cd2-f3f57061ccd9*