- Compliance & Governance
Website Performance Monitoring for Nonprofits: What to Measure and How Often
Key takeaways
- Having Google Analytics installed is not monitoring; meaningful monitoring requires the right data being collected, regular review of it, and a process for acting on what you find.
- Track the metrics tied to actual goals: mark donations, form submissions, sign-ups and event registrations as key events in GA4 rather than just counting pageviews.
- Combine GA4 with Google Search Console for organic search performance, and watch traffic sources, engagement metrics, and the instructive gap between high-traffic pages and high-converting pages.
- Adopt a sustainable cadence: a short monthly review that produces at least one action item, quarterly trend analysis, and an annual strategic review that feeds the content audit.
- Treat monitoring as a governance function, not a technical afterthought. Report performance to senior leadership, give it a named owner, and document findings to build institutional memory.
- Use a free Google Data Studio dashboard to make monthly reviews quick, and set up alert-based monitoring for sudden problems like a page going offline or a form breaking.
Summary
A practical guide to website performance monitoring for nonprofit organisations: which metrics to track, which tools to use, and how to build a sustainable quarterly review cadence.
Why Most Nonprofit Websites Are Under-Monitored
A nonprofit's programme delivery is measured. Fundraising campaigns are evaluated. Staff performance is reviewed. The website, which may be the first point of contact for beneficiaries, funders and donors, is often managed by instinct, updated by feel, and assessed only when someone notices something is wrong.
This guide covers how to set up meaningful website monitoring for a nonprofit: what to track, how often to review it, and how to turn analytics data into decisions rather than just numbers. Performance here means both halves of the word, the audience numbers and the speed and availability of the site those numbers arrive at.
The Problem With “We Have Google Analytics”
Most nonprofit websites have Google Analytics installed. Far fewer have it configured to measure anything meaningful. Having GA4 tracking pageviews isn't monitoring: it's having the potential for monitoring without using it.
Meaningful website monitoring requires three things: the right data being collected, regular review of that data, and a process for acting on what you find. Most organisations have the first at some level, skip the second, and never get to the third.
What to Track: The Metrics That Matter
Not all analytics data is equally useful. For nonprofits, the metrics that matter most are those connected to your actual goals, which I set out at more length in website performance benchmarks for NGOs.
Conversion Events
A conversion is any action on your website that represents a meaningful outcome. For nonprofits, typical conversions include:
- Donation completions (or clicks through to a hosted donation platform)
- Contact form submissions
- Newsletter or mailing list sign-ups
- Volunteer application submissions
- Resource downloads (if relevant to your mission)
- Event registrations
These should be marked as key events in GA4. That is the setting Analytics used to call a conversion: in GA4 today, a conversion means a key event imported into Google Ads, and it does not appear in standard Analytics reports. Until you've done this, your analytics setup is measuring activity (visits, pageviews) but not outcomes.
For how to configure them, see my guide to GTM, GA4 and Consent Mode setup on Webflow.
Organic Search Performance
Google Search Console shows you how your site performs in search: which queries you appear for, your average position, how many people click through, and which pages generate the most search traffic.
This is separate from GA4 and requires its own setup. Connect your Search Console property to GA4 for integrated reporting. It is also the starting point for a technical SEO audit.
Traffic Sources
Where is your website traffic coming from? The primary channels to monitor:
- Organic search: People finding you via Google and other search engines
- Direct: People who type your URL directly or arrive without a tracked referrer
- Referral: People arriving from links on other websites
- Social: Traffic from social media platforms
- Email: Traffic from email campaigns (requires UTM parameter setup)
- Paid: Traffic from any paid advertising
Channel mix matters because different sources have different conversion rates and different implications for your communications strategy.
Engagement Metrics
GA4's engagement metrics (engagement rate, average engagement time, views per session) give a sense of whether people are finding what they're looking for or bouncing immediately. Look at these by page and by traffic source.
Top Pages
Which pages receive the most traffic? Which pages lead most frequently to conversions? These aren't always the same pages, and the gap is instructive. A highly-trafficked page that generates no conversions warrants investigation. Is it serving its purpose, or is something broken?
Page Speed and Core Web Vitals
Analytics tell you what people did. Page speed tells you what they sat through to do it. Google's Core Web Vitals are three metrics: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. The good thresholds are an LCP within 2.5 seconds, an INP of 200 milliseconds or less, and a CLS of 0.1 or less, judged at the 75th percentile of page loads rather than as an average, and segmented across mobile and desktop.
Check the metric names before you reuse an older report or dashboard. Interaction to Next Paint replaced First Input Delay on 12 March 2024, so anything still reporting FID predates the current set.
Two free tools cover this. PageSpeed Insights runs a single URL and shows both a lab test and real-user data where it exists. Search Console's Core Web Vitals report groups your whole site by status, drawing on the Chrome UX Report. That second point is the catch for a small charity: CrUX only covers pages with a minimum number of visitors, so a quiet site will not appear in it at all and the lab test is what you work from.
State the ranking question precisely, because it is routinely overstated. Google says Core Web Vitals “are used by our ranking systems”, and says in the same document that “there is no single signal” and that good results in the Core Web Vitals report do not guarantee a page will rank at the top (Google Search Central, 2026). Treat them as a user-experience measure that also helps in search, not as a lever you pull for position.
Availability is the third part of performance, and it is handled by alerting rather than by review. The setup is below.
How Often to Review: The Monitoring Cadence
Monthly: Core Performance Review
A monthly review should cover:
- Total sessions and unique users (compared to previous month and year-on-year)
- Conversion counts by type
- Top traffic sources
- Organic search performance from Search Console
- Any significant changes: traffic drops, new referrers, page errors in Search Console
- Core Web Vitals status in Search Console, and the month's uptime figure from your monitor
With a properly configured dashboard this review is a short session in my experience, and it should produce at least one action item: a page to investigate, a content gap to address, an error to fix.
Quarterly: Deeper Analysis
Quarterly reviews look at trends rather than snapshots:
- Are conversions increasing, decreasing, or flat over the past quarter?
- Which content is driving the most meaningful traffic?
- Are there pages consistently failing to perform that need attention?
- Are the Core Web Vitals holding, or drifting as pages accumulate images and embeds?
- How does performance compare to the same quarter last year?
Annual: Strategic Review
The annual review connects website performance to organisational strategy:
- Did the website support this year's communications goals?
- Which audiences are you reaching, and which are you missing?
- Are your key pages still serving their purpose, or have strategic priorities shifted?
- What investment does the website need in the coming year?
The annual review feeds directly into the content audit process, and the monthly and quarterly checks sit alongside the wider website maintenance schedule.
Making Monitoring a Governance Function
Website monitoring is often treated as a technical task, something the digital person checks occasionally. For nonprofits, it's more accurately a governance function: the mechanism by which the organisation knows whether its website is fulfilling its institutional purpose.
This reframing has practical implications:
- Reporting: Website performance data should be reported to senior leadership, not just discussed within a communications team. The Communications Director should be able to report website performance to the CEO the same way programme outcomes are reported.
- Accountability: Someone specific should own the monitoring function, not as a casual responsibility but as a named accountability with time allocated for it.
- Documentation: Monitoring findings should be documented, not just noted. A log of monthly reviews creates institutional memory and makes it easier to identify trends over time.
For integrating monitoring into your broader website governance framework, see my guide to website governance policies for nonprofits.
Setting Up a Monitoring Dashboard
Manually navigating GA4 every month is time-consuming and inconsistent. A custom dashboard connected to your GA4 property lets you see your key metrics at a glance without navigating multiple reports. Google's own tool for this is free and is called Data Studio: it went by the name Looker Studio until April 2026, so guides and menus you meet may use either name.
A basic nonprofit monitoring dashboard should show:
- Session and user trends (month-on-month comparison)
- Conversion counts by event type
- Top pages by sessions
- Traffic source breakdown
- Search Console data (if connected)
Building this takes a few hours initially but saves significant time in each subsequent monthly review.
When Something Goes Wrong: Alert-Based Monitoring
Scheduled reviews catch trends. They don't catch sudden problems. For issues that need immediate attention (a page going offline, a form stopping working, a traffic drop that suggests a technical problem), you need alert-based monitoring.
GA4 lets you create custom insights: conditions that detect changes in your data, with an optional email alert when one triggers. Search Console alerts you when Google encounters indexing, spam or other issues on your site. Uptime monitoring tools can notify you immediately if your site goes offline, and UptimeRobot's free tier covers 50 monitors on a five-minute check interval.
For nonprofits, the minimum alert setup is Search Console notifications enabled, and an uptime monitor watching your site and your most important forms.
Connecting Monitoring to Action
The purpose of monitoring isn't to produce reports. It's to inform decisions. The test of a good monitoring process is whether findings lead to changes: to content, to site structure, to budget, to priorities.
If your monthly review produces data but no actions, either the data isn't actionable or the governance structure to act on it isn't in place. Both are fixable, but they require different interventions.
For technical foundations including analytics setup, see my GTM setup guide. For the content side of what monitoring should feed into, see the content audit guide and the pre-launch checklist for how monitoring should be established before a site goes live.
If you'd like help establishing a monitoring framework as part of a broader site governance review, the Blueprint Audit includes assessment of your current analytics configuration and recommendations for a sustainable monitoring approach.
Two clicks. Three things.
Send the address of your website. Within two working days you get a short email naming the three things a funder would hold against it, including what AI assistants like ChatGPT and Google’s AI Overviews currently say about you. No report, no call, no follow-up unless you ask.
Received. Your three things arrive within two working days.
That did not send. Email hello@socialectric.com with your website address and I will reply from there.
Frequently asked questions
- We already have Google Analytics. Isn't that monitoring?
Not on its own. Having GA4 tracking pageviews is the potential for monitoring rather than monitoring itself. Meaningful monitoring requires three things: the right data being collected, regular review of that data, and a process for acting on what you find. Most organisations have the first at some level, skip the second, and never get to the third.
- What should a nonprofit actually measure?
Start with the outcomes that matter (donation completions or clicks through to a hosted donation platform, contact form submissions, newsletter sign-ups, volunteer applications, resource downloads and event registrations), marked as key events in GA4, which is what Analytics used to call marking a conversion. Until that is done you are measuring activity rather than outcomes, and my GTM, GA4 and Consent Mode setup guide covers the configuration. Add organic search performance from Google Search Console, which needs its own setup and can be connected to GA4; traffic sources across organic, direct, referral, social, email and paid; GA4's engagement metrics by page and by source; and your top pages. Pay particular attention to the gap between the pages that get the most traffic and the pages that lead to conversions, because a highly-trafficked page generating no conversions warrants investigation. Then add the speed side, which is the other half of what performance means. Google's three Core Web Vitals are Largest Contentful Paint (good within 2.5 seconds), Interaction to Next Paint (200 milliseconds or less) and Cumulative Layout Shift (0.1 or less), each judged at the 75th percentile of page loads (web.dev). PageSpeed Insights tests a single URL for free and Search Console reports the site as a whole, although its data comes from the Chrome UX Report and a low-traffic charity site may not appear there at all.
- How often should we review website performance?
On three cadences, each answering a different question. The monthly review covers sessions and users against the previous month and year on year, conversion counts by type, top traffic sources, Search Console performance and any significant changes such as traffic drops or page errors; with a properly configured dashboard it is a short session in my experience and should produce at least one action item. Quarterly reviews look at trends rather than snapshots, and the annual review connects website performance to organisational strategy, meaning which audiences you are reaching and missing, and what investment the site needs in the coming year. The analytics cadence sits inside the wider website maintenance schedule.
- How do we catch a sudden problem between reviews?
Scheduled reviews catch trends, not sudden failures, so you also need alert-based monitoring. GA4 lets you create custom insights, which are conditions that detect changes in your data and can email you when they trigger, and Google Search Console alerts you when Google encounters indexing, spam or other issues on your site. The minimum setup for a nonprofit is Search Console notifications enabled plus an uptime monitoring tool (UptimeRobot's free tier covers 50 monitors on a five-minute check) watching your site and your most important forms.
- Is there a way to avoid navigating GA4 every month?
Build a dashboard. Manually navigating GA4 each month is time-consuming and inconsistent, whereas a custom dashboard in Google's free Data Studio, the tool called Looker Studio until April 2026, connects to your GA4 property and shows your key metrics at a glance. A basic nonprofit dashboard should show session and user trends month on month, conversion counts by event type, top pages by sessions, the traffic source breakdown, and Search Console data if it is connected.
- Who should own website monitoring?
Someone specific, as a named accountability with time allocated for it, rather than a casual responsibility for whoever the digital person happens to be. Monitoring is better understood as a governance function than a technical task: it is the mechanism by which the organisation knows whether its website is fulfilling its institutional purpose. Performance should be reported to senior leadership the way programme outcomes are, and findings should be documented, because a log of reviews creates institutional memory and makes trends easier to identify.