Nonprofits collect 37% of their online revenue in December, so the site that carries that traffic has to be fixed in Q3, not November. With about 17 weeks until GivingTuesday on December 1, start now on page speed, donation-form friction, and mobile checkout.
The short version
- December brings 37% of annual online revenue and the final week alone brings 10%, per the 2026 M+R Benchmarks. A donation flow that breaks in December costs more than in any other month.
- GivingTuesday 2026 falls on December 1. From early August that is roughly 17 weeks, and developer bandwidth vanishes by November, so scope the work now.
- The three highest-return fixes, in order, are page speed, donation-form friction, and mobile checkout.
- Accessibility failures on a donation form are both a conversion leak and legal exposure. Hold the site to WCAG 2.2 Level AA.
- Freeze changes to donation pages the week before GivingTuesday. Late November is not the time to ship.
December is not a month, it's a fiscal cliff
The end of the year is not a busy season, it is the season. The 2026 M+R Benchmarks, which pool data from hundreds of nonprofits, found that organizations received 37% of all online revenue in December, that the final week of the year drove 10% of annual revenue, and that the single last day drove 4%. Layer GivingTuesday on top of that: donors in the United States gave $4.0 billion on GivingTuesday 2025, up 13% year over year, across 38.1 million participants, according to the GivingTuesday Data Commons.
Here is the uncomfortable part. That revenue arrives on the same donation page you built for a quiet Tuesday in March. The traffic is seasonal, the infrastructure is not. If the page is slow, the form is long, or the mobile experience fights the donor's thumb, the cost of those flaws is multiplied by the highest-traffic month you will see all year.
Why Q3 is the real deadline, not November
The work has to be scoped in Q3 because the calendar collapses fast. GivingTuesday 2026 is December 1. Counting from early August, that is about 17 weeks, and the last two of those weeks are unusable: no responsible developer ships changes to a live donation page during the giving surge. Realistically you have a Q3 build window and an October test window, then a freeze.
When I ran a year-end readiness pass for a legal-services nonprofit last summer, the fixes themselves took two weeks. Getting sign-off from the executive director, the payment processor, and the volunteer who owned the content management system took six. That coordination tax is why "we'll handle the site in November" is how organizations end up handling nothing. Agencies book up, board reporting season eats calendars, and the people who can approve a change go on holiday. This is the kind of nonprofit website work that is cheap in July and close to impossible in December, and Q3 is when the people who can approve it are still reachable.
Fix one: page speed, because a slow donation page leaks the gift
Speed is the fix with the widest reach because it touches every donor before they read a word. Google measures user experience with Core Web Vitals (CWV), three metrics with published "good" thresholds: Largest Contentful Paint (LCP) at or under 2.5 seconds, Interaction to Next Paint (INP) at or under 200 milliseconds, and Cumulative Layout Shift (CLS) at or under 0.1. INP replaced First Input Delay as a Core Web Vital in March 2024, and it punishes exactly the sluggish, script-heavy donation embeds that many nonprofits run.
Test the donation page itself, not the homepage. On more than one nonprofit site I have audited, the homepage passed Core Web Vitals while the donation page, weighed down by a third-party form widget and a carousel nobody asked for, failed all three metrics on mobile. The donor never sees a fast homepage on GivingTuesday. They land on the donation URL from an email or an ad, and that is the page that has to be quick.
Fix two: cut the donation form to the bone
Every field you remove is a donor you keep. The pattern I see most often is a form that asks for title, full address, phone number, and employer before it asks for the gift, none of which the organization needs to process a card. Ask for the amount, the card, and the email. Make everything else optional or collect it after the transaction clears. Offer guest giving and never force account creation before a first gift. Turn on the digital wallets, Apple Pay and Google Pay, so a returning donor can give with a fingerprint instead of a keyboard.
Fix three: the mobile give has to work with one thumb
Assume the gift happens on a phone, because increasingly it does. That means tap targets large enough to hit without zooming, inputs that trigger the correct keyboard, browser autofill that actually populates, and wallet buttons placed above the fold. Open your own donation page on your phone tonight and try to give five dollars in under thirty seconds. If you cannot, neither can the donor you spent ad budget to bring there.
Don't let accessibility be the silent conversion killer
An inaccessible donation form quietly turns away donors and invites legal risk at the same time. The Web Content Accessibility Guidelines (WCAG) 2.2, published by the World Wide Web Consortium, define Level AA as the practical standard: text contrast of at least 4.5:1 under Success Criterion 1.4.3, every input tied to a visible label, full keyboard operability, and errors identified in text rather than color alone. A donor using a screen reader or giving one-handed on a bus is still a donor. In the United States, courts have repeatedly treated the Americans with Disabilities Act (ADA) as applying to websites, and donation forms are exactly the transactional pages that draw demand letters. Fixing contrast and labels protects revenue and reduces exposure in the same afternoon.
Instrument it now, so December tells you something
You cannot improve what you did not measure before the surge. Set up conversion tracking in Google Analytics 4 (GA4) now, while traffic is low and you can verify it works. At minimum, mark the completed donation as a key event and build a simple funnel from donation-page view to gift completed, so that in January you can see where donors dropped instead of guessing. Standing this up in December, mid-surge, means you learn nothing from your biggest week. Standing it up in Q3 means December becomes data.
What this does not cover
This is a website readiness piece, so it deliberately leaves out the rest of the year-end program. It does not cover email and paid-media strategy, the appeals calendar, or major-gift and offline fundraising, all of which matter and none of which live on the donation page. It also does not cover donation-page copy and messaging, which deserve their own treatment. And it specifically argues against one thing some teams attempt in Q3: a full platform migration. Replatforming a nonprofit site is worth doing, but not in the ninety days before your biggest revenue event. If a replatform is on your roadmap, run it in Q1, use a proper replatform checklist, and spend this window hardening what you already have.
Frequently asked questions
When should a nonprofit start year-end website prep?
By the end of Q3. Counting from early August, GivingTuesday on December 1 is roughly 17 weeks out, and the final two weeks are a change freeze. That leaves a realistic build-and-test window of about three months, which disappears quickly once approvals and testing are factored in.
What is the single highest-return donation page fix?
Page speed, because it affects every donor before they read anything. Test the donation page against Core Web Vitals on mobile specifically, since most gifts arrive on a phone from an email or ad, not from a fast homepage.
Should we redesign our donation page before December?
No. A redesign introduces risk right before your highest-traffic month. Make targeted fixes to speed, form length, mobile, and accessibility on the page you have. Save the redesign for Q1, when a mistake costs you a slow Tuesday, not a year-end gift.
Is a slow website really costing us donations?
Yes, and the cost is concentrated. With 37% of online revenue landing in December per the 2026 M+R Benchmarks, any friction on the donation flow is multiplied by your heaviest traffic of the year. Slow pages lose donors before the form even loads.
Do we need to freeze website changes during GivingTuesday?
Yes. Stop shipping changes to donation pages the week before GivingTuesday and hold that freeze through year-end. The downside of a bug during the surge is far larger than the upside of a last-minute tweak.
If you want a second set of eyes before the freeze, I will run a Q3 readiness audit on your donation flow covering speed, forms, mobile, and accessibility, and hand you a prioritized fix list. Book a 20-minute read-out and we will start with the page that carries your December.