Website review, no card needed
columbiabankonline.com website review
Visit site (opens in a new tab)Reviewed 2 November 202630 issues · 82 checks
This review found 30 issues worth fixing on columbiabankonline.com, 12 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 181 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 183 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 174 ms |
| Jun 27, 2026 | 178 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 186 ms |
| Jul 25, 2026 | 182 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 190 ms |
| Sep 26, 2026 | 194 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 186 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Render-blocking requests
5.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Use efficient cache lifetimes
3.1 s · 719 KiB26 files are served with short cache lifetimes, so returning visitors download them again (719 KiB).
onlineaccess1.com adds 1.1 s
1.1 sonlineaccess1.com costs a phone 1.1 s of main-thread work and 188 KiB 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: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
2.1 MB11 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (onlineaccess1.com, Google Tag Manager and Optanon and others), adding 955 KiB and 1.8 s of main-thread time.
Reduce unused JavaScript
900 ms · 434 KiBAbout 434 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Reduce unused CSS
450 ms · 92 KiBAbout 92 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 406 ms
406 msGoogle Tag Manager costs a phone 406 ms of main-thread work and 338 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.
2,195 HTML elements
The page has 2,195 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 191 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Advantage Rewards Homepage Panel”.
Time to Interactive: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 539 ms
539 msScripts block taps and scrolling for 539 ms in total while the page loads. Good is under 200 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 181 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 194 ms
194 msReal visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 393 ms
393 msReal visitors wait 393 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.052
0.052The layout barely moves while loading (CLS 0.052, good is under 0.1).
Images and page weight
Page weight: 6.6 MB in 111 requests
6.6 MBYour homepage downloads 6.6 MB in 111 requests on a phone: images 4.7 MB (57), scripts 1.0 MB (14) and fonts 739 KiB (8). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.5 MB4 images are downloaded at several times the size a phone draws them, for example 5f768afba02bad3f53b8aa8398d3be6f.png at 3,654 px wide, shown at 225 px. Resized copies would save about 1.5 MB.
6 images below the first screen load straight away
6 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.88 g of CO₂e: 225.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 64 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
220 links crawlers can't follow
220 links have no real href, so search engines can't follow them.
35 links with vague text
35 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (237 characters)
Your meta description is 237 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
113 internal links, 37 external
The homepage links to 113 pages on columbiabankonline.com and 37 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Have Peace of Mind Knowing You're Covered by Columbia Insurance Services.”.
Title: 59 characters
Your title is a healthy 59 characters: “Personalized Financial Solutions in NJ & NY | Columbia Bank”.
Canonical URL set
The canonical URL is https://www.columbiabankonline.com/.
Structured data in place
Structured data found: BankOrCreditUnion and organization.
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://www.columbiabankonline.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.columbiabankonline.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.
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 (3,084 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 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
6 small tap targets
6 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://www.gstatic.com/_/translate_http/_/ss/k=translate_http.tr.zZZZhVqDDCw.L.W.O/am=AACAAQ/d=0/rs=AN8…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 1,061 words of copy
The homepage carries about 1,061 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Learn More”.
41 calls to action
The homepage has 41 calls to action, for example “Schedule an Appointment”, “Contact Us” and “Learn More”.
8 short forms
8 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links 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.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 columbiabankonline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Employees
- 585
- Founded
- 1927
- Headquarters
- Fair Lawn
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on columbiabankonline.com, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.