landmark found — Accessibility > Landmark Structure 3. **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — Accessibility > 404 Error Page 4. **[WARNING]** 70 third-party resources (100% of weight) — Performance > Page Weight Inventory 5. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 61 | | Accessibility | 90 | | Best Practices | 81 | | SEO | 85 | --- ## Security ### Security Headers (C — 65/100) *6 of 10 headers properly configured* - **[PASS]** Strict-Transport-Security is properly configured - **[PASS]** X-Content-Type-Options is properly configured - **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN. - **[PASS]** Referrer-Policy is properly configured - **[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 (C — 65/100) *2 of 10 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 tag to hijack relative URLs. Set it to 'self' or 'none'. - **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'. - **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking. - **[PASS]** upgrade-insecure-requests is enabled ### 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 36 days) - **[PASS]** Certificate chain has 2 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 2 domain(s) - **[PASS]** Certificate is issued by a trusted CA ### Cookie Security (A+ — 100/100) *No cookies set — no cookie security risks* - **[PASS]** No cookies set — no cookie security risks ### Cookie Hygiene (A+ — 100/100) *No cookies set -- cookie-hygiene check is N/A* - **[PASS]** No cookies set ### WAF / Bot Protection (B — 75/100) *No WAF detected via response headers* - **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva. ### security.txt (B — 70/100) *Vulnerability disclosure policy* - **[PASS]** security.txt found - **[WARNING]** security.txt: Missing required 'Contact' field - **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116) ### Cross-Origin Tab Safety (A+ — 100/100) *No new-tab links found -- no tabnabbing surface* - **[PASS]** No new-tab links present ### CSP Inline-Style Readiness (B — 90/100) *1 inline style attribute(s) detected* - **[INFO]** 1 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. 1 inline style(s) is low. Affected element types include: body. 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) *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 (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 — 90/100) *1 CORS depth signal(s) detected* - **[INFO]** CORS allows any origin (`Access-Control-Allow-Origin: *`) — Any website can fetch this URL via JavaScript and read the response body. Acceptable for genuinely public APIs (e.g. CDN-served static assets). Risky if the URL returns user-specific or session-derived data, since other origins can scrape it via the user's browser without needing credentials. Narrow Allow-Origin to a specific origin allow-list when the response is sensitive. ### 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 (D — 50/100) *Referrer-Policy is `no-referrer-when-downgrade` (leaky -- legacy default that sends full URL cross-origin on HTTPS-to-HTTPS)* - **[WARNING]** Referrer-Policy: `no-referrer-when-downgrade` -- leaky -- legacy default that sends full URL cross-origin on HTTPS-to-HTTPS — The legacy browser default (Chrome <85, Firefox <87). Sends the full URL (path + query) Referer on cross-origin requests as long as the protocol doesn't downgrade. This means session IDs, tracking tokens, search queries, etc. embedded in URLs leak to every third-party HTTPS origin the page links to or embeds. Switch to `strict-origin-when-cross-origin`. ### 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 (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* - **[PASS]** security.txt is present — good practice - **[PASS]** No sensitive files exposed ### Email Security (C — 69/100) *DMARC: quarantine, SPF: ~all, DKIM* - **[PASS]** DMARC policy is quarantine — good protection - **[INFO]** DMARC configured without rua= aggregate reporting — Without rua=, you have no visibility into spoof attempts or auth failures from your own legitimate senders. Add rua=mailto:dmarc@ (or a managed inbox at a reporting service). - **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify). - **[PASS]** DKIM configured (selectors: google, mail, s2, s1) - **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts. 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 (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 (C — 60/100) *Origin: ** - **[INFO]** Access-Control-Allow-Origin: * — unrestricted — Any website can read this resource's response. Appropriate for public APIs but not for user-specific content. - **[INFO]** Origin reflection not testable with a single request — Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header. --- ## Performance ### Page Weight Budget (D — 48/100) *2.3 MB transferred, 71 requests* - **[INFO]** Page weighs 4.6 MB (2.3 MB transferred) - **[WARNING]** Images are 1.4 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size. - **[WARNING]** JavaScript is 500 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts. - **[INFO]** 71 HTTP requests - **[INFO]** Estimated 0.48 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.3 MiB of 2.3 MiB) - **[PASS]** Third-party blocking time is low (0 ms) ### Text Compression (A+ — 100/100) *All text resources are compressed* - **[PASS]** All text resources are compressed ### Image Optimization (A — 85/100) *14 images, 0 KB saveable* - **[PASS]** All images are well-optimized ### JS Execution Cost (C — 60/100) *1658ms total JS execution* - **[WARNING]** https://www.rjwdigital.com.au/: 643ms CPU time - **[WARNING]** Unattributable: 430ms CPU time - **[INFO]** https://www.googletagmanager.com/gtag/js?id=G-E7E0...: 192ms CPU time - **[INFO]** https://connect.facebook.net/en_US/fbevents.js: 106ms CPU time - **[INFO]** https://connect.facebook.net/signals/config/548133...: 99ms CPU time - **[WARNING]** Third-party scripts: 1658ms (100% of total) ### Font Loading (A+ — 100/100) *9 fonts (198 KB)* - **[INFO]** 9 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (C — 60/100) *21 scripts, 191 KB unused* - **[WARNING]** https://b-cloud.becdn.net/builds/free/359-cloud/ed...: 70 KB unused (81%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-E7E0...: 63 KB unused (43%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://connect.facebook.net/en_US/fbevents.js: 32 KB unused (33%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://b-cloud.becdn.net/builds/pro/232-cloud/js/...: 26 KB unused (68%) — Consider code splitting or tree shaking to reduce unused code. - **[INFO]** Total unused JavaScript: 191 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) *No optimization needed* - **[PASS]** No resource hint issues ### HTTP/3 (QUIC) (B — 75/100) *HTTP/3 not advertised* - **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads. ### Compression Algorithm (C — 70/100) *Main response served uncompressed* - **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads. ### LCP Image Preload (A+ — 100/100) *LCP preload audit not available* - **[PASS]** LCP image preload audit not available for this scan ### Main HTML Cache-Control (A+ — 100/100) *Main HTML uses no-store -- correct for sensitive/dynamic content* - **[PASS]** Main HTML uses no-store -- correct for sensitive/dynamic content ### Server-Timing Observability (B — 85/100) *No Server-Timing header found* - **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge. ### Server Response Intelligence (A+ — 95/100) *1 server-response signal(s) detected* - **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: ""` (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 (D — 45/100) *71 resources · 2.3 MB · 191 KB savings available* - **[WARNING]** Page weight 2.3 MB exceeds 1 MB target by 1.3 MB - **[INFO]** ~191 KB of savings available - **[WARNING]** 70 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 ### Third-Party Resources (A+ — 100/100) *No third-party resources detected* ### JavaScript Blocking (A+ — 100/100) *No render-blocking JS or document.write usage detected* - **[PASS]** No JavaScript blocking issues detected ### CSS Performance Depth (A+ — 100/100) *No CSS performance depth issues detected* - **[PASS]** No CSS performance depth issues detected --- ## Content Quality ### Links (A+ — 100/100) *No links to check.* - **[PASS]** No links found on the page ### 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 `