Westmont of Escondido

• [Verified] The live homepage DOM exposed a lower-page “Schedule a tour” link to westmont-at-san-miguel-ranch/schedule-a-tour/, a Chula Vista community, from the Westmont of Escondido page.
• [Verified] On the August 7, 2026 validation pass, the community's Google Business Profile website link in the local pack pointed to the legacy URL westmontliving.com/ca/escondido/westmont-town-court/index.aspx rather than the current community page.

Impact. A high-intent Escondido family can be routed into another community's booking path. Even if the CRM later corrects the record, the experience creates confusion, attribution pollution, and a plausible lost lead.

What we'd do: Correct the route immediately, search the entire Escondido page family for foreign-community URLs, and add an automated community-route QA check before future releases. Fix the Google Business Profile link and confirm the legacy path redirects.

• [Verified] Multiple homepage images and ImageObject descriptions identify “Westmont of La Mesa,” including service, amenity, shopping, dining, recreation, and decorative assets.

Impact. The mistakes dilute Escondido's local relevance, create poor screen-reader experiences, make structured data less trustworthy, and signal a centrally cloned page to prospects who notice.

What we'd do: Replace every foreign location reference with accurate Escondido-specific descriptions, use actual community photography where possible, and validate JSON-LD and alt text together.

• [Verified] The homepage Service JSON-LD emits aggregateRating as an empty object while review objects are present.

Impact. Invalid or incomplete review markup can be ignored by search engines and reduces confidence in the site's entity data.

What we'd do: Remove the empty property or populate it only from a review source that satisfies Google's structured-data policies. Validate all schema with Google's Rich Results Test and Schema.org validator.

• [Verified] No <main> landmark was present. Headings begin with multiple H2 and H3 elements before the H1, service names jump to H5, roughly 30 links had no accessible text in the parent DOM, and two community-search inputs reused the same ID and had no label. The strict automated parse counted 28 unnamed links, with up to 38 depending on what counts as accessible text.

Impact. Keyboard and assistive-technology navigation is harder than it should be. An accessibility widget does not repair source order, labeling, or semantic problems.

What we'd do: Repair the underlying markup, add one main landmark, normalize heading order, label the search control, eliminate duplicate IDs, and give icon-only links accurate accessible names.

Reference: WCAG 1.3.1, 2.4.1, 2.4.6, and 4.1.2

• [Verified] The schedule-a-tour page embeds api.leadconnectorhq.com/widget/booking/ZSl0vi06x2nowlM7IEp5. The parent page exposes no native form, no H1, and no form fallback or consent language around the embed. Only the sitewide header and footer phone number remains as a fallback.

Impact. If the embed is blocked, slow, inaccessible, or misconfigured, the primary web conversion disappears. Cross-origin form performance and accessibility are also harder to govern.

What we'd do: Keep GoHighLevel if it is operationally useful, but add a visible phone fallback, a concise privacy statement, a stable semantic page heading, and monitoring that verifies the iframe loads and books against the Escondido calendar.

• [Verified] The homepage loads two GTM containers, GTM-5DS2WB33 and GTM-KL24NLH4, GA4 ID G-JJG3M4JQJ4 injected via GTM at runtime, 21 distinct Google Ads AW conversion IDs sitewide with per-community conversion labels, three of which fire on the Escondido page, Google's website call-conversion script, Pearl Diver, and GoHighLevel or LeadConnector resources.

Impact. The stack can support strong attribution, but duplicated containers and multiple ad destinations increase the risk of duplicate events, portfolio-level blending, and disagreement over which community receives credit.

What we'd do: Produce an Escondido measurement map covering event name, trigger, destination, CRM field, call source, community ID, owner, and reporting view. Verify one tour form, one phone call, and one pricing-tool completion end to end.

• [Verified] A live curl sample returned a 754,654-byte HTML document with a 0.207-second TTFB. The rendered page exposed 46 images, 37 lazy-loaded images, numerous Elementor and ElementsKit scripts, two virtual-tour iframes, and multiple trackers.

Impact. Server response was healthy, but the HTML and script surface create avoidable parse, main-thread, and mobile data costs.

What we'd do: Remove duplicated modules and hidden template content, reduce plugin payload, defer nonessential widgets, and set a homepage performance budget. Re-test with field data before claiming a speed gain.

• [Verified] At a 390×844 emulated viewport, the page did not horizontally overflow, but the top booking link, phone link, Resident Login, hero tour call to action, virtual-tour link, and several icon controls rendered below 44px in at least one dimension.

Impact. Older adults and family members using mobile devices may have difficulty tapping accurately.

What we'd do: Increase padding around high-value actions and icon controls without changing visual scale. Retain the no-overflow behavior.

• [Verified] The title, description, address, and local schema are strong, but much of the body copy is generic portfolio language. Foreign-community assets further weaken the page's local identity.
• [Verified] The live Ahrefs pull on August 7, 2026 confirmed that the Escondido section receives roughly 82 organic visits per month from 7 keywords, all branded, with zero non-branded local capture.

Impact. The site can rank for the brand while failing to become the best answer for Escondido-specific assisted living, independent living, memory care, cost, neighborhood, hospital-transition, and family-decision queries.

What we'd do: Build a small, high-intent Escondido content cluster backed by actual community details, staff expertise, local travel times, events, pricing context, and original photos, not city-name substitutions.

• [Verified] The homepage displays several testimonials, while A Place for Mom lists 72 reviews and Birdeye aggregates 107 reviews at 4.6 stars, re-validated August 7, 2026.

Impact. Strong reputation exists, but the page does not clearly connect testimonials to a source, date, or review platform.

What we'd do: Feature recent, permissioned reviews with source and date, link to the primary review profile, and maintain a response and review-request cadence.

• [Verified] Two search_cities inputs use the same ID and rely on placeholder text rather than labels.

Impact. The duplicated controls do not have unique IDs or persistent labels.

What we'd do: Render one control per active layout or generate unique IDs and persistent labels.

• [Verified] Repeated cards, duplicated amenity modules, assessments, virtual tours, resident tools, popups, and the help widget compete with the two primary prospect actions: call and schedule.

Impact. The repeated modules and tools compete with the primary call and scheduling actions.

What we'd do: Preserve useful tools but simplify the prospect hierarchy: care fit → pricing and floor plans → tour or call.