# BeaverCheck Audit Report — https://conengagroup.com **Date:** July 10, 2026 **URL:** https://conengagroup.com **Overall Grade:** B (84/100) **Report:** https://beavercheck.com/results/2fc96780-115f-4214-952c-42a2b63d068a ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy 3. **[CRITICAL]** Page weighs 29.7 MB (14.7 MB transferred) — Performance > Page Weight Budget 4. **[CRITICAL]** 7 link(s) with no accessible text — Accessibility > Link & Button Quality 5. **[CRITICAL]** No H1 heading found — Accessibility > Heading Hierarchy --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 38 | | Accessibility | 88 | | Best Practices | 100 | | SEO | 100 | --- ## Security ### Security Headers (C — 65/100) *6 of 10 headers properly configured* - **[WARNING]** HSTS is missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP. - **[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 - **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis. - **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'. - **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers. - **[PASS]** X-Powered-By header is not present - **[PASS]** Server header is present without version info - **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload). ### Content Security Policy (F — 0/100) *No enforcing CSP policy found* - **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading. - **[INFO]** Content-Security-Policy-Report-Only is set but does not enforce — Report-Only logs violations but does not block them. Deploy an enforcing policy when ready. ### 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 74 days) - **[PASS]** Certificate chain has 3 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 4 domain(s) - **[PASS]** Certificate is issued by a trusted CA ### Cookie Security (A+ — 100/100) *No cookies set — no cookie security risks* - **[PASS]** No cookies set — no cookie security risks ### Cookie Hygiene (A+ — 100/100) *No cookies set -- cookie-hygiene check is N/A* - **[PASS]** No cookies set ### WAF / Bot Protection (B — 75/100) *No WAF detected via response headers* - **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva. ### security.txt (C — 60/100) *No security.txt file found* - **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field. ### Cross-Origin Tab Safety (A+ — 100/100) *All 26 new-tab link(s) carry rel=noopener* - **[PASS]** All 26 new-tab link(s) carry rel=noopener ### CSP Inline-Style Readiness (D — 60/100) *192 inline style attribute(s) detected* - **[WARNING]** 192 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. 192 inline style(s) is high. Affected element types include: div, span, h2, a, i. 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 (A+ — 100/100) *Page has no third-party scripts or stylesheets -- SRI not applicable* - **[PASS]** No third-party scripts or stylesheets to protect with SRI ### 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 (D — 50/100) *30% high-risk feature coverage (3/10)* - **[WARNING]** Permissions-Policy covers 3/10 high-risk features (30%) — The Permissions-Policy header explicitly declares policies for 3/10 high-risk features. Covered: camera, microphone, geolocation Not declared (default-allow): payment, usb, serial, midi, accelerometer, gyroscope, magnetometer 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 `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)* - **[PASS]** Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin — The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value. ### Source Map Exposure (A+ — 100/100) *No source maps accessible (probed 3 candidate URL(s))* - **[PASS]** No source maps accessible across 3 probed candidate(s) ### HTML Version Disclosure (D — 60/100) *2 software version(s) disclosed in HTML* - **[WARNING]** 2 software version(s) disclosed in HTML: Site Kit by Google 1.182.0, WPML ver:4.9.5 stt:1,3; — Each disclosed version enables direct CVE lookup -- an attacker who knows you run WordPress 6.4.2 (or whatever specific version) can search the CVE database for known exploits and target accordingly. Remove via your CMS config: WordPress (`remove_action('wp_head', 'wp_generator')`); Drupal (System / Reports / Status report -> Hide generator); Joomla (Global Configuration -> Hide generator); Hugo/Jekyll (delete or override the {{ .Site.Generator }} template hook). For HTML comments, audit your template files directly. ### 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 (A+ — 100/100) *No external resources* - **[PASS]** No external resources to protect ### 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 (A — 85/100) *DMARC: reject, SPF: -all, DKIM* - **[PASS]** DMARC policy is reject — strongest protection - **[INFO]** DMARC enforced on only 25% of failing mail (pct=25) — Receivers apply your policy to only this percentage of authentication failures. The rest are delivered as if no policy existed. Move to pct=100 once you've verified DMARC reports look clean. - **[PASS]** SPF ends in -all (hard fail) — strongest setting - **[PASS]** DKIM configured (selectors: selector2, selector1, k2, s1, s2) - **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts. and a policy file at https://mta-sts./.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.. - **[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 (B — 75/100) *3 directives, 2 missing* - **[PASS]** geolocation=() — blocked for all origins - **[PASS]** microphone=() — blocked for all origins - **[PASS]** camera=() — blocked for all origins - **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content. - **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content. ### CORS Configuration (B — 80/100) *No CORS headers* - **[PASS]** No CORS headers present — secure default --- ## Performance ### Page Weight Budget (F — 0/100) *14.7 MB transferred, 353 requests* - **[CRITICAL]** Page weighs 29.7 MB (14.7 MB transferred) - **[WARNING]** Images are 13.5 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size. - **[INFO]** CSS is 499 KB — consider purging unused styles — Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size. - **[WARNING]** 353 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests. - **[INFO]** Estimated 3.1 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *0% third-party, 0 ms blocking* - **[INFO]** Third-party code accounts for 0% of page weight (66.7 KiB of 14.7 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) *101 images, 0 KB saveable* - **[PASS]** All images are well-optimized ### JS Execution Cost (F — 20/100) *7771ms total JS execution* - **[WARNING]** https://conengagroup.com/wp-includes/js/jquery/jqu...: 1603ms CPU time - **[WARNING]** https://conengagroup.com/wp-content/plugins/fusion...: 1240ms CPU time - **[WARNING]** Unattributable: 1149ms CPU time - **[WARNING]** https://conengagroup.com/en/: 833ms CPU time - **[WARNING]** https://conengagroup.com/wp-content/plugins/fusion...: 824ms CPU time - **[INFO]** Third-party scripts: 125ms (2% of total) ### Font Loading (A+ — 100/100) *7 fonts (161 KB)* - **[INFO]** 7 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (C — 60/100) *139 scripts, 242 KB unused* - **[WARNING]** https://matomo.conengagroup.com/matomo.js: 37 KB unused (56%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://conengagroup.com/wp-content/plugins/sitepr...: 29 KB unused (50%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://conengagroup.com/wp-content/plugins/sitepr...: 29 KB unused (50%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://conengagroup.com/wp-content/themes/Avada/i...: 29 KB unused (56%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://conengagroup.com/wp-content/themes/Avada/i...: 29 KB unused (56%) — Consider code splitting or tree shaking to reduce unused code. - **[INFO]** Total unused JavaScript: 242 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) *1 hints, 0 missing preconnects* - **[PASS]** Page uses 1 resource hint(s) ### HTTP/3 (QUIC) (B — 75/100) *HTTP/3 not advertised* - **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads. ### Compression Algorithm (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 (B — 80/100) *No Cache-Control header on main HTML response* - **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift. ### Server-Timing Observability (B — 85/100) *No Server-Timing header found* - **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge. ### Server Response Intelligence (A+ — 95/100) *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: ""` (or `Last-Modified: `) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth. ### Page Weight Inventory (C — 55/100) *353 resources · 14.7 MB · 242 KB savings available* - **[WARNING]** Page weight 14.7 MB exceeds 1 MB target by 13.7 MB - **[INFO]** ~242 KB of savings available - **[INFO]** 6 third-party resources (0% of weight) - **[INFO]** 25 resources over 200KB ### Render-Blocking Resources (A+ — 100/100) *No render-blocking resources detected* - **[PASS]** No render-blocking resources detected in ### Third-Party Resources (A+ — 100/100) *No third-party resources detected* ### JavaScript Blocking (B — 78/100) *2 JS blocking issue(s) detected* - **[WARNING]** 3 render-blocking