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

**Date:** August 23, 2026  
**URL:** https://ge.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/953c2243-d2a0-47fa-bfe2-dd8a28431c45

## Top Findings

1. **[CRITICAL]** Cookie 'AWSALB' is missing the Secure flag — Security > Cookie Security
2. **[CRITICAL]** 8 image(s) missing alt attribute — Accessibility > Alt Text Quality
3. **[WARNING]** 105 render-blocking stylesheet(s) -- recommended: <=3 — Performance > CSS Performance Depth
4. **[WARNING]** 110 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
5. **[WARNING]** 2 publicly-accessible JavaScript source map(s) — Security > Source Map Exposure

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 26 |
| Accessibility | 87 |
| Best Practices | 69 |
| SEO | 92 |

---

## Security

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

*5 of 10 headers properly configured*

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

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

*2 of 11 CSP checks passed*

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

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

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 83 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 (B — 70/100)

*3 cookies analyzed, 5 checks passed*

- **[CRITICAL]** Cookie 'AWSALB' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'AWSALB' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'AWSALB' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[PASS]** Cookie 'AWSALBCORS' has the Secure flag
- **[WARNING]** Cookie 'AWSALBCORS' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'AWSALBCORS' has SameSite=None
- **[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 3 cookie(s) pass hygiene checks*

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

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

*Cloudflare*

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

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

*No security.txt file found*

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

### Cross-Origin Tab Safety (D — 60/100)

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

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

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

*45 inline style attribute(s) detected*

- **[WARNING]** 45 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. 45 inline style(s) is moderate. Affected element types include: section, div, h3, p, 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.

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

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

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

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

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

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

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

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

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

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

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

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

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

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

### Subresource Integrity Adoption (D — 50/100)

*2% SRI adoption (1/37 third-party resources)*

- **[WARNING]** SRI adoption: 1/37 third-party resources protected (2%) — Of 37 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (2%) 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):
  - //maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css
  - //maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
  - https://snap.licdn.com/li.lms-analytics/insight.old.min.js
  - https://snap.licdn.com/li.lms-analytics/insight.old.min.js
  - https://snap.licdn.com/li.lms-analytics/insight.old.min.js

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### HTML Version Disclosure (B — 90/100)

*1 generator tag(s) without version info*

- **[INFO]** 1 generator tag(s) without version info: Drupal 10 (https://www.drupal.org) — Generator tags reveal the CMS / build tool but no version specifics. Attackers can't directly cross-reference CVEs but can probe known weaknesses for the named platform. Removing the tag entirely is preferable; most CMSes have a one-config-flag option to suppress it.

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

*1 of 37 external resources have SRI*

- **[WARNING]** External link from maxcdn.bootstrapcdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from maxcdn.bootstrapcdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.youtube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.taboola.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.youtube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.ads-twitter.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from snap.licdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.google-analytics.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from connect.facebook.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.youtube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.evidon.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 googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from googleads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from acsbap.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from static.cloudflareinsights.com has SRI protection
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

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

*No known vulnerabilities*

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

### Information Leakage (A+ — 100/100)

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (F — 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 (D — 40/100)

*No header set*

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

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

*No CORS headers*

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

---

## Performance

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

*3.0 MB transferred, 330 requests*

- **[WARNING]** Page weighs 8.6 MB (3.0 MB transferred)
- **[WARNING]** JavaScript is 1.7 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** CSS is 268 KB — consider purging unused styles — Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.
- **[INFO]** Fonts are 246 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** 330 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.64 g CO2 per page load

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

*45% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 45% of page weight (1.4 MiB of 3.0 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

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

*All text resources are compressed*

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

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

*46 images, 0 KB saveable*

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

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

*4800ms total JS execution*

- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-PM8...: 943ms CPU time
- **[WARNING]** Unattributable: 887ms CPU time
- **[WARNING]** https://www.ge.com/: 457ms CPU time
- **[WARNING]** https://www.ge.com/cdn-cgi/challenge-platform/scri...: 348ms CPU time
- **[WARNING]** https://c.evidon.com/sitenotice/evidon-sitenotice-...: 323ms CPU time
- **[WARNING]** Third-party scripts: 2609ms (54% of total)

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

*10 fonts (246 KB)*

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

### JS Bundles (D — 40/100)

*137 scripts, 393 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-M2Q4...: 70 KB unused (42%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-108...: 59 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-109...: 56 KB unused (38%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-PM8...: 55 KB unused (34%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-750...: 53 KB unused (35%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 393 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)

*6 hints, 0 missing preconnects*

- **[PASS]** Page uses 6 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 (B — 80/100)

*Main response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### 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 max-age=60 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=60 (≤ 5min) is appropriate

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

*3 Server-Timing entries advertised*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: X-Bin,Cookie — 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 (D — 40/100)

*330 resources · 3.0 MB · 393 KB savings available*

- **[WARNING]** Page weight 3.0 MB exceeds 1 MB target by 2.0 MB
- **[INFO]** ~393 KB of savings available
- **[WARNING]** 93 third-party resources (45% of weight)
- **[INFO]** 2 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*2 JS blocking issue(s) detected*

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

*200 links checked, 198 healthy, 2 broken*

- **[WARNING]** 198 of 200 links are healthy
- **[WARNING]** Broken link: https://https://www.ge.com/ — Found in <link href>. Get "https://https//www.ge.com/": resolve https: lookup https: no such host
- **[CRITICAL]** Broken link: https://jobs.gecareers.com/aviation/global/en/accessibility — Found in <a href>. Get "https://jobs.gecareers.com/aviation/global/en/accessibility": resolve jobs.gecareers.com: lookup jobs.gecareers.com: no such host

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

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

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

### Open Graph (F — 0/100)

*No Open Graph tags found — social sharing previews will be generic.*

- **[WARNING]** No Open Graph meta tags found — Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

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

*No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)*

- **[PASS]** No OG image / Twitter card to evaluate

### Structured Data (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

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

*6 issues found across 19 images*

- **[WARNING]** 5 images significantly larger than display size — Resizing to display dimensions could save approximately 358 KB.
- **[WARNING]** 7 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 11 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 1 of 19 images use legacy formats
- **[WARNING]** 9 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[INFO]** 4 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://www.ge.com/sites/default/files/2024-07/webbanner-02-resized.webp, https://www.ge.com/sites/default/files/2023-07/pas-1920x850.webp, https://www.ge.com/sites/default/files/2024-07/gev_1920x850-resized.webp (+1 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*2 A records, 33 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[PASS]** Has 2 IPv6 (AAAA) record(s)
- **[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: 33 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 172.64.148.207: lookup 172.64.148.207: 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.39.49: lookup 104.18.39.49: 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 2a06:98c1:310c::ac40:94cf: lookup 2a06:98c1:310c::ac40:94cf: 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 2a06:98c1:310b::6812:2731: lookup 2a06:98c1:310b::6812:2731: 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 24ms across 3 resolvers (spread 9ms)*

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

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

*No redirects — direct access*

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

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

*IPv6 reachable (16 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a06:98c1:310c::ac40:94cf, 2a06:98c1:310b::6812:2731

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

*robots.txt present, sitemap with 26 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 26 entries
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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

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

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

*ge.com — via CSC Corporate Domains, Inc., 40 years, 7 months old, hosted on VERCARA - Vercara, LLC, US*

- **[PASS]** Domain registered until Dec 20, 2026 (3 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: CSC Corporate Domains, Inc.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
- **[PASS]** Hosting: VERCARA - Vercara, LLC, US

---

## 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]** 3 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)

*No known trackers detected on this page*

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

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

*Lang attribute + Content-Language header*

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

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

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

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

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

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

*No accessibility statement detected*

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

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

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

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

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

*8 trackers detected*

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

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

*3 cookies · 8 trackers · 0 pre-consent*

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

### Tracking Pixel Inventory (C — 75/100)

*9 tracking pixel(s) on the page*

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

### 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): AWSALBCORS, __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 (C — 60/100)

*2 of 7 expected legal pages detected*

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

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

*© 2026 General Electric Company We use cookies to persona*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 General Electric Company We use cookies to persona
- **[PASS]** Copyright holder: General Electric Company We use cookies to persona

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

*5 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]** 5 third-party services across 4 categories — 5 third-party services detected across 4 categories: Analytics (1), Tag Management (1), Advertising (2), CDN (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Facebook Pixel (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, User behavior, Ad targeting. Privacy policy: https://www.facebook.com/privacy/policy. Data Processing Agreement available.
- **[INFO]** LinkedIn Insight (Advertising) — Detected via script URL. Typically collects: Page views, Conversions, Ad targeting, Professional demographics. Privacy policy: https://www.linkedin.com/legal/privacy-policy. 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 (BYPASS)*

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

### HTTP Caching (A+ — 95/100)

*max-age=60 (1 minute)*

- **[PASS]** Cache-Control header is set
- **[PASS]** Effective TTL: 1 minute (max-age=60)
- **[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 (B — 75/100)

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

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** HSTS max-age is short: 180 days — HSTS max-age should be at least 1 year (31536000 seconds).
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

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

*Cache state: BYPASS*

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

---

## Accessibility

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

*4 landmarks*

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

### Heading Hierarchy (F — 20/100)

*23 headings, 5 skip(s)*

- **[PASS]** Single H1 present
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H3 → H6 (missing H4) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H3 → H6 (missing H4) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H3 → H6 (missing H4) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H2 → H6 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** 1 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

*All 23 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (C — 60/100)

*8 of 19 images have issues*

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

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

*No form controls*

- **[PASS]** No form controls on this page

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

*3 issue(s) across 52 links and 14 buttons*

- **[WARNING]** 3 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 18 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 31 link(s) with descriptive text

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

*No form controls on this page*

- **[PASS]** No form controls on this page

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

*No form controls on this page*

- **[PASS]** No form controls on this page

### Mobile Keyboard & Autofill (A+ — 100/100)

*No form controls -- mobile keyboard check is N/A*

- **[PASS]** No form controls on this page

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

*Lang attribute set to "en"*

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

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

*6 positive, 14 -1-on-focusable*

- **[INFO]** tabindex="-1" on naturally-focusable <a> — tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
- **[INFO]** tabindex="-1" on naturally-focusable <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 <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 <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 id="slick-slide-control01"> — 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="slick-slide-control02"> — 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="slick-slide-control03"> — 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.)
- **[WARNING]** Positive tabindex on <div id="_evidon_banner">: 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=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=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 <button id="_evidon-decline-button">: 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 <button id="_evidon-accept-button">: 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 <button id="_evidon-option-button">: 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.

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

*2/2 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.
- **[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)

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

- **[WARNING]** 7 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: <button> 0.0px ("Previous"); <a> 11.0px ("Learn more"); <a> 11.0px ("learn more"); <button> 0.0px ("Next"); <a> 11.0px ("Visit GE Aerospace").

---

## UX

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

*HTTP 429, custom page*

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

### Favicon & Branding (C — 65/100)

*7 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
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (C — 60/100)

*Valid manifest*

- **[WARNING]** No name or short_name — Add a name field to identify the app.
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*1 PWA signal(s) surfaced*

- **[INFO]** Manifest has no maskable icon — Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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

*Theme color only*

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

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

*No print styles*

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

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

*1 navigation pattern(s)*

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

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Properly configured*

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

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (59 chars) is optimal
- **[PASS]** Meta description length (157 chars) is optimal
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

*1 title-style issue(s) detected*

- **[INFO]** Title uses 2 different separator characters: :, | — The page title `GE Companies: Next Generation and Future | General Electric` uses multiple separator characters (:, |). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.

### Content Depth (F — 25/100)

*291 words, Very Difficult*

- **[WARNING]** Page has 291 words — thin content — Most well-ranking pages have 300+ words of substantive content.
- **[INFO]** Text-to-HTML ratio is 2% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Very Difficult (grade 33)
- **[WARNING]** Thin content — only 291 words

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

*30 internal, 22 external*

- **[PASS]** 30 internal links (58%)
- **[PASS]** 94% of links use descriptive anchor text
- **[INFO]** 30 internal / 22 external links

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

*19 images, 18 descriptive filenames*

- **[INFO]** 1 image(s) have hash/generic filenames
- **[INFO]** 9 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 (A+ — 100/100)

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

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

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

*No sitemap-vs-robots conflicts in the URL sample*

- **[PASS]** All 5 sampled sitemap URLs are crawlable per robots.txt

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

*Sitemap structure / size look healthy (26 URLs, 4 KB)*

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

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

*1 markup-quality issue(s) detected*

- **[INFO]** 2 redundant ARIA role attribute(s) on native semantic element(s) — The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.

---

## Sustainability

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

*0.72g CO2 per view*

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

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

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Amazon Web Services: 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)

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 13 KB (vs 3122 KB first visit). 329 of 330 resources are served from browser cache, saving 0.72g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.72g)

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

*53th percentile*

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

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

*87% efficient*

- **[INFO]** Transfer efficiency: 87% — An estimated 392 KB (13%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 392 KB of unused JavaScript. This wasted data produces 0.09g 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/953c2243-d2a0-47fa-bfe2-dd8a28431c45*