# BeaverCheck Audit Report — https://www.elmivo.co.uk

**Date:** November 18, 2026  
**URL:** https://www.elmivo.co.uk  
**Overall Grade:** B (86/100)  
**Report:** https://beavercheck.com/results/afd8e25d-b377-4cc3-9344-b305429394cd

## Top Findings

1. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
2. **[WARNING]** 2 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
3. **[WARNING]** 20 third-party resources (55% of weight) — Performance > Page Weight Inventory
4. **[WARNING]** 68 inline style attribute(s) detected — Security > CSP Inline-Style Readiness
5. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 77 |
| Accessibility | 93 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*8 of 10 headers properly configured*

- **[PASS]** HSTS is enabled with preload
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[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 not present
- **[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 (B — 80/100)

*8 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[PASS]** No 'unsafe-eval' in script source
- **[PASS]** No wildcard in script source
- **[PASS]** object-src is set to 'none'
- **[PASS]** base-uri is properly restricted
- **[PASS]** frame-ancestors directive is set
- **[PASS]** form-action directive is set
- **[PASS]** upgrade-insecure-requests is enabled

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

*TLS 1.3, 8 checks passed*

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

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

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

*No security.txt file found*

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

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

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

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

### CSP Inline-Style Readiness (D — 60/100)

*68 inline style attribute(s) detected*

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

### Trusted Types (XSS Sink Hardening) (B — 95/100)

*Trusted Types not enabled*

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Missing SRI on (first 3 examples):
  - https://www.googletagmanager.com/gtag/js?id=AW-18521544156&cx=c&gtm=4e6bg2
  - https://connect.facebook.net/en_US/fbevents.js
  - https://www.googletagmanager.com/gtag/js?id=G-PW16P8SFZQ

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

*30% high-risk feature coverage (3/10)*

- **[WARNING]** Permissions-Policy covers 3/10 high-risk features (30%) — The Permissions-Policy header explicitly declares policies for 3/10 high-risk features.

Covered: camera, microphone, geolocation

Not declared (default-allow): payment, usb, serial, midi, accelerometer, gyroscope, magnetometer

The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

### Referrer-Policy Strictness (A+ — 100/100)

*Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)*

- **[PASS]** Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin — The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

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

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

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

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

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

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 3 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 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.

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

*5 directives, 2 missing*

- **[INFO]** camera=(self)
- **[INFO]** xr-spatial-tracking=(self)
- **[PASS]** microphone=() — blocked for all origins
- **[PASS]** geolocation=() — blocked for all origins
- **[PASS]** interest-cohort=() — blocked for all origins
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (B — 76/100)

*1.3 MB transferred, 63 requests*

- **[PASS]** Page weighs 3.3 MB (1.3 MB transferred)
- **[WARNING]** JavaScript is 618 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** 63 HTTP requests
- **[INFO]** Estimated 0.28 g CO2 per page load

### Third-Party Impact (B — 70/100)

*55% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 55% of page weight (753.1 KiB of 1.3 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

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

*All text resources are compressed*

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

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

*14 images, 0 KB saveable*

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

### JS Execution Cost (D — 40/100)

*2089ms total JS execution*

- **[WARNING]** https://www.elmivo.co.uk/_next/static/chunks/3kmoz...: 508ms CPU time
- **[WARNING]** https://www.elmivo.co.uk/: 444ms CPU time
- **[WARNING]** Unattributable: 318ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-185...: 279ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtag/js?id=G-PW16...: 236ms CPU time
- **[INFO]** Third-party scripts: 636ms (30% of total)

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

*3 fonts (120 KB)*

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

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

*15 scripts, 211 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-PW16...: 70 KB unused (36%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-185...: 69 KB unused (46%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://connect.facebook.net/en_US/fbevents.js: 47 KB unused (49%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.elmivo.co.uk/_next/static/chunks/3kmoz...: 24 KB unused (36%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 211 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)

*5 hints, 0 missing preconnects*

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

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

*HTTP/3 advertised via Alt-Svc*

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

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

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

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

### Asset Compression

*No text asset hosts to measure*

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

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

*LCP preload audit not available*

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

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

*Cache-Control present but without max-age*

- **[INFO]** Main HTML Cache-Control has no max-age: s-maxage=31536000

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[PASS]** `ETag` present -- conditional GET supported

### Page Weight Inventory (D — 50/100)

*63 resources · 1.3 MB · 211 KB savings available*

- **[WARNING]** Page weight 1.3 MB exceeds 1 MB target by 339 KB
- **[INFO]** ~211 KB of savings available
- **[WARNING]** 20 third-party resources (55% of weight)

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*1 JS blocking issue(s) detected*

- **[WARNING]** 2 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

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

*No CSS performance depth issues detected*

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

---

## Content Quality

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

*91 links checked, 91 healthy, 0 broken*

- **[PASS]** 91 of 91 links are healthy

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

- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.
- **[INFO]** Missing og:type — The og:type tag helps social platforms categorize the content.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.

### 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 "OnlineStore" — unable to validate specific properties

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

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

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

OnlineStore

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 30 images*

- **[WARNING]** 1 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 25 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 2 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** 4 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://d1roykkzkathu2.cloudfront.net/w96/q90/brand/elmivo-mark-v2.webp, https://d1roykkzkathu2.cloudfront.net/w828/q75/laxmi-150cm-sliding-wardrobe-sonoma-oak-room.webp, https://d1roykkzkathu2.cloudfront.net/w828/q75/venice-150cm-sliding-wardrobe-white-room.webp (+1 more).
- **[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://d1roykkzkathu2.cloudfront.net/w828/q75/florence-200cm-sliding-wardrobe-black-white-room.webp, https://d1roykkzkathu2.cloudfront.net/w828/q75/laxmi-150cm-sliding-wardrobe-sonoma-oak-room.webp, https://d1roykkzkathu2.cloudfront.net/w828/q75/venice-150cm-sliding-wardrobe-white-room.webp (+7 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)

*4 A records, 50 ms lookup*

- **[PASS]** Resolves to 4 IPv4 address(es)
- **[PASS]** Has 8 IPv6 (AAAA) record(s)
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[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: 50 ms

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

*CNAME points at managed service(s) — verify configuration*

- **[INFO]** CNAME targets AWS CloudFront — verify ownership — CNAME targets CloudFront. Distribution names are GUID-style so accidental re-registration is unlikely, but a deleted distribution will return errors. Verify the CloudFront distribution is still active.

### 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/12 IPs match cert SAN*

- **[INFO]** PTR for 65.8.202.123 does not match any cert SAN: server-65-8-202-123.mad56.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 65.8.202.53 does not match any cert SAN: server-65-8-202-53.mad56.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 65.8.202.111 does not match any cert SAN: server-65-8-202-111.mad56.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 65.8.202.119 does not match any cert SAN: server-65-8-202-119.mad56.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR lookup failed for 2600:9000:2091:c200:14:9b74:e740:93a1: lookup 2600:9000:2091:c200:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:a000:14:9b74:e740:93a1: lookup 2600:9000:2091:a000:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:3600:14:9b74:e740:93a1: lookup 2600:9000:2091:3600:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:6e00:14:9b74:e740:93a1: lookup 2600:9000:2091:6e00:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:e200:14:9b74:e740:93a1: lookup 2600:9000:2091:e200:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:6200:14:9b74:e740:93a1: lookup 2600:9000:2091:6200:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:7e00:14:9b74:e740:93a1: lookup 2600:9000:2091:7e00:14:9b74:e740:93a1: 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.
- **[INFO]** PTR lookup failed for 2600:9000:2091:3e00:14:9b74:e740:93a1: lookup 2600:9000:2091:3e00:14:9b74:e740:93a1: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

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

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

- **[PASS]** Quad9: 10ms
- **[PASS]** Google: 38ms
- **[PASS]** Cloudflare: 56ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (1 ms)*

- **[PASS]** IPv6 is configured and reachable at 2600:9000:2091:c200:14:9b74:e740:93a1, 2600:9000:2091:a000:14:9b74:e740:93a1, 2600:9000:2091:3600:14:9b74:e740:93a1, 2600:9000:2091:6e00:14:9b74:e740:93a1, 2600:9000:2091:e200:14:9b74:e740:93a1, 2600:9000:2091:6200:14:9b74:e740:93a1, 2600:9000:2091:7e00:14:9b74:e740:93a1, 2600:9000:2091:3e00:14:9b74:e740:93a1

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

*robots.txt present, sitemap with 49 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 49 entries
- **[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: www)
- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*elmivo.co.uk — via GoDaddy.com, LLC., 1 months old, hosted on AWS*

- **[PASS]** Domain registered until Sep 24, 2027 (10 months remaining)
- **[INFO]** Domain is only 1 months old — Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
- **[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: GoDaddy.com, LLC.
- **[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: AWS

---

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

*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):

analytics: Google Analytics 4 | marketing: Meta Pixel

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

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

*Lang attribute present*

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

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

*No hreflang tags on this page*

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

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

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

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

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 1 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 1 of 8 categories: Identity / contact details of the data controller. Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), 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 (B — 80/100)

*6 trackers detected*

- **[INFO]** 6 third-party trackers detected — Found 4 analytics, 1 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.

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

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacy, linked from footer.
- **[PASS]** Terms of Service detected — Found at /terms, 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.
- **[PASS]** Refund / Returns Policy detected — Found at /returns, linked from footer.
- **[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 Elmivo Furniture*

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

### 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 (moderate confidence) — Indicators suggesting GDPR may be relevant: Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*2 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 2 third-party services across 2 categories — 2 third-party services detected across 2 categories: Analytics (1), Advertising (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]** 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.

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

*0 compliance badge(s) detected*

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

---

## Availability

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

*Document and assets on AWS CloudFront*

- **[PASS]** Document is served via AWS CloudFront CDN (edge: MAD56-P6)
- **[PASS]** CDN cache status: Hit from cloudfront
- **[PASS]** Assets on AWS CloudFront: d1roykkzkathu2.cloudfront.net (assets: 30), cache Hit from cloudfront

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

*s-maxage=31536000*

- **[PASS]** Cache-Control header is set
- **[PASS]** CDN TTL: 52 weeks (s-maxage=31536000)
- **[PASS]** ETag present — enables conditional (304) responses

### 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+ — 100/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.
- **[PASS]** HSTS enabled (includeSubDomains, preload)
- **[PASS]** HSTS preload enabled
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

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

*Cache state: HIT*

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

---

## Accessibility

### Landmark Structure (A+ — 100/100)

*8 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 2 <nav> landmark(s) found
- **[PASS]** All <nav> elements are properly labeled
- **[PASS]** Skip navigation link present

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

*35 headings*

- **[PASS]** Single H1 present

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

*All 35 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 30 images OK*

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

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

*All 1 controls labeled*

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

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

*91 links, 30 buttons — all OK*

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

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

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

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

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

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

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

### Mobile Keyboard & Autofill (C — 75/100)

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

- **[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 "en-GB"*

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

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

- **[INFO]** 27 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Drawers"); <span> 11.0px ("Grooved"); <span> 11.0px ("Full mirror"); <span> 11.0px ("Slim"); <span> 11.0px ("Panelled").

---

## UX

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

*HTTP 404, custom page*

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

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

*4 icon(s) detected*

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

### Web Manifest (D — 40/100)

*Not found*

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

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

*No PWA depth issues detected*

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

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

*No dark mode signals*

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

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

*No print styles*

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

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

*1 navigation pattern(s)*

- **[PASS]** Skip navigation link detected
- **[PASS]** 2 navigation landmark(s) detected

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

*1 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

---

## SEO

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

*Properly configured*

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

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (48 chars) is optimal
- **[PASS]** Meta description length (156 chars) is optimal
- **[PASS]** Title and H1 are well-aligned

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

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

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

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

*1292 words, Standard*

- **[PASS]** Page has 1292 words — good depth for search engines
- **[INFO]** Text-to-HTML ratio is 3% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Standard (grade 10)

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

*85 internal, 6 external*

- **[PASS]** 85 internal links (93%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 85 internal / 6 external links

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

*30 images, 30 descriptive filenames*

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

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

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

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

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

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

*No sitemap-vs-robots conflicts in the URL sample*

- **[PASS]** All 5 sampled sitemap URLs are crawlable per robots.txt

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

*Sitemap structure / size look healthy (49 URLs, 9 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*0.38g CO2 per view*

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

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

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** AWS: Renewable energy varies by region; committed to 100% by 2025
- **[INFO]** AWS CloudFront: Renewable varies by edge location
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*97% cached*

- **[PASS]** 97% reduction on repeat visits — Returning visitors download only 40 KB (vs 1362 KB first visit). 62 of 63 resources are served from browser cache, saving 0.37g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.38g)

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

*27th percentile*

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

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

*85% efficient*

- **[INFO]** Transfer efficiency: 85% — An estimated 210 KB (15%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 210 KB of unused JavaScript. This wasted data produces 0.06g of unnecessary CO2 per page view.

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

*No detectable Google Fonts weights*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/afd8e25d-b377-4cc3-9344-b305429394cd*
