# BeaverCheck Audit Report — https://fps.agency

**Date:** August 19, 2026  
**URL:** https://fps.agency  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/7257da0a-abd9-4cb5-af9c-a8873a22559a

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** HSTS header is missing — Security > Security Headers
3. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
4. **[CRITICAL]** Page weighs 9.0 MB (7.4 MB transferred) — Performance > Page Weight Budget
5. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 40 |
| Accessibility | 82 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*3 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.
- **[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 85 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)

*1 cookies analyzed, 3 checks passed*

- **[PASS]** Cookie '__cf_bm' has the Secure flag
- **[PASS]** Cookie '__cf_bm' has the HttpOnly flag
- **[PASS]** Cookie '__cf_bm' has SameSite=None

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

*All 1 cookie(s) pass hygiene checks*

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

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a2d50172ac08c02a-GRU

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

*No new-tab links found -- no tabnabbing surface*

- **[PASS]** No new-tab links present

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

*25 inline style attribute(s) detected*

- **[WARNING]** 25 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. 25 inline style(s) is moderate. Affected element types include: div. 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)

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

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

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

Missing SRI on (first 5 examples):
  - https://www.googletagmanager.com/gtag/js?id=G-EEMN405TPT&cx=c&gtm=4e68h1
  - https://cdn-cookieyes.com/client_data/5d75e544ba393034198faee3/script.js
  - //www.googletagmanager.com/gtm.js?id=GTM-KZR6W3C
  - https://www.fps.agency/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=6.0.2
  - https://www.fps.agency/wp-content/themes/fps22/style.css?ver=1.17.1

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

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

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

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

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

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

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

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

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

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

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

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

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

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

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

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

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

*1 software version(s) disclosed in HTML*

- **[WARNING]** 1 software version(s) disclosed in HTML: WordPress 7.0.4 — 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 14 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 cdn-cookieyes.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 www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.jsdelivr.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn-cookieyes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.fps.agency lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

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

*No known vulnerabilities*

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

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

*No exposures*

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

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

*no DMARC, SPF: ~all, DKIM*

- **[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.
- **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).
- **[PASS]** DKIM configured (selectors: google)
- **[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 (F — 0/100)

*7.4 MB transferred, 120 requests*

- **[CRITICAL]** Page weighs 9.0 MB (7.4 MB transferred)
- **[WARNING]** Images are 6.9 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** 120 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 1.6 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 (7.4 MiB of 7.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 (C — 60/100)

*88 images, 0 KB saveable*

- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2025/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2025/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2025/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2022/12/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2025/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/04/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2023/01/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/05/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.fps.agency/wp-content/uploads/2024/11/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*6031ms total JS execution*

- **[WARNING]** https://www.fps.agency/: 3110ms CPU time
- **[WARNING]** Unattributable: 1237ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-KZR...: 501ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-EEMN...: 452ms CPU time
- **[WARNING]** https://www.fps.agency/wp-content/themes/fps22/js/...: 289ms CPU time
- **[WARNING]** Third-party scripts: 4794ms (79% of total)

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

*1 fonts (30 KB)*

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

### JS Bundles (B — 80/100)

*12 scripts, 134 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-EEMN...: 74 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-KZR...: 60 KB unused (43%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 134 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)

*3 hints, 0 missing preconnects*

- **[PASS]** Page uses 3 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.

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

*Main response served uncompressed*

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

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

*LCP preload audit not available*

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

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=0 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate

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

*120 resources · 7.4 MB · 134 KB savings available*

- **[WARNING]** Page weight 7.4 MB exceeds 1 MB target by 6.4 MB
- **[INFO]** ~134 KB of savings available
- **[WARNING]** 119 third-party resources (100% of weight)
- **[INFO]** 14 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


### JavaScript Blocking (B — 70/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 5 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 6.0 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 (C — 75/100)

*126 links checked, 121 healthy, 5 broken*

- **[CRITICAL]** 121 of 126 links are healthy
- **[WARNING]** Broken link: https://fonts.googleapis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://fonts.gstatic.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.fps.agency/feed/ — Found in <link href>. Get "https://www.fps.agency/feed/": context deadline exceeded
- **[CRITICAL]** Broken link: https://www.instagram.com/fps_agency/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.linkedin.com/company/fps-lab-agency — Found in <a href>. Returns HTTP 429.

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

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

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

### Open Graph (B — 85/100)

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

- **[WARNING]** Missing og:image — The og:image tag provides a preview image for social sharing.

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

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

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

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

*1 JSON-LD block(s) declaring 4 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]** 4 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

BreadcrumbList, Organization, 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 — 30/100)

*6 issues found across 56 images*

- **[WARNING]** 51 images significantly larger than display size — Resizing to display dimensions could save approximately 1166 KB.
- **[WARNING]** 51 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 56 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 51 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[WARNING]** Total image weight: 1206 KB (1.2 MB) — Consider compressing images, using modern formats, and serving appropriately sized images.
- **[INFO]** 4 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://www.fps.agency/wp-content/uploads/2026/08/ai-marketing-1024x608.jpg, https://www.fps.agency/wp-content/uploads/2025/10/migliori-agenzie-seo.jpg, https://www.fps.agency/wp-content/uploads/2026/07/prompt-marketing-1024x510.jpg (+1 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*1 A records, 438 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]** 5 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[WARNING]** DNS resolution is slow (438 ms) — Slow DNS adds latency to every page load. Consider a faster DNS provider.

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

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

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

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

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

### Reverse DNS (C — 60/100)

*0/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 162.159.134.42: lookup 162.159.134.42: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (C — 65/100)

*Mean 226ms across 3 resolvers (spread 46ms)*

- **[PASS]** Cloudflare: 210ms
- **[PASS]** Quad9: 212ms
- **[PASS]** Google: 256ms

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

*1 redirect(s), 3464 ms total*

- **[PASS]** Single redirect
- **[INFO]** WWW normalization redirect
- **[WARNING]** Redirect overhead: 3464 ms total

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

*no robots.txt, no sitemap*

- **[INFO]** No robots.txt found — robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
- **[INFO]** No sitemap.xml found — A sitemap helps search engines discover and index your pages more efficiently.

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

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

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

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

*fps.agency — via Server Plan Srl, 6 years, 7 months old, hosted on Cloudflare*

- **[PASS]** Domain registered until Feb 18, 2027 (6 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: Server Plan Srl
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
- **[PASS]** Hosting: Cloudflare

---

## Compliance

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

*No testable criteria*


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

*CookieYes detected, privacy policy found*

- **[PASS]** Privacy policy link found
- **[INFO]** No terms of service link detected
- **[PASS]** Consent banner detected (CookieYes)
- **[PASS]** 1 essential cookie(s) on initial load — no consent required
- **[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.

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

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

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

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

*3 trackers detected*

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

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

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

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

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*1 of 7 expected legal pages detected*

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

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

*No copyright notice detected*

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

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: Consent management platform detected: cookieyes.com; Text mentions: gdpr; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*3 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 3 third-party services across 3 categories — 3 third-party services detected across 3 categories: Analytics (1), Tag Management (1), CDN (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.
- **[INFO]** Cloudflare (CDN) — Detected via cookie name. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. Data Processing Agreement available.

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

*1 compliance badge(s) detected*

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

---

## Availability

### CDN & Delivery (A — 85/100)

*Cloudflare (DYNAMIC)*

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

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

*public, max-age=0, s-maxage=900*

- **[PASS]** Cache-Control header is set
- **[PASS]** CDN TTL: 15 minutes (s-maxage=900)
- **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators.

### 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: 404, /health: 404, /healthz: connection error, /ping: 404, /status: 404.

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

*Cache state: DYNAMIC*

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

---

## Accessibility

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

*12 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 8 <nav> landmark(s) found
- **[WARNING]** 7 of 8 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[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 — 70/100)

*34 headings*

- **[CRITICAL]** No H1 heading found — Every page should have one H1 that describes the page content.
- **[WARNING]** 1 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

*All 34 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 53 images OK*

- **[PASS]** 53 image(s) with good alt text

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

*1 of 6 controls have issues*

- **[CRITICAL]** 1 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[PASS]** 5 control(s) properly labeled

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

*86 issue(s) across 142 links and 2 buttons*

- **[CRITICAL]** 85 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[CRITICAL]** 1 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 57 link(s) with descriptive text

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

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

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

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

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

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

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

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

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

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

*Lang attribute set to "it-IT"*

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

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

*No explicit tabindex attributes found*

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

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

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

### Mobile-Readable Font Sizes (C — 75/100)

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

- **[WARNING]** 14 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <button> 8.7px ("Personalizza"); <button> 8.7px ("Rifiuta"); <button> 8.7px ("Accetta"); <div> 8.7px ("Chi siamo"); <p> 8.7px ("Aiutiamo persone e imprese a trovare la ...").

---

## UX

### 404 Error Page (B — 70/100)

*HTTP 404, custom page*

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

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

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

*Valid manifest*

- **[PASS]** Name present: FpS
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*1 PWA signal(s) surfaced*

- **[INFO]** Manifest has no maskable icon — Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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

*Theme color only*

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

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

*No print styles*

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

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

*No navigation patterns*

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

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

*2 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

## SEO

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (51 chars) is optimal
- **[PASS]** Meta description length (136 chars) is optimal

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

*1040 words, Very Difficult*

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

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

*70 internal, 72 external*

- **[PASS]** 70 internal links (49%)
- **[WARNING]** Only 40% of links use descriptive anchor text — Generic text like 'click here' wastes an opportunity to tell search engines what the linked page is about.
- **[INFO]** 70 internal / 72 external links

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

*53 images, 53 descriptive filenames*

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

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

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

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (C — 75/100)

*No sitemap.xml found*

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

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

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

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

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

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

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*1.76g CO2 per view*

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

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

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Kinsta: Verified by the Green Web Foundation
- **[INFO]** Cloudflare: 100% renewable energy for global network since 2019
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 21 KB (vs 7602 KB first visit). 119 of 120 resources are served from browser cache, saving 1.75g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 1.76g)

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

*83th percentile*

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

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

*98% efficient*

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

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

*6 font weights loaded across 1 famil(y/ies)*

- **[INFO]** 6 font weights loaded -- review whether all are used — 5+ weights for a single page is often more than needed. Compare against the actual font-weight CSS rules in your stylesheets; trim weights that aren't applied to any element. Affected families: Dosis.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/7257da0a-abd9-4cb5-af9c-a8873a22559a*