# BeaverCheck Audit Report — https://renaissancejewel.com

**Date:** September 29, 2026  
**URL:** https://renaissancejewel.com  
**Overall Grade:** C (79/100)  
**Report:** https://beavercheck.com/results/204f498e-4d11-49d6-bb76-156d042080a3

## Top Findings

1. **[CRITICAL]** Cookie 'cart_currency' is missing the Secure flag — Security > Cookie Security
2. **[CRITICAL]** Cookie 'localization' is missing the Secure flag — Security > Cookie Security
3. **[CRITICAL]** Page weighs 17.3 MB (10.1 MB transferred) — Performance > Page Weight Budget
4. **[CRITICAL]** 11 button(s) with no accessible text — Accessibility > Link & Button Quality
5. **[CRITICAL]** 2 control(s) without accessible label — Accessibility > Form Accessibility

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 27 |
| Accessibility | 83 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

### Security Headers (C — 55/100)

*5 of 10 headers properly configured*

- **[WARNING]** HSTS is enabled but max-age is short (7889238s, should be >= 31536000s) — The header is present and enforced, so first-visit protection is already in place; a short max-age just means the browser forgets it sooner. Set max-age to at least 31536000 (1 year).
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[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 present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (B — 75/100)

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

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

*5 cookies analyzed, 11 checks passed*

- **[CRITICAL]** Cookie 'localization' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'localization' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'localization' has SameSite=Lax
- **[CRITICAL]** Cookie 'cart_currency' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'cart_currency' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'cart_currency' has SameSite=Lax
- **[PASS]** Cookie '_shopify_essential' has the Secure flag
- **[PASS]** Cookie '_shopify_essential' has the HttpOnly flag
- **[PASS]** Cookie '_shopify_essential' has SameSite=Lax
- **[PASS]** Cookie '_shopify_analytics' has the Secure flag
- **[PASS]** Cookie '_shopify_analytics' has the HttpOnly flag
- **[PASS]** Cookie '_shopify_analytics' has SameSite=Lax
- **[PASS]** Cookie '_shopify_marketing' has the Secure flag
- **[PASS]** Cookie '_shopify_marketing' has the HttpOnly flag
- **[PASS]** Cookie '_shopify_marketing' has SameSite=Lax

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

*All 5 cookie(s) pass hygiene checks*

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

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a42957a03f620246-CDG

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

*8 of 8 new-tab link(s) missing rel=noopener*

- **[WARNING]** 8 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

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

*62 inline style attribute(s) detected*

- **[WARNING]** 62 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. 62 inline style(s) is high. Affected element types include: header, div, details-modal, svg, 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 (D — 50/100)

*4% SRI adoption (2/50 third-party resources)*

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

Missing SRI on (first 5 examples):
  - https://invitejs.trustpilot.com/tp.min.js
  - https://cdn1.affirm.com/js/v2/affirm.js
  - https://ecommplugins-trustboxsettings.trustpilot.com/h-daimondjewellery.myshopify.com.js?settings=1783795215535&shop=h-daimondjewellery.myshopify.com
  - https://ecommplugins-scripts.trustpilot.com/v2.1/js/success.min.js?settings=eyJrZXkiOiJoZm9vMXNJVHVQSXBHMktjIiwicyI6Im5vbmUiLCJ0IjpbIm9yZGVycy9mdWxmaWxsZWQiXSwidiI6IiIsImEiOiIifQ==&shop=h-daimondjewellery.myshopify.com
  - https://ecommplugins-scripts.trustpilot.com/v2.1/js/header.min.js?settings=eyJrZXkiOiJoZm9vMXNJVHVQSXBHMktjIiwicyI6Im5vbmUifQ==&shop=h-daimondjewellery.myshopify.com

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### Source Map Exposure (D — 60/100)

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

- **[WARNING]** 4 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://renaissancejewel.com/cdn/shop/t/56/assets/predictive-search.js.map, https://renaissancejewel.com/cdn/shop/t/56/assets/theme.js.map, https://renaissancejewel.com/cdn/shop/t/56/compiled_assets/scripts.js.map, https://renaissancejewel.com/cdn/shop/t/56/assets/global.js.map.

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

*2 auth-security finding(s) on the login page*

- **[PASS]** Login page detected — The page contains a `type=password` input and at least one identifier field (username / email). Auth-security findings below evaluate the page's hardening posture.
- **[WARNING]** Login form does not contain a recognizable CSRF token — Standard frameworks emit CSRF tokens as a hidden input named `_csrf`, `csrf_token`, `csrfmiddlewaretoken` (Django), `authenticity_token` (Rails), or `__RequestVerificationToken` (ASP.NET). None of those were found. Possibilities: (1) the form posts to an API that uses a custom header or SameSite cookie reliance for CSRF -- legitimate but not visible from this scan, (2) the form is genuinely missing CSRF protection, which would let an attacker submit logins from another origin via a hidden POST. Verify the auth flow has SOME CSRF defense.

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

*2 of 50 external resources have SRI*

- **[WARNING]** External script from invitejs.trustpilot.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn1.affirm.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ecommplugins-trustboxsettings.trustpilot.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ecommplugins-scripts.trustpilot.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ecommplugins-scripts.trustpilot.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from api-eu1.hubapi.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.nfcube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.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.
- **[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.
- **[WARNING]** External script from connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from js.hs-scripts.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from code.jquery.com has SRI protection
- **[WARNING]** External script from shop.app lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from cdn.shopify.com has SRI protection
- **[WARNING]** External link from cdn.jsdelivr.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.jsdelivr.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.paypal.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.hotjar.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn-v2.reelup.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static-tracking.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static-tracking.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static-tracking.klaviyo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from code.tidio.co lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.shopify.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

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

*No known vulnerabilities*

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

### Information Leakage (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 — 37/100)

*DMARC: none, SPF: -all*

- **[WARNING]** DMARC policy is none — monitoring only — This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject after monitoring DMARC reports.
- **[INFO]** DMARC configured without rua= aggregate reporting — Without rua=, you have no visibility into spoof attempts or auth failures from your own legitimate senders. Add rua=mailto:dmarc@<your-domain> (or a managed inbox at a reporting service).
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (C — 65/100)

*GraphQL introspection enabled at /api/graphql*

- **[WARNING]** GraphQL introspection enabled at /api/graphql — Introspection lets clients query the GraphQL server for its complete schema -- every type, field, argument, and resolver name. Convenient during development; on production, an attacker uses it as a free recon tool to map the entire data graph. Disable in production unless your API is intentionally public-spec.

### Permissions-Policy (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

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

*No CORS headers*

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

---

## Performance

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

*10.1 MB transferred, 475 requests*

- **[CRITICAL]** Page weighs 17.3 MB (10.1 MB transferred)
- **[WARNING]** JavaScript is 2.7 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** Images are 1.4 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[INFO]** Fonts are 309 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** 475 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 2.1 g CO2 per page load

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

*78% third-party, 0 ms blocking*

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

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

*All text resources are compressed*

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

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

*68 images, 0 KB saveable*

- **[WARNING]** https://cdn.shopify.com/s/files/1/0713/6598/4514/f... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn.shopify.com/s/files/1/0713/6598/4514/f... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn.shopify.com/s/files/1/0713/6598/4514/f... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn.shopify.com/s/files/1/0713/6598/4514/f... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*14088ms total JS execution*

- **[WARNING]** https://renaissancejewel.com/: 4750ms CPU time
- **[WARNING]** Unattributable: 2218ms CPU time
- **[WARNING]** https://renaissancejewel.com/cdn/shop/t/56/assets/...: 802ms CPU time
- **[WARNING]** https://renaissancejewel.com/cdn/wpm/ba5bf51cfwabd...: 591ms CPU time
- **[WARNING]** https://renaissancejewel.com/cdn/shop/t/56/compile...: 508ms CPU time
- **[INFO]** Third-party scripts: 4301ms (31% of total)

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

*10 fonts (309 KB)*

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

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

*218 scripts, 1.1 MB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-PCZM...: 126 KB unused (66%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-183...: 114 KB unused (71%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://code.tidio.co/widget-v4/1_467_0/static/js/...: 105 KB unused (47%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://code.tidio.co/widget-v4/1_467_0/static/js/...: 84 KB unused (56%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-WXSP...: 74 KB unused (39%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 1.1 MB

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

*147 hints, 0 missing preconnects*

- **[INFO]** 10 preconnect hints -- excessive (recommended: <=6) — Each preconnect eagerly opens a TCP+TLS connection. On slow networks or low-end devices, too many parallel connections cause head-of-line blocking and starve the connections that matter for LCP. Trim to the 4-6 highest-value origins (the ones serving render-blocking or LCP resources).
- **[INFO]** 4 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://api-cf.affirm.com, https://api-cf.affirm.com, https://www.affirm.com (+1 more). Remove the redundant dns-prefetch entries.
- **[INFO]** 4 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: https://www.affirm.com (preconnect+dns-prefetch+preconnect+dns-prefetch), https://fonts.gstatic.com (preconnect+preconnect), https://api-cf.affirm.com/api/v2/ (preconnect+dns-prefetch+preconnect+dns-prefetch) (+1 more).
- **[PASS]** Page uses 147 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 (A+ — 100/100)

*Document response uses brotli*

- **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

### Asset Compression (B — 75/100)

*1 of 6 asset hosts serve text uncompressed*

- **[PASS]** cdn.shopify.com serves assets with brotli (assets: 80)
- **[WARNING]** fonts.googleapis.com serves text assets uncompressed (assets: 10) — The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
- **[PASS]** www.googletagmanager.com serves assets with brotli (assets: 8)
- **[PASS]** cdn.jsdelivr.net serves assets with brotli (assets: 3)
- **[PASS]** static-tracking.klaviyo.com serves assets with brotli (assets: 3)
- **[PASS]** static.klaviyo.com serves assets with brotli (assets: 3)

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

*LCP preload audit not available*

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

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

*No Cache-Control header on main HTML response*

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

### Server-Timing Observability (A+ — 100/100)

*19 Server-Timing entries advertised*

- **[PASS]** Server-Timing header advertises 19 timing entries

### 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 (F — 20/100)

*475 resources · 10.1 MB · 1.1 MB savings available*

- **[WARNING]** Page weight 10.1 MB exceeds 1 MB target by 9.1 MB
- **[INFO]** ~1.1 MB of savings available
- **[WARNING]** 194 third-party resources (78% of weight)
- **[INFO]** 3 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*2 JS blocking issue(s) detected*

- **[WARNING]** 6 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 14.1 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 (B — 78/100)

*2 CSS depth issue(s) detected*

- **[WARNING]** 50 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.
- **[WARNING]** 1 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright.

---

## Content Quality

### Links (B — 80/100)

*200 links checked, 196 healthy, 4 broken*

- **[CRITICAL]** 196 of 200 links are healthy
- **[WARNING]** Broken link: https://api-eu1.hubapi.com/scriptloader/v1/147837436.js?s... — Found in <script src>. Returns HTTP 410.
- **[WARNING]** Broken link: https://js.hs-scripts.com/47999717.js — Found in <script src>. Returns HTTP 410.
- **[WARNING]** Broken link: https://monorail-edge.shopifysvc.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://api-cf.affirm.com/api/v2/ — 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 (B — 85/100)

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

- **[WARNING]** Missing og:image — The og:image tag provides a preview image for social sharing.
- **[INFO]** og:description is long (212 characters) — Descriptions over 200 characters may be truncated in social sharing 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 — 90/100)

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

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

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

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

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

Organization (×2), WebSite (×2), JewelryStore

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
- **[WARNING]** 2 Organization blocks on the page -- only one should describe the publishing entity — Multiple `Organization` JSON-LD blocks confuse search engines about which is canonical. Google may suppress knowledge-panel features when the entity identity is ambiguous. Pick one Organization block (typically representing the publisher) and remove the rest, or merge by giving the duplicates explicit `@id` URIs that point to a single canonical entity.

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

*7 issues found across 151 images*

- **[WARNING]** 20 images significantly larger than display size — Resizing to display dimensions could save approximately 429 KB.
- **[WARNING]** 77 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.
- **[INFO]** 144 of 151 images use legacy formats
- **[WARNING]** 8 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://cdn.shopify.com/s/files/1/0713/6598/4514/files/rj-ready-to-ship-hero.png?width=600, https://cdn.shopify.com/s/files/1/0713/6598/4514/files/ROUND__DIAMOND.jpg?width=160, https://cdn.shopify.com/s/files/1/0713/6598/4514/files/PEAR__DIAMOND.jpg?width=160 (+5 more).
- **[INFO]** 3 image(s) wider than 400px without srcset (no responsive serving) — These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://renaissancejewel.com/cdn/shop/files/hf_20260525_131025_b2902220-2f99-4490-ba90-40a659642da2.png?v=1779714993&width=1100, https://renaissancejewel.com/cdn/shop/files/hf_20260525_123911_557de9d3-3958-4a50-ade2-216f95a3e48f.png?v=1779712886&width=1100, https://cdn.shopify.com/s/files/1/0713/6598/4514/files/EMP02375_3.png?v=1728394412&width=1800.
- **[INFO]** 4 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://cdn.shopify.com/s/files/1/0713/6598/4514/files/rj-ready-to-ship-hero.png?width=600, https://cdn.shopify.com/s/files/1/0713/6598/4514/files/rj-wedding-hero.png?width=600, https://cdn.shopify.com/s/files/1/0713/6598/4514/files/rj-earrings-hero.png?width=600 (+1 more).

### Autoplay Media (B — 90/100)

*1 autoplay media element(s) -- all muted*

- **[INFO]** 1 autoplay media element(s) on page (muted) — Autoplay video transfers bytes whether the user engages or not -- a sustainability concern even when muted. Consider replacing with a static poster image and a click-to-play overlay; the user opts in to the bandwidth cost.

---

## Infrastructure

### DNS Records (A+ — 95/100)

*1 A records, 35 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[PASS]** Has 1 IPv6 (AAAA) record(s)
- **[PASS]** 2 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 35 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

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

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

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

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

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

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 23.227.38.65 does not match any cert SAN: myshopify.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR lookup failed for 2620:127:f00f:5::: lookup 2620:127:f00f:5::: 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 20ms across 3 resolvers (spread 5ms)*

- **[PASS]** Cloudflare: 18ms
- **[PASS]** Google: 20ms
- **[PASS]** Quad9: 23ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (17 ms)*

- **[PASS]** IPv6 is configured and reachable at 2620:127:f00f:5::

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

*robots.txt present, sitemap with 226 URLs*

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

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

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

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

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

*renaissancejewel.com — via NameCheap, Inc., 2 years, 1 months old*

- **[PASS]** Domain registered until Aug 20, 2030 (3 years, 11 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: NameCheap, Inc.
- **[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.

---

## Compliance

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

*No testable criteria*


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

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[WARNING]** 5 unclassified cookie(s) set before any consent step — These cookies could not be matched to a known tracker or to a known essential-cookie family, so the scanner cannot tell whether consent was required. Verify each is strictly necessary; if any is analytics or advertising, it needs consent first. Unrecognized (treated as non-essential): localization, cart_currency, _shopify_essential, _shopify_analytics, _shopify_marketing
- **[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)

*3 known tracker(s) detected*

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

tag-manager: Google Tag Manager | analytics: Google Analytics 4 | 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+ — 100/100)

*Lang attribute + Content-Language header*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[PASS]** Content-Language header is set
- **[PASS]** Language signals are consistent

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

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

- **[INFO]** GDPR Article 13 disclosure coverage: 5 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 5 of 8 categories: Data retention period, Data subject rights (access, erasure, rectification, etc.), International data transfers, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Missing: Data Protection Officer contact (where applicable), Identity / contact details of the data controller, Legal basis for processing. 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 (C — 60/100)

*11 trackers detected*

- **[INFO]** 11 third-party trackers detected — Found 6 analytics, 1 advertising, 2 marketing, 1 tag manager, 1 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.
- **[WARNING]** 1 session-replay tool(s) detected (Hotjar) — Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.

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

*5 cookies · 11 trackers · 0 pre-consent*

- **[INFO]** 2 cookie(s) could not be classified
- **[INFO]** 11 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 SameSite=None cookies -- no cross-site travel surface*

- **[PASS]** No cookies opted in to cross-site travel (SameSite=None)

### Beacon Tracking (sendBeacon) (B — 90/100)

*2 sendBeacon call site(s) in inline scripts*

- **[INFO]** 2 navigator.sendBeacon call site(s) in inline scripts — navigator.sendBeacon() fires fire-and-forget POSTs in the background after page-unload -- typically used for last-second analytics (read-time, scroll depth, exit-intent). Ad-blockers' XHR/fetch interception often misses them (different API path); DevTools shows beacon requests typed as "ping" instead of "fetch", which is easy to overlook in privacy reviews. Audit each call site: what data is being sent? Is the recipient disclosed in the privacy policy? Is the call gated behind cookie-banner consent? Does the user have a way to opt out of the page-unload tracking specifically (separate from in-session analytics)? Detection is limited to inline scripts -- beacons in external SDKs aren't visible to this static scan.

---

## Legal

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

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /policies/privacy-policy.
- **[PASS]** Terms of Service detected — Found at /policies/terms-of-service.
- **[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 /policies/refund-policy.
- **[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 (B — 80/100)

*Copyright 2025*

- **[INFO]** Copyright year is 2025 (1 year(s) behind) — Copyright year is 2025 — 1 year(s) behind. While copyright protection doesn't depend on the year being current, an outdated notice may suggest the site is not actively maintained. Update to © 2026 or use a range like © 2025–2026.

### Regulatory Indicators

*3 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.
- **[INFO]** PCI-DSS indicators detected (moderate confidence) — Indicators suggesting PCI-DSS may be relevant: Payment processor detected: paypal.com. Payment Card Industry Data Security Standard — applies to organizations handling credit card data.
- **[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

*6 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]** 6 third-party services across 6 categories — 6 third-party services detected across 6 categories: Analytics (1), Tag Management (1), Advertising (1), Session Recording (1), Marketing (1), Payment (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Facebook Pixel (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, User behavior, Ad targeting. Privacy policy: https://www.facebook.com/privacy/policy. Data Processing Agreement available.
- **[INFO]** Hotjar (Session Recording) — Detected via script URL. Typically collects: Session recordings, Heatmaps, Click patterns, Form interactions. Privacy policy: https://www.hotjar.com/privacy/. Data Processing Agreement available.
- **[INFO]** HubSpot (Marketing) — Detected via script URL. Typically collects: Lead tracking, Form submissions, Page views, Email tracking. Privacy policy: https://legal.hubspot.com/privacy-policy. Data Processing Agreement available.
- **[INFO]** PayPal (Payment) — Detected via script URL. Typically collects: Payment data, Transaction details, User identity. Privacy policy: https://www.paypal.com/us/legalhub/privacy-full. 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 — 85/100)

*Document on Cloudflare; assets also on Fastly*

- **[PASS]** Document is served via Cloudflare CDN (edge: CDG)
- **[INFO]** CDN cache status: DYNAMIC
- **[PASS]** Assets on Cloudflare: cdn.shopify.com (assets: 80), cache HIT
- **[PASS]** Assets on Cloudflare: cdn.jsdelivr.net (assets: 3), cache HIT
- **[PASS]** Assets on Fastly: static-tracking.klaviyo.com (assets: 3), cache HIT, HIT
- **[PASS]** Assets on Fastly: static.klaviyo.com (assets: 3), cache DYNAMIC

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

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
- **[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 — 85/100)

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

- **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
- **[WARNING]** HSTS max-age is short: 91 days — HSTS max-age should be at least 1 year (31536000 seconds).
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (A+ — 100/100)

*Health endpoint at https://renaissancejewel.com/healthz (HTTP 200)*

- **[PASS]** Public health endpoint at https://renaissancejewel.com/healthz

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

*Cache state: DYNAMIC*

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

---

## Accessibility

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

*6 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.
- **[PASS]** Skip navigation link present

### Heading Hierarchy (C — 65/100)

*30 headings, 1 skip(s)*

- **[WARNING]** Multiple H1 headings (2 found) — A page should have only one H1. Multiple H1s dilute the document outline.
- **[WARNING]** Heading level skipped: H2 → H5 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** 2 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

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

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

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

*2 of 10 controls have issues*

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

### Link & Button Quality (D — 41/100)

*17 issue(s) across 327 links and 55 buttons*

- **[CRITICAL]** 6 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 3 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 11 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 318 link(s) with descriptive text

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

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

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

### Form Input Quality (B — 82/100)

*2 input-semantic issue(s) across 10 form control(s)*

- **[INFO]** 1 password field(s) missing or with invalid `autocomplete` — Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.
- **[INFO]** 3 login form field(s) missing `autocomplete=username` (or `email`) — On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="contact[email]">, <input type="email" name="email">, <input type="email" name="customer[email]">.

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

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

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

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

*Lang attribute set to "en"*

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

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

*12 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (B — 80/100)

*2/2 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="https://renaissancejewel.com/web-pixels@a5bf51cfwabd6c495p49b74ff1maa529d2b/cus…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://renaissancejewel.com/web-pixels@a5bf51cfwabd6c495p49b74ff1maa529d2b/cus…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (B — 90/100)

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

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

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

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

- **[WARNING]** 22 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 ("Ends Soon"); <a> 11.0px ("Shop the Sale →"); <span> 9.5px ("The Collection"); <span> 10.5px ("Shop Engagement Rings →"); <span> 11.5px ("Round").

---

## UX

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

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page

### Favicon & Branding (F — 15/100)

*1 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

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

*Theme color only*

- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

*No print styles*

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

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

*1 navigation pattern(s)*

- **[PASS]** Skip navigation link detected
- **[PASS]** 2 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Title: 8 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 8 characters — consider expanding
- **[INFO]** Meta description is 212 characters — truncated on mobile (~160 char limit)
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

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

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

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

*1203 words, Very Difficult*

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

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

*313 internal, 14 external*

- **[PASS]** 313 internal links (96%)
- **[PASS]** 98% of links use descriptive anchor text
- **[INFO]** Page has 327 links — consider reducing
- **[INFO]** 313 internal / 14 external links
- **[WARNING]** 2 internal links have no anchor text

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

*151 images, 151 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 (226 URLs, 30 KB)*

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

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

*1 markup-quality issue(s) detected*

- **[INFO]** `<meta charset>` declared at byte 4458 -- past the 1024-byte spec window — The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.

---

## Sustainability

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

*2.39g CO2 per view*

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

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

*Green (both)*

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

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

*99% cached*

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

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

*95th percentile*

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

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

*89% efficient*

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

### Web Font Weight Variants (C — 70/100)

*13 font weights loaded across 5 famil(y/ies)*

- **[WARNING]** 13 font weights loaded -- likely 100+ KB of unused payload — Loading 13 font weights typically transfers 200-400 KB just for fonts. Most pages legitimately use 2-3 weights (regular + bold, maybe medium). Audit which weights your stylesheet actually applies and trim the Google Fonts URL accordingly. Affected families: Cormorant, Inter, Kaisei Decol, Montserrat, Nunito Sans.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/204f498e-4d11-49d6-bb76-156d042080a3*