www.nami.org speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:43 UTC. Grade C (73/100), with the screenshots, the timings and the fixes that matter.

https://www.nami.org/

20 October 2026 at 15:43 UTC · Free test · report pt_a0094298a40d
Grade
C
73/100
Performance75/100
Structure71/100

11 audit(s) passed, 5 need work

First byte (TTFB)165 msmeasured from this server
Fully loaded1.15 sfirst byte + slowest asset
Requests26document + assets
Page weight5.32 MBcompressed transfer
HTML document43.6 KBbr
ProtocolHTTP/3cloudflare
Third-party74.3 KBother hosts

Where the first byte went

  • DNS lookup 58 ms 35%
  • TCP connect 10 ms 6%
  • Server wait 97 ms 59%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 97% of 4,999 pages tested here165 ms against a median of 449 ms
Page weightheavier than 94% of 4,999 pages tested here5.32 MB against a median of 650.3 KB
Fully loadedfaster than 89% of 4,999 pages tested here1.15 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The server answered in 165 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 5.32 MB over 26 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 644 ms, inside the 2.5 s Google calls good.
  • Layout shift is 0.215 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 489 ms, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.nami.org
Mobile 390 × 844 · 314.5 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint644 msgood is under 2.5 s
Cumulative layout shift0.215under 0.1 is stable
Total blocking time489 mslong tasks during load
First contentful paint444 msfirst content on screen
Browser page weight8.26 MB253 request(s), scripts included
Failed requests9blocked or unreachable
Largest contentful paint644 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.215
Needs improvementgood under 0.1, poor over 0.25
Total blocking time489 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
5.28 MB 99%

Transfer size, compressed as sent. 26 request(s) in total, 5.32 MB across all of them.

Top issues

Image delivery and format

high impact

9 image(s) over 200 KB and 11 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

30 render-blocking resource(s) in the document head (11 script(s), 19 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 5.32 MB across 26 request(s), with the document itself at 43.6 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESwww.nami.org/wp-content/uploads/2026/02/NAMIWalks-H…
980 ms
IMAGESwww.nami.org/wp-content/uploads/2026/02/NAMI-walks-…
946 ms
IMAGESwww.nami.org/wp-content/uploads/2023/04/call.png
946 ms
IMAGESwww.nami.org/wp-content/uploads/2026/04/93k-360x241…
936 ms
IMAGESwww.nami.org/wp-content/uploads/NAMI-Member-Circle-…
934 ms
IMAGESwww.nami.org/wp-content/uploads/2026/01/personal-gi…
932 ms
IMAGESwww.nami.org/wp-content/uploads/NAMI-NAMICon-Circle…
927 ms
IMAGESwww.nami.org/wp-content/uploads/2023/04/chat.png
927 ms
IMAGESwww.nami.org/wp-content/uploads/NAMI-Donator-Circle…
922 ms
IMAGESwww.nami.org/wp-content/uploads/2023/04/crisis.png
920 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.nami.org/wp-content/uploads/2026/02/NAMIWalks-HP.jpgimages200980 ms135.4 KB
https://www.nami.org/wp-content/uploads/2026/02/NAMI-walks-Indy-HP.jpgimages200946 ms160.7 KB
https://www.nami.org/wp-content/uploads/2023/04/call.pngimages200946 ms1.2 KB
https://www.nami.org/wp-content/uploads/2026/04/93k-360x241-1.pngimages200936 ms2.5 KB
https://www.nami.org/wp-content/uploads/NAMI-Member-Circle-scaled.jpegimages200934 ms509.1 KB
https://www.nami.org/wp-content/uploads/2026/01/personal-giving-cropped.jpgimages200932 ms166.2 KB
https://www.nami.org/wp-content/uploads/NAMI-NAMICon-Circle-scaled.jpgimages200927 ms499.6 KB
https://www.nami.org/wp-content/uploads/2023/04/chat.pngimages200927 ms937 B
https://www.nami.org/wp-content/uploads/NAMI-Donator-Circle-scaled.jpgimages200922 ms528.0 KB
https://www.nami.org/wp-content/uploads/2023/04/crisis.pngimages200920 ms1008 B
https://www.nami.org/wp-content/uploads/2024/08/NAMI-Advocate-Circle.webpimages200914 ms56.1 KB
https://www.nami.org/wp-content/uploads/2023/04/fundraise-scaled.jpgimages200902 ms412.2 KB
https://www.nami.org/wp-content/uploads/2024/08/home-podcasts.webpimages200887 ms82.8 KB
https://img.youtube.com/vi/BZNw3Ldtxrg/maxresdefault.jpg 3rd partyimages200875 ms74.3 KB
https://www.nami.org/wp-content/uploads/2026/10/NewGuideSchizophreniaintheBlackCommunity_Circle.pngimages200866 ms933.3 KB
https://www.nami.org/wp-content/uploads/2025/09/NAMI-LOGO.webpimages200860 ms23.2 KB
https://www.nami.org/wp-content/uploads/2025/07/NAMI40738_28-Evergreen_HPAsset_Interstitial.pngimages200859 ms679.2 KB
https://www.nami.org/wp-content/uploads/2024/03/States-HP-Infograph.webpimages200859 ms4.3 KB
https://www.nami.org/wp-content/uploads/2024/08/hugging-scaled-1.webpimages200858 ms91.7 KB
https://www.nami.org/wp-content/uploads/2025/07/NAMI40738_28-Evergreen_HPAsset_HeroImage.pngimages200856 ms344.0 KB
https://www.nami.org/wp-content/uploads/2026/09/NAMIRuns-Circle-Image.jpg?v=1788468614674097images200844 ms246.4 KB
https://www.nami.org/wp-content/uploads/2024/08/helpline-1-scaled-1.webpimages200838 ms308.6 KB
https://www.nami.org/wp-content/uploads/2024/03/Advocate-HP-Infograph.webpimages200822 ms3.2 KB
https://www.nami.org/wp-content/uploads/2024/08/NAMI-Warning-Signs-Symptoms-Home.webpimages200813 ms93.4 KB
https://www.nami.org/wp-content/uploads/2024/08/NAMI-Find-Support-Circle.webpimages200808 ms51.0 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.