Two in Three Nonprofit Websites Fail Google's Core Web Vitals Test

Only a third of nonprofit websites pass Google's Core Web Vitals on mobile. Across 11,221 organizations running real donation software, just 33.4% clear the bar, one of the lower figures of any sector we have measured. These sites are responsive and visually stable. What they are not is fast to load, and for an organization that raises money on the page, loading is the part that matters most.

The stakes here are literal revenue. The median nonprofit site takes 2.5 seconds to paint its main content, sitting right on the line where visitors start to leave, and the slow page is the donate page. Research on load time is unambiguous that every extra second costs conversions, and for a nonprofit a conversion is a completed gift. A donation page that appears in one second instead of three keeps donors who would otherwise drop off, and a slow page also ranks lower in search, since Google treats speed as a ranking signal for the grant-seeking and campaign traffic these organizations depend on.

These numbers come from Google's Chrome User Experience Report, the real-user field data collected from the Chrome browsers of actual visitors, the same signals Google's ranking systems use. We measured every nonprofit Google has that data for that also runs dedicated fundraising software, so this reflects the organizations that actually raise money online rather than a curated shortlist.

The population is 11,221 nonprofit origins that our technology data identifies as running dedicated donation or fundraising software (GiveWP, Donorbox, Kindful, DonorPerfect, Classy, Bloomerang), measured on mobile at the 75th percentile against Google's Core Web Vitals thresholds. This captures organizations that fundraise online and skews toward WordPress, where most donation plugins live. Passing means clearing all three metrics at once: good loading (Largest Contentful Paint under 2.5 seconds), good responsiveness (Interaction to Next Paint under 200 milliseconds), and good visual stability (Cumulative Layout Shift under 0.1), for the three-quarters of real visitors who define the typical experience.

Break the pass rate into its three parts and the sector is strong on two of them. Good INP runs 94.3% and good CLS 89.8%, both healthy, because a nonprofit site is content-first: a mission, a story, some photos, and a donate button, without the heavy client-side application code that hurts responsiveness elsewhere. Visitors who reach these pages find them stable and quick to react.

The entire gap is loading. Only 50.5% of nonprofit sites have good LCP, and because a site has to clear all three metrics to pass, that one number is the whole reason the sector passes just a third of the time. The median site paints in 2.5 seconds, right at the 2.5-second pass/fail line, the slowest median of the sectors we have measured. More than a quarter of these origins, 28.4%, have too little traffic to report a responsiveness score, a sign of how many small organizations run lightly-trafficked sites where nobody owns performance.

The loading weakness is not a mystery once you see what these sites are built on. The most common donation platform in the data by a wide margin is a WordPress plugin, which means most of these nonprofit sites are WordPress sites. Our WordPress study found the same shape: strong responsiveness and stability, weak loading, driven by heavy themes, stacked plugins, and unoptimized images.

Nonprofits inherit that profile and then add fundraising widgets and campaign imagery on top of it. The result is a donate page that works and holds still but takes too long to appear. Because the weakness is structural rather than accidental, it responds to the same structural fixes, and those fixes pay for themselves in gifts that would otherwise be lost to the wait.

Responsive and stable, held back entirely by loading.

For a nonprofit this is a narrow, revenue-shaped diagnosis. Responsiveness is already strong at 94.3% good INP and stability at 89.8% good CLS, so neither is why only 33.4% of these sites pass. The whole gap is loading: 50.5% good LCP and a 2.5-second median that sits right on the 2.5-second pass/fail line, the slowest of any sector we have measured. The page that loads too slowly is the donate page, where the money comes in.

Because most of these sites are WordPress with a donation plugin, they inherit WordPress's loading weakness, so the same fixes apply. Compress and correctly size the campaign images so the largest paint is not a hero photo, move to faster hosting with caching, and trim the theme and plugin weight to what the mission actually needs. A donate page that appears in one second instead of two and a half keeps donors who would otherwise leave before the gift clears.

One number frames the stakes: 28.4% of these origins draw too little traffic to even report a responsiveness score, which usually means nobody owns performance. For an organization that small, one focused afternoon on loading is likely the cheapest fundraising gain it has available.