Point 1 of 9 · The review
Top 5 opportunities for the first 30 days
The five I'd investigate or improve first. Each with the competency it shows, how I'd validate it, and my confidence before seeing live data.
1. Build out good reporting & monitoring (ship first)
- Why first: you can't optimize what you can't see. This is the foundation everything else reads from.
- Build: funnel reporting end to end (key events, qualified app starts, step-by-step drop-off), plus uptime and site-health monitoring with alerts.
- Competency: analytics, reporting, monitoring.
- Validate: reporting reconciles with the app's actual starts; alerts fire when something breaks.
- Confidence: high. Foundational.
2. Eligibility clarity + insurance pre-check (the "qualified" lever)
- Problem: qualification is discovered late: unqualified visitors burn 10 minutes and bounce; qualified ones leave unsure "is this for me, is my plan covered?"
- Do: a scannable "Is Talkiatry right for you" block near CTAs (states, plans + Medicaid exclusion, in/out-of-scope conditions, age 5+, virtual-only).
- Competency: eligibility clarity, page experience, CTA strategy.
- Validate: A/B the block; watch qualified-start rate + downstream booking/show, not raw starts.
- Confidence: high. The most direct line to "qualified" starts.
3. CTA message-match + trust at the decision point
- Problem: some CTAs promise a different action than the real next step ("Book a visit" → a 10-minute questionnaire). Mismatch breeds distrust; proof sits too low on the page.
- Do: make each CTA set up the real next step; test a coverage-led CTA ("Check your coverage and get matched"); move proof adjacent to CTAs; treat variants as a measured system, not drift.
- Competency: CTA strategy, trust signals, messaging, page experience.
- Validate: CTA click-through + start rate by variant; heatmap on proof placement.
- Confidence: medium-high. Placement reliably matters; the winner is empirical.
4. Mobile UX + Core Web Vitals
- Problem: mobile is where this audience lives, with measurable headroom: Lighthouse performance 79 mobile vs 90 desktop; accessibility 88.
- Do: confirm CrUX field CWV; fix LCP (hero media, fonts) + layout shift; keep one persistent mobile CTA; fix systemic contrast at the design-token level (propagates across hundreds of pages).
- Competency: site speed, mobile UX, accessibility.
- Validate: CWV pass rates, mobile start rate, mobile bounce.
- Confidence: medium. Real but moderate headroom; field CWV sets the urgency.
5. Navigation & discovery: the "Resources" mega-menu
- Hypothesis: ~40 links built for SEO, not for a patient deciding to start care; it may add top-of-funnel load. To test, not assert.
- Do: measure menu engagement vs. start-rate; test leaner nav + a resources hub/footer that preserves internal links and crawlability. Reconcile UX and SEO, don't trade one for the other.
- Competency: IA, UX, technical-SEO judgment.
- Validate: start-rate for menu-openers vs. not; Search Console + crawl confirm no indexation regression.
- Confidence: medium. Test-first and low-risk (never sacrifice the SEO).