rhb24.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Squarespace and Facebook and others), adding 4.7 MB and 1.5 s of main-thread time.

Google Tag Manager costs a phone 782 ms of main-thread work and 902 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 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.

11 files are served with short cache lifetimes, so returning visitors download them again (218 KiB).

Squarespace costs a phone 515 ms of main-thread work and 1.2 MB 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.

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.9 MB 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.

Adobe TypeKit costs a phone 20 ms of main-thread work and 412 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.

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

7 images could be 110 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Desktop scores 63 but mobile only 36. 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 10.7 s on a phone. Good is under 1.8 s.

Your largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FDIC”.

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

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

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

2 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-17, real Chrome visitors' tap response (inp) went from 163 ms to 171 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 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 109 requests on a phone: scripts 2.3 MB (52), images 1.9 MB (16) and fonts 404 KiB (18). Under 2 MB keeps phones on slow connections fast.

CONtactless+(2).png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

There are 21 <h1> headlines (“PRODUCTS”, “Investing in the very best in Tech” and “Online Banking”). One clear main headline is easier for people and search engines.

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

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5c12ce1bf8370a8b158…”.

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

The homepage links to 107 pages on rhb24.com and 15 external pages.

Your Organization JSON-LD is missing name, url, logo, 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://www.rhb24.com/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://www.rhb24.com/about-index and https://www.rhb24.com/about-us all use the title “About Index — RiverHills Bank”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rhb24.com/personal-accounts, https://www.rhb24.com/business-accounts, https://www.rhb24.com/treasury-management, https://www.rhb24.com/commercial-loans, https://www.rhb24.com/impact-depositing-index and https://www.rhb24.com/my-custom-card and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.rhb24.com/about-us, whose canonical is https://www.rhb24.com/about-index. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/custom-css/5c12ce1bf8370a8b158be61a/5c13d5f36d2a73e…”.

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

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

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