# BeaverCheck Audit Report — https://www.hornbach.se

**Date:** May 11, 2026  
**URL:** https://www.hornbach.se  
**Overall Grade:** B (82/100)  
**Report:** https://beavercheck.com/results/f6bb0437-8b8b-4334-bd87-05e80ac7a3ee

## Top Findings

1. **[CRITICAL]** Cookie 'hbMarketSession' is missing the Secure flag — Security > Cookie Security
2. **[CRITICAL]** 1 link(s) with no accessible text — Accessibility > Link & Button Quality
3. **[WARNING]** 113 HTTP requests — consider bundling or reducing — Performance > Page Weight Budget
4. **[WARNING]** 2 publicly-accessible JavaScript source map(s) — Security > Source Map Exposure
5. **[WARNING]** 3 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 50 |
| Accessibility | 100 |
| Best Practices | 100 |
| SEO | 92 |

---

## Security

### Security Headers (B — 70/100)

*6 of 10 headers properly configured*

- **[WARNING]** HSTS is missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP.
- **[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.
- **[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 — 70/100)

*2 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[WARNING]** default-src directive is missing — default-src provides a fallback for other directives. Set it to restrict default resource loading.
- **[INFO]** No script-src or default-src to check for 'unsafe-inline'
- **[INFO]** No script-src or default-src to check for 'unsafe-eval'
- **[INFO]** No script-src or default-src to check for wildcard
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[PASS]** frame-ancestors directive is set
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

### 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 72 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (C — 65/100)

*5 cookies analyzed, 9 checks passed*

- **[CRITICAL]** Cookie 'hbMarketSession' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'hbMarketSession' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'hbMarketSession' has SameSite=Lax
- **[PASS]** Cookie 'hbMarketCookie' has the Secure flag
- **[PASS]** Cookie 'hbMarketCookie' has the HttpOnly flag
- **[WARNING]** Cookie 'hbMarketCookie' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'hbUserSession' has the Secure flag
- **[WARNING]** Cookie 'hbUserSession' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'hbUserSession' has SameSite=Lax
- **[PASS]** Cookie 'dtCookieo26m5unv' has the Secure flag
- **[WARNING]** Cookie 'dtCookieo26m5unv' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'dtCookieo26m5unv' has SameSite=None
- **[PASS]** Cookie 'absearchvariant' has the Secure flag
- **[WARNING]** Cookie 'absearchvariant' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'absearchvariant' has SameSite=None

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

*All 5 cookie(s) pass hygiene checks*

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

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

*No WAF detected via response headers*

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

### security.txt (A — 85/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116)

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

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

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

### CSP Inline-Style Readiness (B — 90/100)

*8 inline style attribute(s) detected*

- **[INFO]** 8 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. 8 inline style(s) is low. Affected element types include: html, span, cms-hero-teaser, cms-project-module, cms-current-topic. 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 (D — 50/100)

*20% SRI adoption (1/5 third-party resources)*

- **[WARNING]** SRI adoption: 1/5 third-party resources protected (20%) — Of 5 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (20%) 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 4 examples):
  - https://cdn.trkkn.com/tracking-extension/4.1/gtmext.min.4.1.1.js?pid=trial_hornbach
  - https://www.googletagmanager.com/gtm.js?id=GTM-WWSVZZV&gtm=4e6562
  - https://www.googletagmanager.com/gtm.js?id=GTM-54PRXDGS
  - https://cdn.ablyft.com/s/22895057-657_prd_client_hornbach_se.js

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

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

*0% high-risk feature coverage (0/10)*

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

Covered: 

Not declared (default-allow): camera, microphone, geolocation, 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 (D — 60/100)

*2 publicly-accessible source map(s) -- full source code leaked*

- **[WARNING]** 2 publicly-accessible JavaScript source map(s) — Source maps (.js.map files) reveal the original source code -- variable names, comments, file structure, and sometimes secrets that were stripped from the bundled output. They're shipped to production by mistake almost universally; the standard fix is a build-tool config flag (Webpack: `devtool: false` or `'hidden-source-map'`; Vite: `build.sourcemap: false`; Next.js: `productionBrowserSourceMaps: false`). Once removed, audit your CDN/edge cache to evict any previously-cached .map URLs. Sample accessible URLs: https://www.hornbach.se/header/js/header.8e528c6a434cf3702354.js.map, https://www.hornbach.se/autocomplete/assets/autocomplete.79c197ddf69e3992ed42.js.map.

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

*No software-version disclosures in HTML*

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

### Open Redirect Surface (B — 90/100)

*1 link(s) carry redirect-shaped query parameter(s)*

- **[INFO]** 1 link(s) carry redirect-shaped query parameter(s) — Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.

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

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

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

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

*No risky subdomain names in certificate SANs*

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

---

## Advanced Security

### Subresource Integrity (D — 40/100)

*1 of 5 external resources have SRI*

- **[WARNING]** External script from cdn.trkkn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from dok.js-cdn.dynatrace.com has SRI protection
- **[WARNING]** External script from cdn.ablyft.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*

- **[PASS]** security.txt is present — good practice
- **[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 (C — 60/100)

*6 directives, 5 missing*

- **[INFO]** ch-ua=(self "https://*.hornbach.se")
- **[INFO]** ch-ua-full-version-list=(self "https://*.hornbach.se")
- **[INFO]** ch-ua-model=(self "https://*.hornbach.se")
- **[INFO]** ch-ua-mobile=(self "https://*.hornbach.se")
- **[INFO]** ch-ua-platform=(self "https://*.hornbach.se")
- **[INFO]** ch-ua-platform-version=(self "https://*.hornbach.se")
- **[INFO]** camera not restricted — Consider adding camera=() to block camera access from embedded content.
- **[INFO]** microphone not restricted — Consider adding microphone=() to block microphone access from embedded content.
- **[INFO]** geolocation not restricted — Consider adding geolocation=() to block geolocation access from embedded content.
- **[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 (D — 43/100)

*2.4 MB transferred, 113 requests*

- **[INFO]** Page weighs 8.8 MB (2.4 MB transferred)
- **[WARNING]** Images are 1.1 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 759 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 113 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.51 g CO2 per page load

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

*54% third-party, 0 ms blocking*

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

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

*All text resources are compressed*

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

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

*39 images, 0 KB saveable*

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

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

*6250ms total JS execution*

- **[WARNING]** https://www.hornbach.se/cms/static/stencil/hornbac...: 1959ms CPU time
- **[WARNING]** https://www.hornbach.se/: 1568ms CPU time
- **[WARNING]** Unattributable: 1025ms CPU time
- **[WARNING]** https://dok.js-cdn.dynatrace.com/jstag/193010ae318...: 645ms CPU time
- **[WARNING]** https://www.hornbach.se/cms/static/stencil/hornbac...: 318ms CPU time
- **[INFO]** Third-party scripts: 2084ms (33% of total)

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

*3 fonts (91 KB)*

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

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

*49 scripts, 166 KB unused*

- **[WARNING]** https://dok.js-cdn.dynatrace.com/jstag/193010ae318...: 57 KB unused (45%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.hornbach.se/globals/static/globals/glo...: 38 KB unused (55%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.hornbach.se/globals/static/globals/glo...: 36 KB unused (85%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://web.cmp.usercentrics.eu/ui/v/3.119.0/WebSd...: 35 KB unused (63%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 166 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 — 90/100)

*15 hints, 0 missing preconnects*

- **[INFO]** 6 dns-prefetch redundant with preconnect on same origin — preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://www.googletagmanager.com, https://www.googleadservices.com, https://googleads.g.doubleclick.net (+3 more). Remove the redundant dns-prefetch entries.
- **[INFO]** 6 URL(s) appear in multiple hints — The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: //www.googletagmanager.com (dns-prefetch+preconnect), //www.googleadservices.com (dns-prefetch+preconnect), //www.google.de (dns-prefetch+preconnect) (+3 more).
- **[PASS]** Page uses 15 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 uses no-store -- correct for sensitive/dynamic content*

- **[PASS]** Main HTML uses no-store -- correct for sensitive/dynamic content

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding,Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

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

*113 resources · 2.4 MB · 166 KB savings available*

- **[WARNING]** Page weight 2.4 MB exceeds 1 MB target by 1.4 MB
- **[INFO]** ~166 KB of savings available
- **[WARNING]** 53 third-party resources (54% of weight)
- **[INFO]** 1 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 — 78/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 3 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.2 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

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

*1 CSS depth issue(s) detected*

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

---

## Content Quality

### Links (B — 85/100)

*195 links checked, 192 healthy, 3 broken*

- **[WARNING]** 192 of 195 links are healthy
- **[WARNING]** Broken link: https://www.googletagmanager.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.googleadservices.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://media.hornbach.se — Found in <link href>. Returns HTTP 404.

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

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

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

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

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

- **[INFO]** og:title is long (66 characters) — Titles over 60 characters may be truncated in social sharing previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

### Open Graph / Twitter Card Depth (A+ — 100/100)

*OG image dimensions and Twitter card configuration look healthy*

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

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

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

- **[INFO]** Missing recommended property "description" for WebSite — Adding "description" can improve how search engines display your content.
- **[INFO]** Missing recommended property "potentialAction" for WebSite — Adding "potentialAction" can improve how search engines display your content.
- **[PASS]** 2 JSON-LD blocks found

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

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

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

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

*5 issues found across 22 images*

- **[WARNING]** 1 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 2 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 7 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.
- **[INFO]** 1 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://media.hornbach.se/webshop-commons/657/images/logo.sv-SE.v1.svg.

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*4 A records, 24 ms lookup*

- **[PASS]** Resolves to 4 IPv4 address(es)
- **[INFO]** No IPv6 (AAAA) records
- **[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.
- **[INFO]** No NS records found
- **[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: 24 ms

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

*No subdomain takeover risk detected*

- **[PASS]** CNAME does not point at a known takeover-able service

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

- **[INFO]** PTR lookup failed for 151.101.193.91: lookup 151.101.193.91: 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 151.101.1.91: lookup 151.101.1.91: 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 151.101.65.91: lookup 151.101.65.91: 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 151.101.129.91: lookup 151.101.129.91: 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 — 90/100)

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

- **[PASS]** Google: 23ms
- **[PASS]** Cloudflare: 31ms
- **[PASS]** Quad9: 80ms

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

*No redirects — direct access*

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

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

*No IPv6 support*

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

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

*robots.txt present, sitemap with 12 URLs*

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

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

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

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

### Domain Intelligence (B — 70/100)

*hornbach.se — via EuroDNS S.A, 22 years, 3 months old, hosted on Fastly*

- **[CRITICAL]** Domain expires in 15 days — This domain expires on May 27, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
- **[PASS]** Registrar: EuroDNS S.A
- **[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: Fastly

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (D — 40/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — A privacy policy page is recommended for transparency and may be legally required.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[CRITICAL]** 5 non-essential cookie(s) set without consent banner — Unrecognized (treated as non-essential): hbMarketSession, hbMarketCookie, hbUserSession, dtCookieo26m5unv, absearchvariant
- **[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)

*1 known tracker(s) detected*

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

tag-manager: Google Tag Manager

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

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

*Lang attribute present*

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

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

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

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

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

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

### 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 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: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

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

*4 trackers detected*

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

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

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

- **[CRITICAL]** 1 tracking cookie(s) set before consent interaction — Under GDPR ePrivacy Art. 5(3), analytics and advertising cookies require explicit opt-in. These cookies appeared in the server response without any consent step — a likely violation.
- **[INFO]** 4 cookie(s) could not be classified
- **[INFO]** 4 third-party tracker(s) detected on page

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

### Cross-Site Cookies (SameSite=None) (B — 85/100)

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

- **[INFO]** 2 tracking-shaped cross-site cookie(s): absearchvariant, dtCookieo26m5unv — 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 — 20/100)

*1 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[PASS]** Cookie Policy detected — Found at , linked from footer.
- **[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

*2 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: European TLD detected: .se. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
- **[INFO]** HIPAA indicators detected (weak confidence) — Indicators suggesting HIPAA may be relevant: Text mentions: phi. Health Insurance Portability and Accountability Act — protects sensitive patient health information.

### Third-Party Data Sharing

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

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

*0 compliance badge(s) detected*

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

---

## Availability

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

*No CDN detected*

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

### HTTP Caching (D — 40/100)

*no-store (uncacheable)*

- **[INFO]** Cache-Control: no-store prevents all caching — Intentional for dynamic content, but increases server load for every page view.
- **[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+ — 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 (base policy)
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

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

*5 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 2 <nav> landmark(s) found
- **[WARNING]** 2 of 2 <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 — 80/100)

*No headings*

- **[WARNING]** No headings found — Headings (H1-H6) create the document outline for screen reader navigation.

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

*No headings to evaluate -- check is N/A*

- **[PASS]** No headings to evaluate -- check is N/A

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

*All 22 images OK*

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

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

*All 1 controls labeled*

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

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

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

- **[CRITICAL]** 1 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 7 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 166 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 (A+ — 100/100)

*No autofill-eligible form controls*

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

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

*Lang attribute set to "sv"*

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

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

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

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

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

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

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

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

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

---

## UX

### 404 Error Page (A — 90/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
- **[PASS]** Search form present on 404 page

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

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

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: HORNBACH
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*2 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).
- **[INFO]** Manifest is missing `theme_color` — Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

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

*No navigation patterns*

- **[PASS]** 2 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+ — 97/100)

*4 mobile-depth signal(s) detected*

- **[PASS]** iOS smart-banner opt-in present (`apple-itunes-app`) — The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.
- **[PASS]** Android smart-banner opt-in present (`google-play-app`) — The page declares a companion Android app via `<meta name="google-play-app" content="app-id=...">` (or `google-play-id`). Combined with Chrome's intent: protocol or App Links, this lets supporting browsers offer to open the page in the app.
- **[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.
- **[INFO]** iOS auto-link for phone numbers disabled (`format-detection: telephone=no`) — The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

---

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

*Title: 5 chars*

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

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

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

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

### Content Depth (C — 65/100)

*510 words, Very Difficult*

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

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

*163 internal, 11 external*

- **[PASS]** 163 internal links (94%)
- **[PASS]** 99% of links use descriptive anchor text
- **[INFO]** 163 internal / 11 external links

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

*22 images, 22 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 — 70/100)

*Sitemap exists but no <lastmod> entries*

- **[INFO]** Sitemap has no <lastmod> entries — Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.

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

*No sitemap-vs-robots conflicts detected*

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

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

*Sitemap structure / size look healthy (12 URLs, 1 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (B — 70/100)

*0.58g CO2 per view*

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

### Green Hosting (B — 80/100)

*Green (hosting)*

- **[PASS]** Axis12 Ltd uses renewable energy
- **[INFO]** Axis12 Ltd: Verified by the Green Web Foundation
- **[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)

*81% cached*

- **[PASS]** 81% reduction on repeat visits — Returning visitors download only 483 KB (vs 2495 KB first visit). 111 of 113 resources are served from browser cache, saving 0.46g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.11g CO2 (first visit: 0.58g)

### Carbon Budget (B — 70/100)

*47th percentile*

- **[INFO]** 0.58g CO2 — below the median website (0.60g) — Better than an estimated 53% of websites, but above the sustainability target of 0.50g. Reducing page weight would help reach the target.
- **[INFO]** Estimated 47th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

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

*93% efficient*

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

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

*No detectable Google Fonts weights*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/f6bb0437-8b8b-4334-bd87-05e80ac7a3ee*