napawash.org website review

42 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

10 images could be 780 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

About 584 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

87 KiB could be saved by minifying JavaScript.

About 172 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

8 third-party services load with your homepage (ShareThis, Google Analytics and Google Tag Manager and others), adding 894 KiB and 285 ms of main-thread time.

2 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Solving Public Management Challenges Through Independent Th…”. Most of its time is resource load delay (8.2 s).

Visually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 16.0 s. Good is under 3.8 s.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

9 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 82 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images are downloaded at several times the size a phone draws them, for example P20260929DT-1520.webp at 3,000 px wide, shown at 128 px. Resized copies would save about 671 KiB.

Your homepage downloads 3.1 MB in 93 requests on a phone: images 1.5 MB (33), scripts 939 KiB (15) and fonts 443 KiB (12). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (777 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (649 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 105.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

27 links have no real href, so search engines can't follow them.

Structured data found (BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Organization: missing name”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at napawash.org/robots.txt, the first file search crawlers ask for.

The homepage links to 61 pages on napawash.org and 5 external pages.

There is no https://napawash.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://napawash.org/solutions, https://napawash.org/our-work and https://napawash.org/commentary all use the title “National Academy of Public Administration”. Search engines can't tell which page to show for a search, so each competes with the others.

https://napawash.org/solutions, https://napawash.org/our-work and https://napawash.org/commentary have no meta description, so Google writes the search snippet from whatever text it finds.

https://napawash.org/solutions, https://napawash.org/our-fellows, https://napawash.org/our-work and https://napawash.org/commentary have no <h1> headline, so visitors and search engines get no clear main topic.

https://napawash.org/commentary and https://napawash.org/donate took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

3 images failed to load on a phone, for example https://napawash.org/imager/uploads/partner-logos/39255/goldman-logo-2021_5f28a37dfffeac17d8504dfc1bc3d34b.svg.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://napawash.org' has been blocked by …”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 13 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 300 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 7 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.