wealthcu.org website review

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

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

8 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (onlineaccess1.com, Google Tag Manager and salemove.com and others), adding 2.2 MB and 2.3 s of main-thread time.

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

onlineaccess1.com costs a phone 820 ms of main-thread work and 186 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.

Google Tag Manager costs a phone 714 ms of main-thread work and 814 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.

salemove.com costs a phone 283 ms of main-thread work and 430 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.

financialtown.com costs a phone 158 ms of main-thread work and 402 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.

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

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

78 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 51.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Real visitors wait 301 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 9.3 MB in 148 requests on a phone: images 5.5 MB (36), scripts 2.2 MB (44) and fonts 1.3 MB (9). Under 2 MB keeps phones on slow connections fast.

2 images (113 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 2.63 g of CO₂e: 316.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (3 elements).

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 189 pages on wealthcu.org and 28 external pages.

There is no https://www.wealthcu.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 65 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27004991&tm=gtm002&Ver=2&mid=35997406-2b71-4795-aaca-06d559231383&bo=1&sid=4ba7d160cc3411f18d652b6218bc927e&vid=4ba836b0cc3411f1809c9132b9df0efb&vids=1&msclkid=N&pi=91.

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'prototype')”.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,075 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 5 mores (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 17 cookies, 2 of them by other companies (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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.