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

**Date:** August 12, 2026  
**URL:** https://rollingstone.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/b1694973-d6bb-4765-b7d7-1570ab69ef3e

## Top Findings

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

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 8 |
| Accessibility | 85 |
| Best Practices | 77 |
| SEO | 92 |

---

## Security

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

*2 of 10 headers properly configured*

- **[WARNING]** HSTS max-age is too short (300s, should be ≥ 31536000s) — A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 0/100)

*No enforcing CSP policy found*

- **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

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

*TLS 1.3, 7 checks passed*

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

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

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

*No security.txt file found*

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

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

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

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

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

*14 inline style attribute(s) detected*

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

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

*No CSP header -- Trusted Types check is N/A*

- **[PASS]** No CSP header found -- Trusted Types check is N/A

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

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

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

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

*HTTP status is non-2xx -- soft-404 check is N/A*

- **[PASS]** HTTP status is non-2xx -- soft-404 check is N/A

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

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

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

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

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

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

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

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

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

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

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

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

Missing SRI on (first 5 examples):
  - https://d1mkq4fbm7j30i.cloudfront.net/21/oHS-21.js
  - https://www.googletagmanager.com/gtag/js?id=AW-16451108737&cx=c&gtm=4e68a1
  - https://cdn.cxense.com/cx.js
  - https://www.googletagmanager.com/gtag/js?id=G-VB3XMC1V0Q&cx=c&gtm=4e68a1
  - https://s3-us-west-2.amazonaws.com/jsstore/a/020H0DJ/ge.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 (C — 60/100)

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

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

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

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

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

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

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

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

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

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

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

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

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

*No software-version disclosures in HTML*

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

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

*No redirect-shaped query parameters in DOM links*

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

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

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

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

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

*No risky subdomain names in certificate SANs*

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

---

## Advanced Security

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

*0 of 52 external resources have SRI*

- **[WARNING]** External script from d1mkq4fbm7j30i.cloudfront.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 cdn.cxense.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 s3-us-west-2.amazonaws.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.cxense.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from slimesupplies.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 iabusprivacy.pmc.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.cookielaw.org lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.cookielaw.org lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from experiments.parsely.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.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.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ads.blogherads.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ads.blogherads.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cds.connatix.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 www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from use.typekit.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pmc-pp-tou.s3.us-west-1.amazonaws.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from fpa-cdn.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.rollingstone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from stats.wp.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from api.fouanalytics.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tru.am lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn-magiclinks.trackonomics.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from rfpx1.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from s.skimresources.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 (B — 82/100)

*DMARC: reject, SPF: ~all, DKIM*

- **[PASS]** DMARC policy is reject — strongest protection
- **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).
- **[PASS]** DKIM configured (selectors: default, selector1, s2, s1)
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

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

*No header set*

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

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

*No CORS headers*

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

---

## Performance

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

*4.1 MB transferred, 296 requests*

- **[CRITICAL]** Page weighs 15.9 MB (4.1 MB transferred)
- **[WARNING]** JavaScript is 2.0 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** Fonts are 1.0 MB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** 296 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.85 g CO2 per page load

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

*98% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 98% of page weight (4.0 MiB of 4.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 — 75/100)

*25 images, 0 KB saveable*

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

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

*8501ms total JS execution*

- **[WARNING]** https://www.rollingstone.com/: 1228ms CPU time
- **[WARNING]** Unattributable: 1225ms CPU time
- **[WARNING]** https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12...: 1182ms CPU time
- **[WARNING]** https://cdn.cookielaw.org/scripttemplates/202511.1...: 682ms CPU time
- **[WARNING]** https://cdn.cookielaw.org/scripttemplates/202511.1...: 680ms CPU time
- **[WARNING]** Third-party scripts: 7276ms (86% of total)

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

*25 fonts (1045 KB)*

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

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

*164 scripts, 998 KB unused*

- **[WARNING]** https://ads.blogherads.com/static/chunks/5273.7066...: 104 KB unused (80%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://cds.connatix.com/p/606857375/connatix.play...: 101 KB unused (73%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-MH9...: 84 KB unused (55%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://cdn.rollingstone.com/api/tinypass.min.js: 73 KB unused (53%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-VB3X...: 72 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 998 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+ — 95/100)

*37 hints, 0 missing preconnects*

- **[INFO]** 1 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://ads.blogherads.com. Remove the redundant dns-prefetch entries.
- **[PASS]** Page uses 37 resource hint(s)

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

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

*No Cache-Control header on main HTML response*

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

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

*No Server-Timing header found*

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

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

*1 server-response signal(s) detected*

- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (F — 25/100)

*296 resources · 4.1 MB · 998 KB savings available*

- **[WARNING]** Page weight 4.1 MB exceeds 1 MB target by 3.1 MB
- **[INFO]** ~998 KB of savings available
- **[WARNING]** 272 third-party resources (98% of weight)

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*2 JS blocking issue(s) detected*

- **[WARNING]** 2 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
- **[WARNING]** Total JS execution time is 8.5 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

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

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (C — 70/100)

*200 links checked, 194 healthy, 6 broken*

- **[CRITICAL]** 194 of 200 links are healthy
- **[WARNING]** Broken link: https://securepubads.g.doubleclick.net — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://ads.blogherads.com/static/ — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.googletagmanager.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://ads.blogherads.com — Found in <link href>. Returns HTTP 404.
- **[CRITICAL]** Broken link: https://optout.aboutads.info/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.instagram.com/rollingstone/ — Found in <a href>. Returns HTTP 429.

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

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

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

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

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

- **[CRITICAL]** og:image is not reachable — The og:image URL could not be fetched. Social platforms won't be able to display it.
- **[INFO]** og:title is short (13 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** og:description is short (43 characters) — Ideal length is 55–200 characters for 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+ — 100/100)

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

- **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content.
- **[PASS]** Custom type "WebPage" — unable to validate specific properties
- **[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, WebPage

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

*3 issues found across 34 images*

- **[INFO]** 34 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 34 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]** 5 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://www.rollingstone.com/wp-content/themes/vip/pmc-rollingstone-2022/assets/public/lazyload-fallback.gif, https://www.rollingstone.com/wp-content/themes/vip/pmc-rollingstone-2022/assets/public/lazyload-fallback.gif, https://www.rollingstone.com/wp-content/themes/vip/pmc-rollingstone-2022/assets/public/lazyload-fallback.gif (+2 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*1 A records, 98 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[INFO]** No IPv6 (AAAA) records
- **[PASS]** 4 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 98 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 (C — 60/100)

*0/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 192.0.66.114: lookup 192.0.66.114: 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 23ms across 3 resolvers (spread 38ms)*

- **[PASS]** Quad9: 2ms
- **[PASS]** Cloudflare: 27ms
- **[PASS]** Google: 40ms

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

*1 redirect(s), 17 ms total*

- **[PASS]** Single redirect
- **[INFO]** WWW normalization redirect

### 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 1253 URLs*

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

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

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

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

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

*rollingstone.com — via CSC Corporate Domains, Inc., 32 years, 4 months old, hosted on WordPress.com (Automattic)*

- **[WARNING]** Domain expires in 38 days — Consider enabling auto-renewal to prevent accidental expiration.
- **[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: CSC Corporate Domains, 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.
- **[PASS]** Hosting: WordPress.com (Automattic)

---

## Compliance

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

*No testable criteria*


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

*privacy policy found*

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

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

*No consent-UX depth issues detected*

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

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

*2 known tracker(s) detected*

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

tag-manager: Google Tag Manager | analytics: Google Analytics 4

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

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

*Lang attribute present*

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

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

*No hreflang tags on this page*

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

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*Statement found, no conformance level*

- **[INFO]** Accessibility statement found but lacks WCAG conformance level — Mature accessibility statements declare a target conformance level (e.g., WCAG 2.1 AA). Without a stated level, users and reviewers cannot tell what the statement actually commits to.

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

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

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

### Third-Party Trackers (B — 80/100)

*9 trackers detected*

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

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

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

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

### Tracking Pixel Inventory (B — 90/100)

*1 tracking pixel(s) on the page*

- **[INFO]** 1 tracking pixel(s) on the page (1 domain(s)) — Tracking pixels are 1x1 / 2x2 cross-origin <img> tags that fire a GET request when the browser renders them -- no JavaScript, no cookies needed. They're how trackers survive when users disable JS or block third-party cookies, and they bypass most ad-blocker rules that target script src. Each one needs explicit disclosure under GDPR Art 7 / CCPA / ePrivacy because the request itself transmits the page URL + IP + user-agent + referrer to the tracker. Audit each surfaced domain: is it disclosed in your privacy policy? Is it conditional on the cookie banner? Affected domains: www.rollingstone.com.

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://pmc.com/privacy-policy/.
- **[PASS]** Terms of Service detected — Found at https://pmc.com/terms-of-use/.
- **[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.
- **[PASS]** Accessibility Statement detected — Found at /accessibility/.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

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

*© 2026 Rolling Stone*

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

### 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 (strong confidence) — Indicators suggesting GDPR may be relevant: Consent management platform detected: cookielaw.org; European TLD detected: .fr; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
- **[INFO]** ADA indicators detected (moderate confidence) — Indicators suggesting ADA may be relevant: Accessibility statement page found. Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.
- **[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

*2 third-party service(s) detected*

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

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

*1 compliance badge(s) detected*

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

---

## Availability

### CDN & Delivery (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 (F — 30/100)

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (B — 75/100)

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

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** HSTS max-age is short: 0 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://rollingstone.com/health (HTTP 200)*

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

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

*Cache state: EXPIRED*

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

---

## Accessibility

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

*11 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 5 <nav> landmark(s) found
- **[WARNING]** 2 of 5 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[PASS]** Skip navigation link present
- **[WARNING]** Skip link target(s) don't exist on page: #pagetop — The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

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

*61 headings, 1 skip(s)*

- **[PASS]** Single H1 present
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

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

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

- **[WARNING]** 3 heading(s) are over 120 characters -- likely a misformatted paragraph — Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected:
  - H1: 200 chars
  - H3: 132 chars
  - H3: 124 chars

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

*All 34 images OK*

- **[INFO]** 10 image(s) with alt text over 125 characters
- **[PASS]** 2 decorative image(s) correctly marked
- **[PASS]** 22 image(s) with good alt text

### Form Accessibility (D — 54/100)

*4 of 6 controls have issues*

- **[CRITICAL]** 2 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[WARNING]** 2 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 2 control(s) properly labeled

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

*6 issue(s) across 231 links and 13 buttons*

- **[CRITICAL]** 1 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 4 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 5 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 1 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 221 link(s) with descriptive text

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

*2 input(s) using type=text where a specific type would help*

- **[INFO]** Input "q" should use type="search" (currently type="text") — Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
- **[INFO]** Input "q" should use type="search" (currently type="text") — Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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

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

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

### Mobile Keyboard & Autofill (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 "en-US"*

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

### Tabindex Anti-Patterns (D — 40/100)

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

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

### Iframe Accessibility (D — 40/100)

*9/10 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="javascript:false") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…") — 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="about:blank") — 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 (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

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

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

- **[WARNING]** 10 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: <li> 11.0px ("By"); <a> 11.0px ("Jon Blistein"); <li> 11.0px ("By"); <a> 11.0px ("Emily Zemler"); <li> 11.0px ("By").

---

## UX

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

*HTTP 404, custom page*

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

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

*4 icon(s) detected*

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

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

*Not found*

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

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

*No PWA depth issues detected*

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

### Dark Mode Support (D — 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 — 30/100)

*1 navigation pattern(s)*

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

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Properly configured*

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

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

*Title: 61 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 61 characters — may be truncated in search results
- **[PASS]** Meta description length (89 chars) is optimal
- **[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)

*1636 words, Very Difficult*

- **[PASS]** Page has 1636 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 21)

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

*58 internal, 173 external*

- **[PASS]** 58 internal links (25%)
- **[PASS]** 98% of links use descriptive anchor text
- **[INFO]** Page has 231 links — consider reducing
- **[INFO]** 58 internal / 173 external links

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

*34 images, 33 descriptive filenames*

- **[INFO]** 1 image(s) have hash/generic filenames

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

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

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

- **[PASS]** Sitemap actively maintained — newest lastmod: today

### 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 (1253 URLs, 156 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*1.15g CO2 per view*

- **[WARNING]** 1.15g CO2 per page view — This page transfers 4.1 MB, producing an estimated 1.15g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.21g, network 0.20g, end-user device 0.74g.
- **[INFO]** At 10,000 monthly views: 137.7 kg CO2/year — With 10,000 page views per month, this page would generate approximately 137.7 kg of CO2 annually — equivalent to charging 17210 smartphones.

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

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** 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)

*96% cached*

- **[PASS]** 96% reduction on repeat visits — Returning visitors download only 148 KB (vs 4148 KB first visit). 287 of 296 resources are served from browser cache, saving 1.11g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.04g CO2 (first visit: 1.15g)

### Carbon Budget (D — 50/100)

*65th percentile*

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

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

*76% efficient*

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

### Web Font Weight Variants (A+ — 100/100)

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

- **[PASS]** 1 font weight(s) loaded across 1 famil(y/ies)

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/b1694973-d6bb-4765-b7d7-1570ab69ef3e*