Website review, no card needed

cnext.bank logo

cnext.bank website review

Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 84 checks

This review found 43 issues worth fixing on cnext.bank, 17 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
3.1 s1.5 sApr 25Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.7 s
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.7 s
May 30, 20262.4 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
246 ms88 msApr 25Oct 10186 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026125 ms
May 2, 2026133 ms
May 9, 2026131 ms
May 16, 2026133 ms
May 23, 2026123 ms
May 30, 2026111 ms
Jun 6, 2026106 ms
Jun 13, 2026108 ms
Jun 20, 2026113 ms
Jun 27, 2026128 ms
Jul 4, 2026196 ms
Jul 11, 2026220 ms
Jul 18, 2026228 ms
Jul 25, 2026216 ms
Aug 1, 2026202 ms
Aug 8, 2026186 ms
Aug 15, 2026183 ms
Aug 22, 2026181 ms
Aug 29, 2026180 ms
Sep 5, 2026192 ms
Sep 12, 2026203 ms
Sep 19, 2026192 ms
Sep 26, 2026201 ms
Oct 3, 2026186 ms
Oct 10, 2026186 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 cnext.bank (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cnext.bank at 1.1 s1.1 s
  2. cnext.bank at 2.3 s2.3 s
  3. cnext.bank at 3.4 s3.4 s
  4. cnext.bank at 4.5 s4.5 s
  5. cnext.bank at 5.7 s5.7 s
  6. cnext.bank at 6.8 s6.8 s
  7. cnext.bank at 7.9 s7.9 s
  8. cnext.bank at 9.0 s9.0 s

Speed

14 to fix35
  • Use efficient cache lifetimes

    4.3 s · 1.1 MB

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

  • Reduce unused JavaScript

    3.9 s · 726 KiB

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

  • Improve image delivery

    1.7 s · 1.4 MB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 35

    35/100

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

  • 8 third-party services on the page

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

  • Font display

    900 ms

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

  • Google Tag Manager adds 560 ms

    560 ms

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

  • Legacy JavaScript

    350 ms · 25 KiB

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

  • Facebook adds 345 ms

    345 ms

    Facebook costs a phone 345 ms of main-thread work and 289 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.

  • Reduce unused CSS

    300 ms · 45 KiB

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

  • salemove.com adds 298 ms

    298 ms

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

  • Main-thread work: 2.7 s

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

  • 13 long tasks on the main thread

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 22.4 s

    22.4 s

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

  • Time to Interactive: 22.8 s

    22.8 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 650 ms

    650 ms

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user CLS: 0.17

    0.17

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

  • Tap response (INP) got 44% slower for real visitors

    +44%

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

  • Cumulative Layout Shift: 0.194

    0.194

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

  • 14 images without width and height

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

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 192 ms

    192 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 654 ms

    654 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

Images and page weight

3 to fix45
  • Page weight: 4.7 MB in 116 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 116 requests on a phone: images 2.9 MB (39), scripts 1.4 MB (25) and fonts 238 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    022657-cnext_online-enhancements_now_live-1400X.jpg weighs 513 KiB. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (1.4 MB) 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.

  • 3 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.34 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7788
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 16 text elements with low contrast

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

  • All page content should be contained by landmarks (15 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

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

  • 4 form fields without a label

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

3 to fixGoogle 7785
  • No H1 headline

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

  • No social preview image

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 75 internal links, 8 external

    The homepage links to 75 pages on cnext.bank and 8 external pages.

6 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “At Century Next Bank, we don't just do business in our communities, we invest in them... and that means investing in yo…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “CNext - Century Next Bank | Lincoln | Ouachita | Ashley County”.

  • Canonical URL set

    The canonical URL is https://www.cnext.bank/.

  • Structured data in place

    Structured data found: LocalBusiness.

  • 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://www.cnext.bank/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

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

  • No llms.txt

    There is no https://www.cnext.bank/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.

2 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (351 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 48 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 185 words

    The homepage has only about 185 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • Phone number is not tap-to-call

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

  • 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.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Contact Us” and “Learn More →”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 13 cookies set on arrival

    13

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

  • No consent tool detected

    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.

  • 23 other companies contacted

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

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 cnext.bank, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on cnext.bank, including 24 speed issues, 3 SEO issues 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