Page Speed For Nonprofit Websites: What moves the Needle
Page speed affects both SEO rankings and donation conversion, but the gains most nonprofits need come from three or four concrete fixes. The rest is noise. This piece walks through what’s worth doing, what isn’t, and when to call for help.
Why this matters now
Google has treated page speed as a ranking signal in some form for over a decade. In 2021 it started weighing Core Web Vitals directly, and mobile performance has only grown in importance since.
For a small nonprofit, the honest version is this. Page speed isn’t the most important thing about your website, but it’s one of the easier things to get wrong. A slow site quietly erodes two things you care about: Google rankings and donation completions. The fixes aren’t technical gymnastics. Most are an afternoon of work, some of which a staff member can do without a developer.
Where speed matters most
Not every page on your site carries the same weight.
The donation page matters most. Google’s mobile speed research pegs the bounce rate increase at roughly 32% going from a 1-second to a 3-second load, and 90% going from 1 to 5. For a nonprofit pulling in donors mostly via email campaigns and social posts, those are mobile-first visits on variable networks. A donation page that takes five or six seconds to load on a phone is losing real revenue.
The homepage matters almost as much. First impression, usually mobile, often on a weak connection.
Program and service pages that pull in search traffic are next. Google rewards faster pages, and ties often break on speed.
Internal staff pages and deep archives matter less. If nobody’s clicking on them, they don’t need to be fast.
Five questions that settle what to do
1. Does page speed actually move the needle on donations?
Yes, and it’s a slope rather than a cliff.
The Google benchmark shows bounce rates rising sharply past three seconds. A donation page that loads in two seconds keeps more of the traffic you paid to get there. A donation page that loads in seven loses a meaningful share of it.
The effect is real. It’s also not the only thing affecting conversion. If your donation page is slow but also has a confusing four-step flow, fix the flow first. Speed amplifies a good experience and compounds a bad one.
2. How do you measure it?
Two free tools cover most of what a nonprofit needs.
PageSpeed Insights gives you a score and a breakdown of Core Web Vitals for mobile and desktop. It’s Google’s own tool using Google’s own criteria, so the numbers correlate with what affects ranking.
GTmetrix gives a second opinion and better visualization of which specific files are slow.
Run both against your homepage and your donation page. If both tools come back green, stop worrying and go work on copy.
If either is yellow or red, focus on the three Core Web Vitals numbers: Largest Contentful Paint (how fast the main thing appears), Interaction to Next Paint (how fast the page responds when a visitor clicks), and Cumulative Layout Shift (how much stuff jumps around while loading). These are what Google is actually measuring.
3. What’s usually making a nonprofit site slow?
Four things, in roughly this order of likelihood.
Oversized images. The single most common issue. A homepage with a 4MB hero photo that should be 200KB. Staff uploading phone photos directly into the media library. Stock images pasted in at full resolution. This alone can turn a fast site into a slow one.
Plugin bloat. WordPress sites accumulate plugins the way garages accumulate boxes. Each one loads scripts, styles, sometimes tracking. A small nonprofit site running 40 plugins is carrying weight it doesn’t need.
Cheap or shared hosting. On the cheapest hosting tier, your site shares a server with hundreds of others. When a neighbor has a traffic spike, your site slows. This matters less than people assume, but it’s real.
Tracking scripts and embeds. Facebook pixel, Google Analytics, HubSpot, a chat widget, three different form providers. Each one adds load time. Most nonprofits run more of these than they need.
Notice what’s not on this list: your theme, in most cases. Unless your theme was custom-built badly or dates from 2015, the theme is rarely the bottleneck.
4. What can you fix without a developer?
More than most staff assume.
- Compress images before uploading. Use TinyPNG or Squoosh. Aim for hero images under 200KB and content images under 100KB. This is the biggest single win for most nonprofit sites.
- Audit your plugins. Deactivate anything you haven’t actively used in six months. If nothing breaks after a week, delete it. Page builders installed for one page and never removed are common culprits.
- Install a caching plugin. If you don’t have one, add WP Rocket (paid) or W3 Total Cache (free). Default settings are usually fine. This alone often moves PageSpeed Insights scores 15 to 25 points.
- Remove tracking scripts you don’t use. Check your analytics. If a pixel hasn’t fired in six months, it’s weighing the site down for no reason.
- Limit custom fonts. Every font family and weight adds load. Two weights of one font is plenty for most sites.
None of these need code. A marketing manager can do them in an afternoon, assuming someone with admin access is available.
5. When should you bring in technical help?
If you’ve done the above and the site is still slow, the remaining issues usually fall into three buckets.
Hosting. Moving from shared hosting to managed WordPress hosting (Kinsta, WP Engine, Pressable) often produces a clear speed jump. Expect $30 to $100 per month instead of $5 to $20. For most nonprofits with real traffic, this is worth it.
Theme or page builder bloat. Some themes, particularly older “mega” themes, load huge amounts of code regardless of what’s on the page. Replacing a bloated theme is real work and needs a developer.
Database or code-level issues. Sites that have run for many years accumulate database cruft, orphaned settings, and unused tables. This usually shows up as slow “Time to First Byte.” A developer can clean it in a day or two.
At that point you’re looking at real engagement, not an afternoon of cleanup. Most nonprofits cross this line only once every several years.
Investments ranked by effort and impact
| Fix | Effort | Impact | Who does it |
|---|---|---|---|
| Image compression | Low | High | Staff |
| Plugin audit | Low | Medium | Staff |
| Caching plugin | Low | High | Staff |
| Remove unused trackers | Low | Low to medium | Staff |
| Trim custom fonts | Low | Low | Staff |
| Hosting upgrade | Medium | Medium to high | Staff with guidance |
| Theme replacement | High | High | Developer |
| Database cleanup | Medium | Medium | Developer |
Where this leaves you
Most nonprofit sites are slow for ordinary reasons. Usually big images. Sometimes plugin bloat. Occasionally old tracking scripts nobody removed. Fixing those is cheap and fast and usually enough.
If your homepage loads in under three seconds on mobile, your donation page in under two, and your Core Web Vitals come back green, you’re doing better than most nonprofits. If you’re nowhere near that, the list above is where to start before anyone begins talking about redesigns or rebuilds.
The question worth asking: when was the last time someone on your team ran your site through PageSpeed Insights? If the answer is “never” or “more than a year ago,” that’s the first thing to do this week.
Not sure where your site stands? Start a conversation.