Donation Page CRO: Design Patterns That Increase Giving

Most nonprofit donation pages are not designed. They are whatever the payment platform produced, embedded in whatever template the site uses, with fields accumulated over years because someone once wanted the data. The result is a page that loses a meaningful share of people who had already decided to give — which is the most expensive kind of loss, because the hard work of persuading them was already done.

This is about the mechanics of that page. Not fundraising strategy, not appeal copy — the specific design decisions between "I want to donate" and a completed transaction.

Design for the phone, because that is where they are

Donation traffic skews heavily mobile, particularly from email and social. Yet donation pages are routinely designed on a desktop and checked on a phone at the end.

Invert that. Design the mobile view first. Check that amount buttons are large enough to hit accurately, that the keyboard that appears for the amount field is numeric, that the form does not require pinch-zooming, and that the submit button is reachable without scrolling past six optional fields.

Cut the form to what you need to process the gift

Every field costs completions. The minimum for most organizations is amount, name, email and payment details. Address is often needed for tax receipting; if so, keep it, but ask whether you need it for a $10 gift.

Everything else — phone number, how they heard about you, employer, title, mailing preferences — should be justified individually or removed. If a field is genuinely useful but not required, ask for it after the transaction, on the thank-you page, where asking costs you nothing.

This overlaps directly with donor data privacy: fields you do not collect are fields you do not have to protect.

Make recurring giving easy to choose and easy to understand

Recurring donors are worth substantially more over time, and the decision is made on this page or not at all. Present monthly as a clear option rather than a checkbox in small type, and state plainly what will happen — the amount, the frequency, and that it can be cancelled.

Ambiguity here suppresses giving. People hesitate to start a recurring commitment they are not sure they can stop, and a single sentence saying they can resolves it.

Choose suggested amounts deliberately

Suggested amounts anchor the decision, and most pages inherit defaults from the platform. Set them based on your actual gift distribution rather than aspiration: if most gifts are $25 to $50, a ladder starting at $100 makes the majority of your donors feel their gift is inadequate.

Always include a clearly usable custom amount field. And where you can, describe what an amount does — "$50 provides a week of meals" — but only if it is true and defensible, because a claim you cannot substantiate is worse than no claim.

Keep them on your domain

Sending a donor from your site to a third-party platform with different branding and a different URL introduces exactly the moment of doubt you cannot afford. People check whether a payment page is legitimate, and a mismatch reads as a warning sign.

Use an embedded or hosted flow that keeps your branding and, where possible, your domain. This also matters for the Google Ad Grant, which expects campaigns to point at your own domain.

Test the whole journey with a keyboard and a screen reader

This is the step almost nobody takes, and it is where donation pages fail hardest. Complete the entire flow using only the keyboard: tab to each field, select an amount, enter card details, submit. Then do it with a screen reader.

What surfaces is usually unlabelled amount buttons announced as "button" with no value, error messages that appear visually but are never announced, and a payment iframe that cannot be reached by keyboard at all. Every one of those excludes donors who want to give you money — see our WCAG 2.2 AA checklist, which applies just as well here.

Handle errors like a human would

Payment errors are inevitable. What matters is what the page does next. The amount and the entered details should survive the error rather than being cleared. The message should say what to fix in plain language, next to the field, rather than "Transaction failed (code 402)" at the top of the page.

And the error must be announced to assistive technology, not just coloured red — a donor using a screen reader otherwise sits on a page that has silently refused them.

Make the page fast

Donation pages are frequently the slowest on a nonprofit site because they load the site template, a payment SDK, analytics, a chat widget and three tracking pixels. Every second costs completions on exactly the page where it is most expensive.

Strip the page to what the transaction needs. A donation page does not need a mega-menu, a carousel or a live chat widget.

Treat the thank-you page as part of the design

The thank-you page is the highest-attention moment you will get, and most organizations waste it on a single line of confirmation.

Confirm clearly what was given and that a receipt is coming. Then ask for exactly one thing: sharing, a monthly upgrade, newsletter signup, or the optional data you removed from the form. One ask, not four. The follow-up email matters as much — it should arrive quickly and read like a person wrote it.

Measure the funnel, not just the total

Track page views, donation starts, submissions and completions separately. Without those steps you cannot tell whether people are not starting or not finishing, and those have opposite fixes.

Watch for the gap between submission and completion in particular — that is usually a payment-error or validation problem, and it is invisible in a report that only counts successful gifts.

A short checklist

Mobile-first layout with tappable amounts and a numeric keypad. Fields cut to the minimum. Recurring presented clearly with a plain cancellation statement. Amount ladder based on real data. Flow kept on your domain. Whole journey tested by keyboard and screen reader. Errors preserved, announced and readable. Page stripped for speed. Thank-you page with exactly one ask. Funnel measured at four steps.

We build donation journeys to this standard as part of nonprofit website design, and the same testing discipline is what an accessibility audit applies to an existing one.