citadelbanking.com website review

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

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

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

YouTube costs a phone 1.0 s of main-thread work and 2.0 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 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and FontAwesome CDN and others), adding 3.4 MB and 2.7 s of main-thread time.

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

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

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

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

2 KiB JavaScript is shipped twice across bundles.

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 8.9 s on a phone. Good is under 1.8 s.

Your largest element takes 17.6 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 39.1 s. Good is under 3.8 s.

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

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

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

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

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

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

The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

8 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' largest content (lcp) went from 2.8 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 284 requests on a phone: scripts 4.7 MB (85), images 386 KiB (64) and fonts 330 KiB (12). Under 2 MB keeps phones on slow connections fast.

3944-heloc-flyout-02.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (56 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.68 g of CO₂e: 202.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 elements use ARIA attributes their role does not allow, which confuses screen readers.

6 elements hidden from screen readers can still receive keyboard focus.

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

1 link inside paragraphs relies on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 73 characters, so Google will cut it off around 60: “Citadel Credit Union | Mobile Banking, Credit Cards, Mortgages, Auto Loan”.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

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

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

The homepage links to 183 pages on citadelbanking.com and 22 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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 119 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=134605299&tm=gtm002&Ver=2&mid=5219b1fd-05b6-438f-961b-d6cb371963ba&bo=1&sid=da9bcfe0d4a611f1866a65f8add1f369&vid=da9bf480d4a611f1aa025357c7ce0fcf&vids=1&msclkid=N&pi=9.

7 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 “Failed to load resource: net::ERR_CONNECTION_RESET”.

Large scripts ship without source maps.

Requests the geolocation permission on page load.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://citadelbanking.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

citadelbanking.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

citadelbanking.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The homepage carries about 938 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 9 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 28 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 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.