truwest.org website review

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

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

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

cloudfront.net costs a phone 1.2 s of main-thread work and 2.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 32 (desktop: 72). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,858 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (cloudfront.net, Cookiebot and eltropy.com and others), adding 3.5 MB and 1.7 s of main-thread time.

3 images could be 470 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

About 113 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.

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

eltropy.com costs a phone 177 ms of main-thread work and 748 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

27 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 85 KiB JavaScript that modern phones do not need.

16 KiB could be saved by minifying CSS.

Desktop scores 72 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Build Your Future with TruWest Credit Union Committed to He…”.

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

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

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 5.1 MB in 181 requests on a phone: scripts 3.4 MB (69), images 1.0 MB (40) and fonts 503 KiB (17). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example botAvatar.png at 5,132 px wide, shown at 39 px. Resized copies would save about 354 KiB.

3 images (506 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.

1 image further down the page (81 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

20 tap targets are too small or too close together to hit reliably with a finger.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

5 visible links have no text or label, so screen readers cannot say where they go.

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

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 154 pages on truwest.org and 22 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://truwest.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.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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 898 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 1 cookie (measured from a US location before any click).

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