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

**Date:** May 10, 2026  
**URL:** https://perryhomes.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/e405fc7f-f46e-4b44-b6c3-023eb8fc5277

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[WARNING]** 10 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
4. **[WARNING]** 143 HTTP requests — consider bundling or reducing — Performance > Page Weight Budget
5. **[WARNING]** 4 render-blocking stylesheet(s) -- recommended: <=3 — Performance > CSS Performance Depth

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 31 |
| Accessibility | 95 |
| Best Practices | 73 |
| SEO | 92 |

---

## Security

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

*5 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
- **[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 (D — 45/100)

*4 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[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.

### 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 86 days)
- **[PASS]** Certificate chain has 2 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 (D — 60/100)

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

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

*40 inline style attribute(s) detected*

- **[WARNING]** 40 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. 40 inline style(s) is moderate. Affected element types include: body, img, div, button, article. 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 (F — 30/100)

*0% SRI adoption (0/27 third-party resources)*

- **[WARNING]** SRI adoption: 0/27 third-party resources protected (0%) — Of 27 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://s2.adform.net/banners/scripts/st/trackpoint-async.js
  - https://js.hscollectedforms.net/collectedforms.js
  - https://js.hs-analytics.net/analytics/1778414400000/5016179.js
  - https://js.hs-banner.com/v2/5016179/banner.js
  - https://www.redditstatic.com/ads/pixel.js?pixel_id=a2_ivqw7bocplbk

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

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

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

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

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

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

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

*No software-version disclosures in HTML*

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

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

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

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

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

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

*No risky subdomain names in certificate SANs*

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

---

## Advanced Security

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

*0 of 27 external resources have SRI*

- **[WARNING]** External script from s2.adform.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from js.hscollectedforms.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from js.hs-analytics.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from js.hs-banner.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.redditstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.lytics.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tags.srv.stackadapt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from storage.cloud.kargo.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.hotjar.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 perryhomes.my.site.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from perryhomes.my.site.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from maps.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from tags.srv.stackadapt.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 js-na1.hs-scripts.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from js.hs-scripts.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from 108073.tctm.co lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from perryhomes.my.site.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

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

*No known vulnerabilities*

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

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

*No exposures*

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

### Email Security (B — 72/100)

*DMARC: quarantine, SPF: ~all, DKIM*

- **[PASS]** DMARC policy is quarantine — good protection
- **[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: smtpapi, k2, selector1, k1, 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.<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 — 15/100)

*3.4 MB transferred, 143 requests*

- **[WARNING]** Page weighs 11.1 MB (3.4 MB transferred)
- **[WARNING]** JavaScript is 2.1 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** Fonts are 833 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** 143 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.71 g CO2 per page load

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

*56% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 56% of page weight (1.9 MiB of 3.4 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)

*22 images, 0 KB saveable*

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

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

*4796ms total JS execution*

- **[WARNING]** Unattributable: 645ms CPU time
- **[WARNING]** https://perryhomes.com/: 536ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-KFQ...: 517ms CPU time
- **[WARNING]** https://js.hs-analytics.net/analytics/177841440000...: 488ms CPU time
- **[WARNING]** https://perryhomes.com/_next/static/chunks/7023-17...: 459ms CPU time
- **[WARNING]** Third-party scripts: 3483ms (73% of total)

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

*9 fonts (833 KB)*

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

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

*74 scripts, 443 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-CNS7...: 67 KB unused (39%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-KFQ...: 61 KB unused (31%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://maps.googleapis.com/maps-api-v3/api/js/64/...: 54 KB unused (65%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://perryhomes.com/_next/static/chunks/4027-9a...: 33 KB unused (87%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://connect.facebook.net/en_US/fbevents.js: 31 KB unused (32%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 443 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 — 85/100)

*12 hints, 0 missing preconnects*

- **[WARNING]** 9 font preload(s) missing `crossorigin` -- font will be downloaded twice — Fonts are always fetched as crossorigin=anonymous; a preload without the attribute creates a different cache key, so the browser refetches when the actual font request happens. Sample: /_next/static/media/1d8c655f89aebb8a-s.p.ttf, /_next/static/media/1fc0c74dec9a0f56-s.p.ttf, /_next/static/media/2bcf28b7fb0a1dab-s.p.ttf (+6 more). Add `crossorigin` (or `crossorigin="anonymous"`) to each preload.
- **[PASS]** Page uses 12 resource hint(s)

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Compression Algorithm (C — 70/100)

*Main response served uncompressed*

- **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

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

*LCP preload audit not available*

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

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=0 (≤ 5min) is appropriate*

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

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

*No Server-Timing header found*

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

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

*3 server-response signal(s) detected*

- **[PASS]** `Cache-Status` header present (RFC 9211): "Netlify Durable"; hit; ttl=21, "Next.js"; hit, "Netlify Edge"; fwd=miss — The page returns a `Cache-Status` header -- the standardized way for CDNs and caches to communicate per-hop cache state to debugging tools. Format: `Cache-Status: cdn-name; hit; ttl=300` (or `; fwd=miss` / `; fwd=stale`). Standard alternative to vendor-specific `X-Cache` patterns each CDN had historically. Cloudflare, Fastly, and Akamai all support emitting it.
- **[PASS]** `Vary` header declared: RSC,Next-Router-State-Tree,Next-Router-Prefetch,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).
- **[PASS]** `ETag` present -- conditional GET supported

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

*143 resources · 3.4 MB · 443 KB savings available*

- **[WARNING]** Page weight 3.4 MB exceeds 1 MB target by 2.4 MB
- **[INFO]** ~443 KB of savings available
- **[WARNING]** 91 third-party resources (56% of weight)
- **[INFO]** 1 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]** 10 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]** 4 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+ — 100/100)

*158 links checked, 158 healthy, 0 broken*

- **[PASS]** 158 of 158 links are healthy

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

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

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

### Open Graph (A — 95/100)

*Open Graph tags are well configured for social sharing.*

- **[INFO]** og:title is short (18 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** og:description is long (210 characters) — Descriptions over 200 characters may be truncated in social sharing previews.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.

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

*1 OG/Twitter depth issue(s) detected*

- **[INFO]** 1 Twitter Card field(s) differ from Open Graph counterparts — Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches:
  - description: twitter="Perry Homes has been a Texas tradition f...", og="Discover new homes and custom designs by..."

Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.

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

*6 issues found across 19 images*

- **[WARNING]** 5 images significantly larger than display size — Resizing to display dimensions could save approximately 27 KB.
- **[WARNING]** 8 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 2 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** 1 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[WARNING]** 3 above-fold image(s) marked loading="lazy" (LCP anti-pattern) — Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_71/Britton_Logo_tm7kv3?_a=BAVAfVDW0, https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_71/Mastercraft_Logo_2025_White_Small_cbegmk?_a=BAVAfVDW0, https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_106/PerryHomesLogo_xvr0cp?_a=BAVAfVDW0.
- **[INFO]** 2 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_106/PerryHomesLogo_xvr0cp?_a=BAVAfVDW0, https://res.cloudinary.com/perryhomes/image/upload/c_limit,w_828/f_auto/q_auto/PH.com4_Hero_Perry_1512x650_lf0ty3?_a=BAVAfVDW0.

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*2 A records, 66 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[INFO]** No IPv6 (AAAA) records
- **[PASS]** 4 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 66 ms

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

*No subdomain takeover risk detected*

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

### 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 (B — 75/100)

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 15.197.167.90 does not match any cert SAN: afa7f374f51cc8991.awsglobalaccelerator.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 3.33.186.135 does not match any cert SAN: afa7f374f51cc8991.awsglobalaccelerator.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

### Multi-Resolver DNS Speed (A — 90/100)

*Mean 52ms across 3 resolvers (spread 47ms)*

- **[PASS]** Google: 36ms
- **[PASS]** Cloudflare: 37ms
- **[PASS]** Quad9: 83ms

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

*No redirects — direct access*

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

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

*No IPv6 support*

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

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

*robots.txt present, sitemap with 8354 URLs*

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

### URL Variants (B — 75/100)

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

- **[CRITICAL]** Both www and non-www versions serve content
- **[PASS]** HTTP correctly 301-redirects to HTTPS

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

*perryhomes.com — via Network Solutions, LLC, 30 years, 5 months old, hosted on AWS*

- **[PASS]** Domain registered until May 10, 2030 (4 years 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: Network Solutions, LLC
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
- **[PASS]** Hosting: AWS

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A — 85/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — A privacy policy page is recommended for transparency and may be legally required.
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[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)

*4 known tracker(s) detected*

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

analytics: Google Analytics 4 | marketing: Reddit Pixel, Meta Pixel | session-replay: Hotjar

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

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

*Lang attribute present*

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

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

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

### Accessibility Statement (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 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: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

### Third-Party Trackers (F — 20/100)

*13 trackers detected*

- **[INFO]** 13 third-party trackers detected — Found 8 analytics, 2 advertising, 1 marketing, 1 tag manager, 1 session-replay, 0 heatmap trackers.
- **[WARNING]** 2 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
- **[WARNING]** 1 session-replay tool(s) detected (Hotjar) — Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 13 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

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

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

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

### Tracking Pixel Inventory (B — 90/100)

*1 tracking pixel(s) on the page*

- **[INFO]** 1 tracking pixel(s) on the page (1 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: insight.adsrvr.org.

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

*No browser-fingerprinting libraries detected*

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

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No cookies on the page*

- **[PASS]** No cookies set on the page response

### 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 (F — 30/100)

*1 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[PASS]** Terms of Service detected — Found at /legal, 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 (C — 60/100)

*© 2001-2024 Perry Homes*

- **[INFO]** Copyright year is 2024 (2 year(s) behind) — Copyright year is 2024 — 2 year(s) behind. While copyright protection doesn't depend on the year being current, an outdated notice may suggest the site is not actively maintained. Update to © 2026 or use a range like © 2024–2026.
- **[PASS]** Copyright holder: Perry Homes

### Regulatory Indicators

*0 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]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### 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 5 categories — 5 third-party services detected across 5 categories: Analytics (1), Tag Management (1), Advertising (1), Session Recording (1), Marketing (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]** Hotjar (Session Recording) — Detected via script URL. Typically collects: Session recordings, Heatmaps, Click patterns, Form interactions. Privacy policy: https://www.hotjar.com/privacy/. Data Processing Agreement available.
- **[INFO]** HubSpot (Marketing) — Detected via script URL. Typically collects: Lead tracking, Form submissions, Page views, Email tracking. Privacy policy: https://legal.hubspot.com/privacy-policy. Data Processing Agreement available.

### Compliance Badges (B — 70/100)

*1 compliance badge(s) detected*

- **[PASS]** TRUSTe / TrustArc badge detected — Found via body text: 'truste'. Note: the presence of a badge does not verify the certification is current or valid.

---

## Availability

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

*Netlify*

- **[PASS]** Site is served via Netlify CDN

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

*public,max-age=0,must-revalidate*

- **[PASS]** Cache-Control header is set
- **[PASS]** ETag present — enables conditional (304) responses

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (A — 90/100)

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

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[PASS]** HSTS enabled (base policy)
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

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

*Cache state: Age=880s*

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

---

## Accessibility

### Landmark Structure (A — 90/100)

*8 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 4 <nav> landmark(s) found
- **[WARNING]** 1 of 4 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[PASS]** Skip navigation link present

### Heading Hierarchy (C — 60/100)

*12 headings, 2 skip(s)*

- **[WARNING]** Multiple H1 headings (2 found) — A page should have only one H1. Multiple H1s dilute the document outline.
- **[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: H2 → H6 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

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

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

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

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

*2 of 19 images have issues*

- **[WARNING]** 1 image(s) with filename as alt text
- **[WARNING]** 1 image(s) with generic alt text
- **[PASS]** 1 decorative image(s) correctly marked
- **[PASS]** 16 image(s) with good alt text

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

*No form controls*

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

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

*5 issue(s) across 109 links and 41 buttons*

- **[WARNING]** 5 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 6 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 98 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 (A+ — 100/100)

*51 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

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

*2/4 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="javascript:false") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://perryhomes.my.site.com/ESWChatBotMessageforwe1744836953484/assets/htdoc…") — 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 (D — 60/100)

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

- **[WARNING]** 125 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 7.6px ("Skip to main content"); <a> 10.7px ("Spring Savings Event - Limited Time Ince..."); <span> 7.8px ("Search Now"); <strong> 8.3px ("Since 1967, Perry Homes has built luxury..."); <p> 8.3px ("All Perry homes include smart home techn...").

---

## UX

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

*HTTP 404, bare page*

- **[PASS]** Correct 404 status code returned
- **[WARNING]** Bare server default 404 page — The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

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

*1 icon(s) detected*

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

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

*Not found*

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

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

*No PWA depth issues detected*

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

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

*No dark mode signals*

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

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

*No print styles*

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

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

*1 navigation pattern(s)*

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

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

### Canonical URL (B — 75/100)

*Minor issues*

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

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (58 chars) is optimal
- **[INFO]** Meta description is 210 characters — truncated on mobile (~160 char limit)
- **[PASS]** Title and H1 are well-aligned

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

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

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

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

*2555 words, Fairly Difficult*

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

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

*100 internal, 9 external*

- **[PASS]** 100 internal links (92%)
- **[PASS]** 95% of links use descriptive anchor text
- **[INFO]** 100 internal / 9 external links

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

*19 images, 19 descriptive filenames*

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

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

### 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 (8354/8354 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: 2 days ago

### 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 (8354 URLs, 1.8 MB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*0.81g CO2 per view*

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

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

*Green (cdn)*

- **[PASS]** Netlify CDN uses renewable energy — Since most traffic is served through the CDN, the majority of data transfer energy is renewable.
- **[INFO]** Netlify: Hosted on AWS/Google Cloud with renewable energy matching
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*99% cached*

- **[PASS]** 99% reduction on repeat visits — Returning visitors download only 44 KB (vs 3491 KB first visit). 137 of 143 resources are served from browser cache, saving 0.80g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.81g)

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

*55th percentile*

- **[WARNING]** 0.81g CO2 — above the median website (0.60g) — Heavier than an estimated 45% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 55th 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 442 KB (13%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 442 KB of unused JavaScript. This wasted data produces 0.10g 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/e405fc7f-f46e-4b44-b6c3-023eb8fc5277*