# BeaverCheck Audit Report — https://www.nytimes.com

**Date:** May 9, 2026  
**URL:** https://www.nytimes.com  
**Overall Grade:** C (79/100)  
**Report:** https://beavercheck.com/results/dfc2bcaa-7a70-46b9-82e5-156d23da9915

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[CRITICAL]** Cookie 'nyt-gdpr' is missing the Secure flag — Security > Cookie Security
4. **[CRITICAL]** Cookie 'nyt-geo' is missing the Secure flag — Security > Cookie Security
5. **[CRITICAL]** Cookie 'nyt-s-present' is missing the Secure flag — Security > Cookie Security

---

## Lighthouse Scores

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

---

## Security

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

*7 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured
- **[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.
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[PASS]** Domain is in the Chrome HSTS preload list (status: preloaded)

### Content Security Policy (D — 40/100)

*4 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[WARNING]** object-src allows plugin content — Set object-src to 'none' to prevent Flash/Java plugin exploits.
- **[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'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[PASS]** form-action directive is set
- **[PASS]** upgrade-insecure-requests is enabled

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

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[PASS]** OCSP stapling enabled
- **[PASS]** Certificate is valid (expires in 127 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 29 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (D — 40/100)

*7 cookies analyzed, 8 checks passed*

- **[PASS]** Cookie 'nyt-a' has the Secure flag
- **[WARNING]** Cookie 'nyt-a' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'nyt-a' has SameSite=None
- **[CRITICAL]** Cookie 'nyt-gdpr' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'nyt-gdpr' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'nyt-gdpr' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'nyt-purr' has the Secure flag
- **[WARNING]** Cookie 'nyt-purr' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'nyt-purr' has SameSite=Lax
- **[CRITICAL]** Cookie 'nyt-geo' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'nyt-geo' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'nyt-geo' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'datadome' has the Secure flag
- **[WARNING]** Cookie 'datadome' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'datadome' has SameSite=Lax
- **[CRITICAL]** Cookie 'nyt-s-present' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'nyt-s-present' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'nyt-s-present' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'nyt-traceid' has the Secure flag
- **[WARNING]** Cookie 'nyt-traceid' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'nyt-traceid' has SameSite=None

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

*All 7 cookie(s) pass hygiene checks*

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

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

*No WAF detected via response headers*

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

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

*Vulnerability disclosure policy*

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

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

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

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

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

*334 inline style attribute(s) detected*

- **[WARNING]** 334 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. 334 inline style(s) is high. Affected element types include: body, button, th, td, span. 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.

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

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

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

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

*No software-version disclosures in HTML*

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

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

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

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

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

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

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

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

*No risky subdomain names in certificate SANs*

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

---

## Advanced Security

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

*0 of 24 external resources have SRI*

- **[WARNING]** External script from dd.nytimes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.datadoghq-browser-agent.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from g1.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from rumcdn.geoedge.be lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from warp.media.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.chartbeat.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from static01.nytimes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from static01.nytimes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from static01.nytimes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from static01.nytimes.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pay.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static01.nyt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from a1.nyt.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*

- **[PASS]** security.txt is present — good practice
- **[PASS]** No sensitive files exposed

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

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

### Permissions-Policy (C — 65/100)

*1 directives, 5 missing*

- **[PASS]** browsing-topics=() — blocked for all origins
- **[INFO]** camera not restricted — Consider adding camera=() to block camera access from embedded content.
- **[INFO]** microphone not restricted — Consider adding microphone=() to block microphone access from embedded content.
- **[INFO]** geolocation not restricted — Consider adding geolocation=() to block geolocation access from embedded content.
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

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

*No CORS headers*

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

---

## Performance

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

*6.9 MB transferred, 159 requests*

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

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

*71% third-party, 0 ms blocking*

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

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

*All text resources are compressed*

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

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

*15 images, 0 KB saveable*

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

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

*25005ms total JS execution*

- **[WARNING]** https://www.nytimes.com/vi-assets/static-assets/ma...: 12526ms CPU time
- **[WARNING]** Unattributable: 2206ms CPU time
- **[WARNING]** https://static01.nyt.com/video-static/betamax/beta...: 2028ms CPU time
- **[WARNING]** https://www.nytimes.com/: 1969ms CPU time
- **[WARNING]** https://www.nytimes.com/vi-assets/static-assets/ad...: 1010ms CPU time
- **[INFO]** Third-party scripts: 8435ms (34% of total)

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

*13 fonts (325 KB)*

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

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

*43 scripts, 1.3 MB unused*

- **[WARNING]** https://www.nytimes.com/vi-assets/static-assets/ma...: 469 KB unused (46%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.nytimes.com/vi-assets/static-assets/ho...: 210 KB unused (45%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://static01.nyt.com/video-static/betamax/hlsj...: 140 KB unused (96%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://pagead2.googlesyndication.com/pagead/manag...: 132 KB unused (70%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://warp.media.net/js/tags/clientag.js?cid=8CU...: 94 KB unused (49%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 1.3 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 (A+ — 100/100)

*1 hints, 0 missing preconnects*

- **[PASS]** Page uses 1 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 (A+ — 100/100)

*Main HTML uses no-cache -- safe revalidate-on-request policy*

- **[PASS]** Main HTML uses no-cache -- safe revalidate-on-request policy

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding, Fastly-SSL — 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]** `Last-Modified` present -- timestamp-based conditional GET supported — Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.

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

*159 resources · 6.9 MB · 1.3 MB savings available*

- **[WARNING]** Page weight 6.9 MB exceeds 1 MB target by 5.9 MB
- **[INFO]** ~1.3 MB of savings available
- **[WARNING]** 144 third-party resources (71% of weight)
- **[INFO]** 8 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 (C — 68/100)

*3 JS blocking issue(s) detected*

- **[WARNING]** 4 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]** Page uses document.write() -- disables Chrome's preload scanner — `document.write()` blocks all parallel resource discovery while it executes. Chrome explicitly disables the preload scanner on connections it judges slow when document.write is detected, serializing the entire subtree load. Almost always third-party ad / analytics legacy code; replacing with createElement + appendChild (or refusing to integrate the offending vendor) recovers significant load-time on mobile.
- **[WARNING]** Total JS execution time is 25.0 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

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

*1 CSS depth issue(s) detected*

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

---

## Content Quality

### Links (F — 40/100)

*200 links checked, 156 healthy, 44 broken*

- **[CRITICAL]** 156 of 200 links are healthy
- **[WARNING]** Broken link: https://www.nytimes.com/es/ — Found in <link href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/markwayne-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/nyregion/mahmoud-khali... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/trump-immi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/lawmakers-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/04/technology/trump-ai-mo... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/03/us/politics/justice-de... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/trump-fda-commissio... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/ufo-sighti... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/trump-pent... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/reflecting... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/06/us/politics/trump-indi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/upshot/redistricting-m... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/virginia-r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/alabama-su... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/politics/virginia-r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/arts/television/david-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/09/world/asia/china-milit... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/09/world/asia/trump-xi-ch... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/09/business/china-april-t... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/03/20/world/europe/ukraine-r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/07/world/europe/ukraine-r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/05/world/europe/russia-uk... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/04/world/africa/ukraine-r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/09/world/europe/russia-vi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/07/world/middleeast/iran-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/07/world/middleeast/trump... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/07/world/middleeast/israe... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/article/iran-war-trump-us-oil-hor... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/live/2026/05/08/world/iran-strike... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/business/trump-sanctio... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/climate/iran-kharg-oil... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/world/hantavirus-mv-ho... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/world/americas/norovir... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/nyregion/epstein-suici... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/kristin-smart-inves... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/opinion/ezra-klein-pod... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/opinion/hegseth-kelly-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/opinion/hegseth-war-co... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/opinion/social-media-t... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/nyregion/mamdani-belle... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/movies/blake-lively-ju... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/us/postal-service-hand... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.nytimes.com/2026/05/08/world/europe/uk-electi... — Found in <a href>. Returns HTTP 403.

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

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

- **[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 long (66 characters) — Titles over 60 characters may be truncated in social sharing previews.
- **[INFO]** og:description is long (267 characters) — Descriptions over 200 characters may be truncated in social sharing previews.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

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

- **[INFO]** Missing recommended property "description" for WebSite — Adding "description" can improve how search engines display your content.
- **[PASS]** Custom type "NewsMediaOrganization" — 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]** 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]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

NewsMediaOrganization, WebSite

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

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

*No images to analyze*


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

*No autoplay media on the page*

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

---

## Infrastructure

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

*4 A records, 86 ms lookup*

- **[PASS]** Resolves to 4 IPv4 address(es)
- **[INFO]** No IPv6 (AAAA) records
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 86 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

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

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

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

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

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

*0/4 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 151.101.129.164: lookup 151.101.129.164: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 151.101.193.164: lookup 151.101.193.164: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 151.101.65.164: lookup 151.101.65.164: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 151.101.1.164: lookup 151.101.1.164: 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 1ms across 3 resolvers (spread 0ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 1ms
- **[PASS]** Google: 1ms

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

*No redirects — direct access*

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

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

*No IPv6 support*

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

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

*robots.txt present, sitemap with 717 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 717 entries
- **[PASS]** robots.txt references sitemap

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

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

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

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

*nytimes.com — via MarkMonitor Inc., 32 years, 9 months old, hosted on Fastly*

- **[PASS]** Domain registered until Jan 19, 2027 (8 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: MarkMonitor 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: Fastly

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (C — 60/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[CRITICAL]** 7 non-essential cookie(s) set without consent banner — Unrecognized (treated as non-essential): nyt-a, nyt-gdpr, nyt-purr, nyt-geo, datadome, nyt-s-present, nyt-traceid
- **[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)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

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

*All 9 hreflang tag(s) look correct*

- **[PASS]** All 9 hreflang tag(s) look correct

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

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 1 / 8 categories — Scanned the homepage body text for GDPR Article 13 disclosures. Matched 1 of 8 categories: Legal basis for processing. 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, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

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

*7 trackers detected*

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

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

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

- **[INFO]** 7 cookie(s) could not be classified
- **[INFO]** 7 third-party tracker(s) detected on page

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

*No image data to inspect for tracking pixels*

- **[PASS]** No image data to inspect for tracking pixels

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

*No browser-fingerprinting libraries detected*

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

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

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

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

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

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

- **[INFO]** 1 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 (B — 80/100)

*4 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://6sense.com/privacy-policy/.
- **[PASS]** Terms of Service detected — Found at https://help.nytimes.com/hc/en-us/articles/115014893428-Terms-of-Service.
- **[PASS]** Cookie Policy detected — Found at https://www.nytimes.com/privacy/cookie-policy.
- **[PASS]** Accessibility Statement detected — Found at https://help.nytimes.com/hc/en-us/articles/115015727108-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 The New York Times Company NYTCo Contact Us Access*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 The New York Times Company NYTCo Contact Us Access
- **[PASS]** Copyright holder: The New York Times Company NYTCo Contact Us Access

### Regulatory Indicators

*2 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .de; 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 link found: Accessibility. Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.

### Third-Party Data Sharing

*1 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: Tag Management (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.

### Compliance Badges (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 (A+ — 100/100)

*Fastly (HIT, MISS)*

- **[PASS]** Site is served via Fastly CDN
- **[PASS]** CDN cache status: HIT, MISS

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

*s-maxage=30,no-cache*

- **[PASS]** Cache-Control header is set
- **[PASS]** CDN TTL: 30 seconds (s-maxage=30)
- **[PASS]** Last-Modified header present

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

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

*Health endpoint at https://www.nytimes.com/health (HTTP 200)*

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

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

*Cache state: HIT*

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

---

## Accessibility

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

*10 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 7 <nav> landmark(s) found
- **[WARNING]** 2 of 7 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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

*54 headings*

- **[PASS]** Single H1 present
- **[WARNING]** 2 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

*All 22 images OK*

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

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

*All 20 controls labeled*

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

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

*19 issue(s) across 429 links and 78 buttons*

- **[CRITICAL]** 19 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 20 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 390 link(s) with descriptive text

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

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

- **[INFO]** Input "query" should use type="search" (currently type="text") — Field name "query" 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)

*20 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"*

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

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

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

- **[INFO]** tabindex="-1" on naturally-focusable <button id="fides-tab-features"> — 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 <button id="fides-tab-vendors"> — 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 <button id="fidesActiveMenuItem"> — 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 <button> — 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 <button> — 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 <button> — 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 <button id="fidesActiveMenuItem"> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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 <button> — 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)

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

- **[WARNING]** <iframe> missing title attribute (src="https://hbx.media.net/checksync.php?cid=8CU26C87G&cs=16&cv=37&hb=1&vsSync=1&ref…") — 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://static01.nyt.com/ads/tpc-check.html") — 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.
- **[WARNING]** <iframe> missing title attribute (src="") — 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.
- **[WARNING]** <iframe> missing title attribute (src="https://pay.google.com/gp/p/ui/payframe?origin=https%3A%2F%2Fwww.nytimes.com&mi…") — 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 (C — 75/100)

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

- **[WARNING]** 9 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 (A+ — 100/100)

*Font-size measurement not available for this scan*

- **[PASS]** Font-size measurement not available for this scan

---

## UX

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

*HTTP 404, custom page*

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

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

*6 icon(s) detected*

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

### Web Manifest (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 (B — 70/100)

*Dark mode detected*

- **[PASS]** prefers-color-scheme CSS detected in inline styles
- **[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 — 20/100)

*No navigation patterns*

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

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target reachable (self-referencing)

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

*Title: 66 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 66 characters — may be truncated in search results
- **[INFO]** Meta description is 267 characters — truncated on mobile (~160 char limit)
- **[PASS]** Title and H1 are well-aligned

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

*6036 words, Very Difficult*

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

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

*373 internal, 56 external*

- **[PASS]** 373 internal links (87%)
- **[PASS]** 96% of links use descriptive anchor text
- **[INFO]** Page has 429 links — consider reducing
- **[INFO]** 373 internal / 56 external links
- **[WARNING]** 2 internal links have no anchor text

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

*22 images, 22 descriptive filenames*

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

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

*Sitemap updated within 90 days (717/717 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 (717 URLs, 624 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*1.63g CO2 per view*

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

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

*Green (cdn)*

- **[PASS]** Fastly CDN uses renewable energy — Since most traffic is served through the CDN, the majority of data transfer energy is renewable.
- **[INFO]** Fastly: 100% renewable energy for edge network
- **[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 302 KB (vs 7039 KB first visit). 155 of 159 resources are served from browser cache, saving 1.56g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.07g CO2 (first visit: 1.63g)

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

*79th percentile*

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

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

*81% efficient*

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

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

*No detectable Google Fonts weights*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/dfc2bcaa-7a70-46b9-82e5-156d23da9915*