Website Performance Benchmarks for NGOs: What You Should Actually Be Measuring
Key takeaways
- Default analytics metrics like sessions and pageviews describe activity, not whether the website is serving its stakeholders or meeting the compliance obligations the Board is accountable for.
- Core Web Vitals give standardised performance targets — Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200ms, Cumulative Layout Shift under 0.1 — and should be tested on the homepage, a programme page and the donation page.
- Accessibility benchmarks are non-negotiable: WCAG AA compliance, zero critical violations on automated scans, complete keyboard navigation, sufficient colour contrast and full alt-text coverage on meaningful images.
- Content currency is a credibility metric — a stale annual report, out-of-date programme descriptions or an inactive news section lead funders to draw conclusions about governance quality.
- Conversion should be measured against mission actions such as donations, enquiries, sign-ups and document downloads, watching the trend rather than a single number.
- Website performance should be presented to the Board in terms of institutional risk, not traffic numbers.
Summary
Most nonprofits measure the wrong things on their website. They track total sessions and pageviews — the metrics that analytics dashboards present by default — without connecting them to the institutional functions the website is supposed to perform. High traffic on a website that is failing its primary stakeholders — where funders cannot find governance documents, where donors are abandoning the donation flow, where beneficiaries cannot locate the service information they need — is a vanity metric that obscures institutional failure.The performance benchmarks that matter for established nonprofits are the ones that measure whether the website is doing its governance job: whether funders can navigate to the information they need during due diligence, whether the donation flow converts at a rate consistent with sector benchmarks, whether the accessibility metrics indicate ongoing compliance or accumulating failure, and whether the site's performance against search and AI visibility metrics suggests it is building the institutional credibility that drives discovery by the right stakeholders.This post covers the specific benchmarks that digital managers at established nonprofits should track quarterly: the governance content accessibility metrics, the donation flow metrics, the accessibility monitoring metrics that catch compliance drift, the search visibility metrics that track organisational discoverability, and the content currency metrics that indicate whether the maintenance schedule is being followed and the website remains accurate. Each benchmark is explained in governance language with sector reference points where available, and a template reporting framework is provided for quarterly Board-level use.
Google Analytics shows you pageviews. Your hosting dashboard shows uptime. Your agency report shows you a design that looks impressive. None of this tells you whether your website is functioning as institutional infrastructure — whether it’s serving the stakeholders who matter most, meeting the compliance obligations your Board is accountable for, and performing at a level that supports rather than undermines the organisation’s credibility.
Performance benchmarks for nonprofit websites need to be framed around governance outcomes, not marketing metrics. This guide covers the specific benchmarks that Communications Directors should track, what ‘good’ looks like for established nonprofits with £500K–£10M budgets, and how to present performance to a Board that cares about institutional risk rather than traffic numbers.
Why Most Nonprofit Performance Metrics Miss the Point
The metrics that web agencies report — traffic growth, bounce rate, session duration, page views per visit — describe activity. They do not describe whether the website is doing its job. A nonprofit website that attracts 50,000 monthly visitors but has a broken donation flow, inaccessible programme pages, and outdated governance documents is failing at its institutional purpose regardless of its traffic numbers.
The benchmarks that matter for nonprofits are: can your primary stakeholders find what they need, can they complete the actions that serve the organisation’s mission, does the site meet its compliance obligations, and is the content accurate and current? These are governance benchmarks, not marketing benchmarks.
Page Speed and Core Web Vitals
Google’s Core Web Vitals are the closest thing to standardised performance metrics for websites. They measure three things: how quickly the main content loads (Largest Contentful Paint, LCP), how responsive the page is to interaction (Interaction to Next Paint, INP), and how stable the layout is as the page loads (Cumulative Layout Shift, CLS).
LCP target: under 2.5 seconds. This is achievable on Webflow with proper image optimisation and minimal third-party scripts. Nonprofit sites commonly fail this because of uncompressed hero images, multiple tracking scripts loading simultaneously, or heavy animation libraries on every page.
INP target: under 200ms. Most nonprofit Webflow sites pass this by default because they don’t have complex JavaScript interactions. If your site fails INP, it’s usually a third-party embed (chatbot, donation widget, social media feed) that’s blocking the main thread.
CLS target: under 0.1. Layout shift happens when elements load after the page appears and push content around. The most common cause on nonprofit sites is images without defined dimensions, web fonts loading late, and cookie consent banners that push content down.
Run PageSpeed Insights on your homepage, a programme page, and your donation page. If any page fails Core Web Vitals on mobile, it’s a priority fix — both for user experience and for search visibility.
Accessibility Benchmarks
WCAG AA compliance is not optional for nonprofit websites. The Equality Act 2010 creates accessibility obligations for any UK organisation providing services to the public, including digital services. The European Accessibility Act extends this for organisations serving EU audiences.
Automated scan baseline: zero critical violations. Run axe DevTools on your homepage monthly. The target is zero critical violations and a declining trend on serious violations. Automated tools catch approximately 30–40% of WCAG issues — the rest require manual testing.
Keyboard navigation: complete. Every interactive element on the site should be reachable and operable via keyboard alone. Test by pressing Tab through your homepage. If you can’t reach the navigation, the donation button, or the contact form, you have a critical accessibility failure.
Colour contrast: 4.5:1 for normal text, 3:1 for large text. This is not subjective. Use a contrast checker against your actual colour values.
Alt text coverage: 100% of meaningful images. Every image that conveys information needs a descriptive alt attribute. Decorative images should have an empty alt attribute.
For the full accessibility framework, see WCAG AA Accessibility on Webflow. For the governance argument for accessibility investment, see WCAG Accessibility as a Nonprofit Governance Obligation.
Content Currency Benchmarks
Content accuracy is a credibility metric. Institutional funders conducting due diligence check whether programme descriptions match current delivery, whether the annual report is current, and whether governance documents are visible and up to date.
Annual report: current financial year. If a funder visits your site and the most recent annual report is from two years ago, they will draw conclusions about governance quality.
Programme descriptions: reviewed within current quarter. Programmes evolve — new geographies, updated eligibility, changed delivery models. The website should reflect the current state, not the state when the page was first written.
Leadership and governance: current. The team page should list current staff and leadership. Trustees should be named (for UK charities, this is a Charity Commission expectation). Departed staff should be removed within one week of leaving.
News/blog: activity within current quarter. If the most recent blog post is from six months ago, it signals either that the organisation has stopped communicating or that the website is not being maintained. Either interpretation damages credibility.
Compliance documents: dated within current year. Privacy policy, accessibility statement, safeguarding policy — these should show a review date within the past 12 months.
Conversion Benchmarks
For nonprofits, ‘conversion’ means: did the website visitor complete an action that serves the organisation’s mission? The relevant conversions are donations, contact form submissions, newsletter sign-ups, document downloads (particularly annual reports and governance documents), and volunteer or programme applications.
Donation page conversion rate: 3–8% of visitors who reach the page. If fewer than 3% of people who visit your donation page complete a donation, the page has a problem — friction in the form, unclear messaging, broken mobile experience, or a payment platform that creates barriers. If your rate is above 8%, the page is performing well.
Contact form submission rate: depends on page purpose. A general enquiry form might see 2–5% conversion from page visitors. A programme-specific form where the visitor has clear intent might see 10–15%. The benchmark is less about the number and more about the trend — is it stable or declining?
Newsletter sign-up: 1–3% of site visitors. This is a secondary conversion for most nonprofits. If it’s significantly below 1%, check whether the sign-up is visible, whether the value proposition is clear, and whether the form works on mobile.
Set these up as Key Events in GA4, or as the equivalent conversion events in whichever analytics platform you run. See Analytics and Consent on Webflow: GTM, GA4, and Consent Mode V2 for implementation guidance, and note that privacy-focused alternatives such as Plausible, Fathom, or Cloudflare Web Analytics measure the same conversions without setting cookies, which simplifies PECR consent obligations.
Search Visibility Benchmarks
Google Search Console provides the data. The metrics that matter:
Branded search impressions: stable or growing. If impressions for your organisation’s name are declining, something has changed — either in search behaviour or in how Google evaluates your site. Investigate.
Non-branded impressions for mission terms: growing. These are searches related to what you do rather than who you are — people searching for your issue area, your service type, or your geography. Growth here indicates the site is building topical authority.
Click-through rate from search: 3–8% average. Below 3% suggests your title tags and meta descriptions aren’t compelling. Above 8% indicates strong relevance matching. This varies significantly by query type — branded queries will have much higher CTR than informational ones.
Indexed pages: stable and matching expectation. If the number of indexed pages drops unexpectedly, it signals a technical problem. If it’s growing faster than you’re publishing content, check for duplicate URLs or parameter-based crawling issues.
Uptime and Technical Health
Uptime: 99.9% minimum. Webflow hosting typically delivers this. If you’re self-hosting or using a custom setup, monitor uptime actively.
SSL certificate: valid and auto-renewing. An expired SSL certificate breaks the entire site and shows a security warning to every visitor. Webflow handles this automatically, but verify it’s working.
Console errors: zero critical errors. Open browser developer tools on your homepage. If there are JavaScript errors in the console, something is broken. Third-party scripts are the most common cause.
Broken internal links: zero. Run a crawl (Screaming Frog free version handles up to 500 URLs) quarterly. Every internal broken link is both a user experience failure and an SEO signal that the site isn’t maintained.
Quarterly Review Framework
These benchmarks should be reviewed quarterly. The review takes approximately 90 minutes and should produce a one-page summary for the Communications Director (operational) and a traffic-light overview for the Board (governance).
Quarter review covers: Core Web Vitals on three key pages, accessibility scan results and trend, content currency status on five key pages, conversion metrics for donation and contact forms, search visibility trends from Search Console, technical health (uptime, SSL, console errors, broken links).
The output should be a simple dashboard: green for benchmarks being met, amber for declining trends, red for benchmarks not being met. The Board version needs the traffic lights and one sentence per metric. The operational version needs the data, the trend, and a prioritised action list for the next quarter.
For related guidance, see A website maintenance schedule and Optimising images for performance.
Further Reading
- Why Your NGO Website Is a Governance Problem, Not a Marketing Problem
- Nonprofit Website Stakeholder Mapping Using Salience Theory
- Questions Your Board Should Be Asking About the Website
- How to Build an Internal Case for Nonprofit Website Investment
What These Benchmarks Actually Tell You
Any single metric in isolation is meaningless. What matters is the pattern across multiple dimensions over time. A site with excellent Core Web Vitals but outdated content is technically fast and institutionally negligent. A site with current content but broken accessibility is well-maintained and legally exposed. A site with good conversion rates but declining search visibility is serving existing audiences but failing to reach new ones.
The benchmarks above cover all the performance dimensions a nonprofit communications team needs to manage a well-governed website.
Frequently asked questions
Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1 — tested on the homepage, a programme page, and the donation page, on mobile as well as desktop. The common failure causes are uncompressed hero images and stacked tracking scripts for LCP, third-party embeds for INP, and undimensioned images, late-loading fonts, and consent banners for CLS.
Between 3 and 8 per cent of visitors who reach the donation page. Below 3 per cent indicates a problem — friction in the form, unclear messaging, a broken mobile experience, or a payment platform that creates barriers. Above 8 per cent, the page is performing well. The trend over time matters as much as the number itself.
Zero critical violations on a monthly automated scan such as axe DevTools, complete keyboard navigation across every interactive element, colour contrast of at least 4.5:1 for normal text and 3:1 for large text, and alt text on 100 per cent of meaningful images. Automated tools catch roughly 30 to 40 per cent of WCAG issues, so manual testing — particularly keyboard-only testing of the donation flow — remains essential.
Quarterly. The review takes approximately 90 minutes and covers Core Web Vitals on three key pages, accessibility scan trends, content currency on five key pages, donation and contact conversion, search visibility, and technical health. The Board version should be a traffic-light overview with one sentence per metric, framed as institutional risk; the operational version carries the data, the trends, and a prioritised action list for the next quarter.
Because traffic describes activity, not whether the website is doing its institutional job. A site attracting 50,000 monthly visitors with a broken donation flow, inaccessible programme pages, and outdated governance documents is failing regardless of its numbers. The benchmarks that matter are whether primary stakeholders can find what they need, complete the actions that serve the mission, and encounter accurate, current, compliant content.
