Website review, no card needed

communitybank.com logo

communitybank.com website review

Visit site (opens in a new tab)Reviewed 7 November 202625 issues · 84 checks

This review found 25 issues worth fixing on communitybank.com, 15 of them high impact, across 84 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s2.0 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
151 ms135 msMay 16Oct 31149 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026145 ms
May 23, 2026143 ms
May 30, 2026144 ms
Jun 6, 2026143 ms
Jun 13, 2026143 ms
Jun 20, 2026143 ms
Jun 27, 2026144 ms
Jul 4, 2026144 ms
Jul 11, 2026145 ms
Jul 18, 2026144 ms
Jul 25, 2026143 ms
Aug 1, 2026141 ms
Aug 8, 2026140 ms
Aug 15, 2026139 ms
Aug 22, 2026139 ms
Aug 29, 2026138 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026138 ms
Sep 26, 2026138 ms
Oct 3, 2026139 ms
Oct 10, 2026140 ms
Oct 17, 2026144 ms
Oct 24, 2026146 ms
Oct 31, 2026149 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of communitybank.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. communitybank.com at 0.4 s0.4 s
  2. communitybank.com at 0.8 s0.8 s
  3. communitybank.com at 1.1 s1.1 s
  4. communitybank.com at 1.5 s1.5 s
  5. communitybank.com at 1.9 s1.9 s
  6. communitybank.com at 2.3 s2.3 s
  7. communitybank.com at 2.6 s2.6 s
  8. communitybank.com at 3.0 s3.0 s

Speed

10 to fix40
  • Avoid multiple page redirects

    12.2 s

    The page goes through 1 redirect before it starts loading, costing about 12.2 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    7.7 s · 1.0 MB

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

  • Improve image delivery

    1.1 s · 311 KiB

    11 images could be 311 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 1.3 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.

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 4.8 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, silvercloudinc.com and Azure Web Services and others), adding 1.7 MB and 1.4 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 376 KiB

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

  • Render-blocking requests

    850 ms

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

  • 1,543 HTML elements

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    95 KiB

    About 95 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 27.5 s

    27.5 s

    Your largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies for essential site …”.

  • Time to Interactive: 30.4 s

    30.4 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 151 ms

    151 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 497 ms

    497 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.6 MB in 325 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 325 requests on a phone: scripts 3.9 MB (189), images 1,023 KiB (27) and other files 412 KiB (75). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.58 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8592
  • ARIA attributes must conform to valid values (3 elements)

    ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

  • 3 tap targets too small

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

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • Hidden but focusable

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 10 links with vague text

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

  • 96 internal links, 31 external

    The homepage links to 96 pages on communitybank.com and 31 external pages.

8 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “For over 155 years, Community Bank, N.A. has prioritized putting customers first. More than a full-service bank, we're …”.

  • One H1 headline

    Your main headline reads: “Banking options for a better life”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Community Bank, N.A. | Your Trusted Neighborhood Bank”.

  • Canonical URL set

    The canonical URL is https://cbna.com/.

  • Structured data in place

    Structured data found: BankOrCreditUnion, BreadcrumbList, Organization and WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://cbna.com/sitemaps-1-sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (849 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • Local business without LocalBusiness data

    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.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 593 words of copy

    The homepage carries about 593 words of visible text.

7 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Open/Apply”, “Contact” and “Request A Callback”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar, LinkedIn Insight, Meta Pixel and The Trade Desk (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at communitybank.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Tag Manager
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on communitybank.com, including 16 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25