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

**Date:** August 17, 2026  
**URL:** https://rtx.com  
**Overall Grade:** B (83/100)  
**Report:** https://beavercheck.com/results/180fb2b3-8e5c-4761-abe9-531308d20ae6

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** HSTS header is missing — Security > Security Headers
3. **[CRITICAL]** 1 control(s) without accessible label — Accessibility > Form Accessibility
4. **[CRITICAL]** 1 image(s) missing alt attribute — Accessibility > Alt Text Quality
5. **[CRITICAL]** No H1 heading found — Accessibility > Heading Hierarchy

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 53 |
| Accessibility | 87 |
| Best Practices | 77 |
| SEO | 85 |

---

## Security

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

*9 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[PASS]** Cross-Origin-Opener-Policy is properly configured
- **[PASS]** Cross-Origin-Embedder-Policy is set
- **[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 (C — 65/100)

*6 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[PASS]** No 'unsafe-inline' in script source
- **[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
- **[PASS]** object-src falls back to default-src
- **[PASS]** base-uri is properly restricted
- **[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
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

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

*TLS 1.3, 7 checks passed*

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

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

*1 cookies analyzed, 3 checks passed*

- **[PASS]** Cookie '__cf_bm' has the Secure flag
- **[PASS]** Cookie '__cf_bm' has the HttpOnly flag
- **[PASS]** Cookie '__cf_bm' has SameSite=None

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

*All 1 cookie(s) pass hygiene checks*

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

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

*Cloudflare WAF (active mitigation)*

- **[PASS]** Cloudflare WAF (active mitigation) detected — Detected via: cf-ray: a2ca17532eec9dae-CDG; cf-mitigated: challenge

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

*No inline style attributes -- strict CSP is feasible*

- **[PASS]** No inline style attributes detected

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

*Trusted Types not enabled*

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

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

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

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

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

*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/23 third-party resources)*

- **[WARNING]** SRI adoption: 0/23 third-party resources protected (0%) — Of 23 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://prd-sc102-cdn.rtx.com/-/media/base-themes/rtx-third-party-components-themes/styles/pre-optimized-min.css?rev=ed3e10e00a6d49f59d28393551c94334&rid=fe5d7fdf89c04d999aa3b5fbd009c9f3&t=20231122T171254Z&hash=6B852A56E26F35B1CA5124FD81C63CD1
  - https://prd-sc102-cdn.rtx.com/-/media/base-themes/rtx-gdpr/styles/pre-optimized-min.css?rev=767f7fdbc15e4d7682cfe7ba309229d6&rid=fe5d7fdf89c04d999aa3b5fbd009c9f3&t=20220725T092858Z&hash=19AEF7772C8022000ABA3C821353F04C
  - https://prd-sc102-cdn.rtx.com/-/media/themes/raytheon-technologies/rtx-shared/rtx-theme/styles/pre-optimized-min.css?rev=fae6e93aabd542f789471abf9e1b7329&rid=fe5d7fdf89c04d999aa3b5fbd009c9f3&t=20260718T035959Z&hash=3AB877322ECBB7D8E9CED9A10F1214FE
  - https://prd-sc102-cdn.rtx.com/-/media/base-themes/news-template/styles/pre-optimized-min.css?rev=c118412b42c347d79216b7b8ed110de7&rid=fe5d7fdf89c04d999aa3b5fbd009c9f3&t=20230810T104401Z&hash=3C339B20D5EB8BAF94D09334953A38EA
  - https://prd-sc102-cdn.rtx.com/-/media/base-themes/cards/styles/pre-optimized-min.css?rev=7bf762a2c61f42158900d0eee724e96a&rid=fe5d7fdf89c04d999aa3b5fbd009c9f3&t=20250514T055017Z&hash=633332E9DAC3B099CC5780C89D6524CA

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

*90% high-risk feature coverage (9/10)*

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

Covered: camera, microphone, geolocation, payment, usb, serial, accelerometer, gyroscope, magnetometer

Not declared (default-allow): midi

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

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

*Referrer-Policy is `same-origin` (strict -- Referer sent only on same-origin requests)*

- **[PASS]** Referrer-Policy: `same-origin` -- strict -- Referer sent only on same-origin requests — Full URL Referer header on same-origin requests; no Referer at all on cross-origin. Strong privacy posture; same-origin analytics still work.

### 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 23 external resources have SRI*

- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from prd-sc102-cdn.rtx.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 ipmeta.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from prd-sc102-cdn.rtx.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 — 70/100)

*DMARC: reject, SPF: -all*

- **[PASS]** DMARC policy is reject — strongest protection
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

*16 directives, 0 missing*

- **[PASS]** accelerometer=() — blocked for all origins
- **[PASS]** camera=() — blocked for all origins
- **[PASS]** clipboard-read=() — blocked for all origins
- **[PASS]** clipboard-write=() — blocked for all origins
- **[PASS]** geolocation=() — blocked for all origins
- **[PASS]** gyroscope=() — blocked for all origins
- **[PASS]** hid=() — blocked for all origins
- **[PASS]** magnetometer=() — blocked for all origins
- **[PASS]** microphone=() — blocked for all origins
- **[PASS]** payment=() — blocked for all origins
- **[PASS]** publickey-credentials-get=() — blocked for all origins
- **[PASS]** screen-wake-lock=() — blocked for all origins
- **[PASS]** serial=() — blocked for all origins
- **[PASS]** sync-xhr=() — blocked for all origins
- **[PASS]** usb=() — blocked for all origins
- **[INFO]** xr-spatial-tracking=*

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (D — 41/100)

*2.5 MB transferred, 59 requests*

- **[WARNING]** Page weighs 3.9 MB (2.5 MB transferred)
- **[WARNING]** Images are 1.6 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[INFO]** Fonts are 293 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[INFO]** 59 HTTP requests
- **[INFO]** Estimated 0.53 g CO2 per page load

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

*100% third-party, 0 ms blocking*

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

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

*All text resources are compressed*

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

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

*16 images, 0 KB saveable*

- **[WARNING]** https://prd-sc102-cdn.rtx.com/-/media/themes/rayth... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (C — 60/100)

*1433ms total JS execution*

- **[WARNING]** Unattributable: 309ms CPU time
- **[WARNING]** https://www.rtx.com/cdn-cgi/challenge-platform/scr...: 280ms CPU time
- **[WARNING]** https://prd-sc102-cdn.rtx.com/-/media/base-themes/...: 269ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtm.js?id=GTM-KTM...: 217ms CPU time
- **[INFO]** https://www.rtx.com/: 188ms CPU time
- **[WARNING]** Third-party scripts: 1124ms (78% of total)

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

*7 fonts (293 KB)*

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

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

*15 scripts, 257 KB unused*

- **[WARNING]** https://prd-sc102-cdn.rtx.com/-/media/base-themes/...: 142 KB unused (76%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-KTM...: 67 KB unused (46%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://prd-sc102-cdn.rtx.com/-/media/base-themes/...: 48 KB unused (78%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 257 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*5 hints, 0 missing preconnects*

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

### HTTP/3 (QUIC) (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 (A+ — 100/100)

*Main response uses brotli*

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

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

*LCP preload audit not available*

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

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

*No Cache-Control header on main HTML response*

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

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

*1 Server-Timing entries advertised*

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

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

*2 server-response signal(s) detected*

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

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

*59 resources · 2.5 MB · 257 KB savings available*

- **[WARNING]** Page weight 2.5 MB exceeds 1 MB target by 1.5 MB
- **[INFO]** ~257 KB of savings available
- **[WARNING]** 58 third-party resources (100% of weight)
- **[INFO]** 3 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*1 JS blocking issue(s) detected*

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

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

*1 CSS depth issue(s) detected*

- **[WARNING]** 10 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)

*93 links checked, 61 healthy, 32 broken*

- **[CRITICAL]** 61 of 93 links are healthy
- **[WARNING]** Broken link: https://rtx.com/-/media/themes/raytheon-technologies/rtx-... — Found in <link href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/ — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://investors.rtx.com/stock-information/ — Found in <a href>. Get "https://investors.rtx.com/stock-information/": context deadline exceeded
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/our-leadership — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/our-businesses — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/our-responsibility — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/corporate-governance — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/global-presence — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/corporate-and-business-headqua... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/what-we-do — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/what-we-do/transformative-technologies — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/what-we-do/advanced-aviation — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/what-we-do/defense-innovation — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/news — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/news/media-resources — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://investors.rtx.com/ — Found in <a href>. Get "https://investors.rtx.com/": context deadline exceeded
- **[CRITICAL]** Broken link: https://rtx.com/suppliers — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/contacts — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/news/news-center/2026/08/17/rtxs-raytheon... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/news/2026/02/04/munitions-agreements — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/news/news-center/2026/07/21/rtxs-raytheon... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/we-are-rtx/rtx-big-questions/w... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/what-we-do/advanced-aviation/civil-missions — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/external-redirects/rtx-careers — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://www.instagram.com/rtxcorporation/ — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://rtx.com/rss-feeds/news — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/who-we-are/contract-vehicles — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/accessibility-statement — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/terms-of-use — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/privacy — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://rtx.com/rtx-gdpr/rtx-gdpr-overlay — 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 — 85/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 short (4 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

*OG image dimensions and Twitter card configuration look healthy*

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

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

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

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

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

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

Organization

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

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

*7 issues found across 18 images*

- **[WARNING]** 2 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 1 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 4 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 16 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.
- **[WARNING]** 1 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[WARNING]** 1 above-fold image(s) marked loading="lazy" (LCP anti-pattern) — Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://prd-sc102-cdn.rtx.com/-/media/themes/raytheon-technologies/rtx-shared/rtx-theme/images/rtx_logo.svg?rev=57e660dbd2ee4ef6895a84799210c5bf&rid=a5829bdc17c74537842441a8a1b055f2&w=354&hash=8D05565DA9D752EAC71DCCB8C57E972A.
- **[INFO]** 2 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://prd-sc102-cdn.rtx.com/-/media/rtx/news-images/2026/01/hp_sizzle_frame1_1920x1080.jpg?h=1080&iar=0&w=1920&rev=fbb5169be67545d6af89f10ad9e5b9bd&rid=e967f4c04ec241e18cd5f53c9954fc25&hash=2194FC72A70D5B937DD78A9D997B8E20, https://prd-sc102-cdn.rtx.com/-/media/ray/s/spy-6/spy-6.jpg?h=1080&iar=0&w=1920&rev=51bb938a39494412889f4404156e25a3&rid=e967f4c04ec241e18cd5f53c9954fc25&hash=D1E187AFFFDDC52AD5319E255823EE21.

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*2 A records, 87 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[PASS]** Has 2 IPv6 (AAAA) record(s)
- **[PASS]** 2 nameserver(s) configured
- **[PASS]** 2 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 87 ms

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

*No subdomain takeover risk detected*

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

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

*Signed and validating*

- **[PASS]** DNSSEC fully signed and chain validates (ECDSAP256SHA256)

### CAA Records (A+ — 100/100)

*issue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com | iodef configured*

- **[PASS]** CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com
- **[PASS]** CAA iodef tag present (failed-issuance notifications enabled)

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

*0/4 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 104.16.47.225: lookup 104.16.47.225: 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 104.18.112.152: lookup 104.18.112.152: 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 2606:4700::6812:7098: lookup 2606:4700::6812:7098: 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 2606:4700::6810:2fe1: lookup 2606:4700::6810:2fe1: 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 16ms across 3 resolvers (spread 24ms)*

- **[PASS]** Quad9: 3ms
- **[PASS]** Cloudflare: 20ms
- **[PASS]** Google: 27ms

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

*0 redirect(s), 67 ms total*


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

*IPv6 reachable (17 ms)*

- **[PASS]** IPv6 is configured and reachable at 2606:4700::6812:7098, 2606:4700::6810:2fe1

### Crawlability (B — 75/100)

*no robots.txt, no sitemap*

- **[INFO]** No robots.txt found — robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
- **[INFO]** No sitemap.xml found — A sitemap helps search engines discover and index your pages more efficiently.

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

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

- **[PASS]** HTTP correctly 301-redirects to HTTPS

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

*rtx.com — via Corsearch Domains LLC, 30 years, 9 months old*

- **[PASS]** Domain registered until Apr 17, 2031 (4 years, 8 months remaining)
- **[PASS]** DNSSEC is enabled
- **[PASS]** Registrar: Corsearch Domains LLC
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## 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
- **[PASS]** 1 essential cookie(s) on initial load — no consent required
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

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

*No consent-UX depth issues detected*

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

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

*1 known tracker(s) detected*

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

tag-manager: Google Tag Manager

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

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

*Lang attribute present*

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

### Hreflang Configuration (A+ — 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 (A+ — 95/100)

*4 trackers detected*

- **[INFO]** 4 third-party trackers detected — Found 3 analytics, 0 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.

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

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

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

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

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

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

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

### Legal Page Ecosystem (B — 70/100)

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacy, linked from footer.
- **[PASS]** Terms of Service detected — Found at /terms-of-use, linked from footer.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[PASS]** Accessibility Statement detected — Found at /accessibility-statement, linked from footer.
- **[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 RTX Accessibility Terms of use Privacy Manage cook*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 RTX Accessibility Terms of use Privacy Manage cook
- **[PASS]** Copyright holder: RTX Accessibility Terms of use Privacy Manage cook

### Regulatory Indicators

*2 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (moderate confidence) — Indicators suggesting GDPR may be relevant: 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.

### 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: Tag Management (1), CDN (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.
- **[INFO]** Cloudflare (CDN) — Detected via cookie name. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. Data Processing Agreement available.

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

*0 compliance badge(s) detected*

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

---

## Availability

### CDN & Delivery (B — 80/100)

*Cloudflare*

- **[PASS]** Site is served via Cloudflare CDN (edge: CDG)

### 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]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*Auth-protected health endpoint at https://rtx.com/health (HTTP 403)*

- **[PASS]** Auth-protected health endpoint exposed at https://rtx.com/health

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

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

*5 landmarks*

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

### Heading Hierarchy (B — 75/100)

*15 headings*

- **[CRITICAL]** No H1 heading found — Every page should have one H1 that describes the page content.

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

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

- **[WARNING]** 2 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:
  - H3: 174 chars
  - H3: 140 chars

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

*1 of 18 images have issues*

- **[CRITICAL]** 1 image(s) missing alt attribute — Images without alt text are invisible to screen readers.
- **[PASS]** 8 decorative image(s) correctly marked
- **[PASS]** 9 image(s) with good alt text

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

*1 of 2 controls have issues*

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

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

*2 issue(s) across 70 links and 7 buttons*

- **[WARNING]** 2 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 6 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 62 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 "searchBar" should use type="search" (currently type="text") — Field name "searchBar" 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)

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

*33 positive, 3 -1-on-focusable*

- **[WARNING]** Positive tabindex on <button>: tabindex=2 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=1 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <button>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <input id="searchBar">: tabindex=6 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <button>: tabindex=5 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <button>: tabindex=6 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[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.)
- **[WARNING]** Positive tabindex on <a>: tabindex=1 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

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

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

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

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

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

- **[WARNING]** 13 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: <a> 10.0px ("RTX"); <a> 10.0px ("Collins Aerospace"); <a> 10.0px ("Pratt & Whitney"); <a> 10.0px ("Raytheon"); <span> 10.0px ("RTX").

---

## UX

### 404 Error Page (F — 25/100)

*HTTP 403, custom page*

- **[WARNING]** Unexpected status code: HTTP 403 — Expected HTTP 404 but received 403. This may confuse search engine crawlers.
- **[PASS]** Custom styled 404 page

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

*1 icon(s) detected*

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

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

*Not found*

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

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

*No PWA depth issues detected*

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

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

*No dark mode signals*

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

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

*No print styles*

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

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

*No navigation patterns*

- **[PASS]** 2 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 (C — 55/100)

*Issues found*

- **[PASS]** Canonical tag present
- **[WARNING]** Canonical does not match final URL (https://rtx.com)
- **[CRITICAL]** Canonical target returns 403 — Search engines cannot follow this canonical, effectively orphaning this page.
- **[INFO]** Canonical points to a different domain
- **[WARNING]** Canonical www-ness doesn't match the final URL — Either the canonical has 'www.' and the final URL doesn't, or vice versa. Search engines may index both forms as duplicates. Pick one and use it consistently in the canonical AND the redirect target.

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

*Title: 10 chars*

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

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

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

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

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

*380 words, Very Difficult*

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

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

*47 internal, 23 external*

- **[PASS]** 47 internal links (67%)
- **[PASS]** 97% of links use descriptive anchor text
- **[INFO]** 47 internal / 23 external links

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

*18 images, 13 descriptive filenames*

- **[INFO]** 5 image(s) have hash/generic filenames
- **[INFO]** 1 image(s) missing alt text — see Accessibility tab

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

### Sitemap Freshness (C — 75/100)

*No sitemap.xml found*

- **[INFO]** No sitemap.xml found — Sitemaps help search engines discover and prioritize URLs. Not strictly required for small sites where every page is linked from the homepage, but recommended once a site grows beyond a few dozen URLs.

### Sitemap × Robots Consistency (C — 75/100)

*Sitemap or robots.txt missing -- consistency check skipped*

- **[INFO]** Cross-check skipped (sitemap or robots.txt absent)

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

*No sitemap to evaluate -- depth check is N/A*

- **[PASS]** No sitemap fetched -- depth check skipped

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

*1 markup-quality issue(s) detected*

- **[WARNING]** No `<meta charset>` declaration in HTML — The page has no `<meta charset="...">` tag. Browsers fall back to a default encoding (typically UTF-8 in modern browsers, but not guaranteed). Add `<meta charset="utf-8">` as the first child of `<head>` to make the encoding explicit.

---

## Sustainability

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

*0.60g CO2 per view*

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

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

*Green (both)*

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

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

*99% cached*

- **[PASS]** 99% reduction on repeat visits — Returning visitors download only 16 KB (vs 2596 KB first visit). 58 of 59 resources are served from browser cache, saving 0.60g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.60g)

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

*50th percentile*

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

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

*90% efficient*

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

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

*No detectable Google Fonts weights*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/180fb2b3-8e5c-4761-abe9-531308d20ae6*
