Six findings across five phases. Two are Critical — address these first. Three are Structural — medium-term investments that compound over time. One is Optimizing — available after the foundation is stable.
The mission statement describes the organization. It doesn't move anyone to give.
The homepage headline reads: "Clearwater Community Table is a 501(c)(3) nonprofit serving food-insecure families across three counties." This is an organizational description, not a mission statement. It communicates legal status and geography. It does not communicate urgency, human stakes, or a reason for a first-time visitor to stop scrolling. A prospective donor who arrives from a Google search or social share has no emotional entry point within the first ten seconds.
Inferred: First impressions determine whether the remaining 99.84% of site visitors — those who do not donate in a given session, per M+R Benchmarks — leave with enough trust and motivation to return. A mission statement that fails to create an emotional entry point suppresses both first-visit conversion and return visits. [Confidence: inferred — confirm with traffic and bounce rate data when available.]
Recommended action: Rewrite the homepage headline to lead with the human consequence of the problem, not the organizational description. Example frame: "1 in 6 families in [region] doesn't know where their next meal is coming from. We're changing that — one table at a time." No developer required. Content change only, executable within one week.
Monthly giving is invisible. The donation form offers no path to a recurring relationship.
The donation form defaults to a one-time gift with no monthly giving option above the fold. A "Give Monthly" checkbox appears below three other form fields and is unchecked by default. On mobile — where 43% of nonprofit donations now occur (M+R Benchmarks 2026) — the monthly option is not visible without scrolling. For an organization whose primary pressure is retention, this is the single highest-cost architectural gap on the site. Every completed one-time donation is a missed sustainer conversion.
Inferred: Monthly donors retain at 71% after one year versus 48% for one-time donors (M+R Benchmarks 2026). A donor who gives once to Clearwater Community Table has a 52% probability of not returning next year. A donor who converts to a $25/month sustainer has a 71% probability of still giving twelve months later — and contributes $300 annually versus a median one-time gift. The architectural suppression of this pathway is a compounding retention and lifetime value loss. [Confidence: inferred — confirm with internal retention and sustainer penetration data.]
Recommended action: Restructure the donation form to present monthly and one-time giving as equal options at the top of the form, with monthly giving featured first or defaulted. Test pre-selecting $25/month as the default. This is a form configuration change — most nonprofit donation platforms (Classy, Bloomerang, DonorPerfect) support this without developer work.
Impact is reported in pounds and meals. Donors need to see people, not numbers.
The impact section of the homepage displays: "2.4 million pounds of food distributed. 180,000 meals served." These are credible numbers. They are also abstract. There is no photograph of a family, no named beneficiary story, no quote from a program participant, and no explanation of what 180,000 meals means in human terms for this specific community. The statistics communicate scale but not significance. A prospective donor — or a program officer at a regional foundation considering a grant — cannot connect these numbers to a person they care about.
Recommended action: Add one beneficiary story — 150 words and a photograph — adjacent to the impact statistics. The story should name a specific person (with permission), describe a specific moment, and connect that moment to the donor's gift. "When Maria's husband lost his job in March, she didn't know how she'd feed her three kids. Clearwater Community Table was there every week for four months." This is a content task, not a technical one. It should be prioritized within 30–60 days.
There is no stewardship infrastructure. Donors who give have nowhere to go next.
The post-donation confirmation page displays: "Thank you for your donation." There is no impact statement, no next action, no invitation to share, no information about what the gift will make possible, and no pathway to a deeper relationship. The site has no blog, no news section updated within the past eight months, and no impact report accessible from the navigation. A donor who completed a gift in January 2026 has received no digital stewardship signal since. For an organization with a retention gap as its primary pressure, the absence of stewardship infrastructure is not a content problem — it is a donor relationship problem expressed as a content gap.
Recommended action: Rebuild the donation confirmation page as a stewardship moment. Add: a specific impact statement tied to the gift amount ("Your $50 provides 40 meals"), a short video or photo from the program, one social share prompt, and a soft invite to join the monthly giving program. This is a content and platform configuration task. Pair it with a quarterly impact email to the existing donor list — even a simple one-page update — to begin rebuilding stewardship cadence.
Mobile donation experience is technically functional but conversion-hostile.
The donation page loads in approximately 5.2 seconds on a mobile connection (measured via PageSpeed Insights — Mobile score: 41). The form fields are sized for desktop interaction: tap targets are smaller than the recommended 44px minimum, the credit card field requires manual entry with no Apple Pay or Google Pay option, and the suggested giving amounts ($25, $50, $100, $250) are presented as small radio buttons that require precise tapping. Given that 43% of nonprofit donations occur on mobile, a page with a mobile PageSpeed score of 41 is actively losing completions on the majority of the traffic it receives.
Recommended action: Prioritize mobile donation page performance as a technical project. Immediate actions: enable Apple Pay and Google Pay through the existing donation platform (most support this with a settings toggle), increase tap target sizes, and compress images on the donation page. Longer-term: address Core Web Vitals issues surfaced in PageSpeed Insights. Requires developer support for full resolution but platform-level payment options can be enabled without code changes.
Suggested giving amounts are anchored too low for the organization's donor base.
The donation form presents suggested amounts of $25, $50, $100, and $250. Based on the organization's estimated revenue tier and regional market, a mid-level donor giving $500–$1,000 annually has no anchor on the form and no named giving level to aspire to. The $250 top anchor is likely suppressing average gift for donors who would give more if presented with a higher reference point and a specific impact statement tied to that amount ("$500 feeds a family for a full month"). This is an Optimizing finding — address it after Critical and Structural items are resolved.
Recommended action: Test a revised giving array with amounts of $50, $100, $250, and $500. Add a specific impact statement to each amount. Consider adding a "Other" field with a prompt of "Make it a monthly gift for greater impact." This is a platform configuration change, executable without developer support on most donation platforms.