Website review, no card needed

canarabank.com logo

canarabank.com website review

Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 87 checks

This review found 40 issues worth fixing on canarabank.com, 12 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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.6 s2.2 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
184 ms155 msMay 16Oct 31181 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026173 ms
May 23, 2026171 ms
May 30, 2026168 ms
Jun 6, 2026164 ms
Jun 13, 2026162 ms
Jun 20, 2026161 ms
Jun 27, 2026161 ms
Jul 4, 2026161 ms
Jul 11, 2026160 ms
Jul 18, 2026160 ms
Jul 25, 2026159 ms
Aug 1, 2026159 ms
Aug 8, 2026159 ms
Aug 15, 2026158 ms
Aug 22, 2026159 ms
Aug 29, 2026159 ms
Sep 5, 2026160 ms
Sep 12, 2026161 ms
Sep 19, 2026162 ms
Sep 26, 2026164 ms
Oct 3, 2026170 ms
Oct 10, 2026175 ms
Oct 17, 2026179 ms
Oct 24, 2026180 ms
Oct 31, 2026181 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 canarabank.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. canarabank.com at 0.6 s0.6 s
  2. canarabank.com at 1.3 s1.3 s
  3. canarabank.com at 1.9 s1.9 s
  4. canarabank.com at 2.5 s2.5 s
  5. canarabank.com at 3.2 s3.2 s
  6. canarabank.com at 3.8 s3.8 s
  7. canarabank.com at 4.4 s4.4 s
  8. canarabank.com at 5.0 s5.0 s

Speed

11 to fix47
  • Render-blocking requests

    3.4 s

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

  • Mobile performance score: 47

    47/100

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

  • Improve image delivery

    5.0 MB

    17 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Document request latency

    900 ms · 367 KiB

    The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused CSS

    950 ms · 242 KiB

    About 242 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 950 ms faster on a phone.

  • Reduce initial server response time

    882 ms

    Reduce initial server response time. Google estimates savings of 882 ms on a phone.

  • Use efficient cache lifetimes

    500 ms · 92 KiB

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

  • Reduce unused JavaScript

    310 ms · 189 KiB

    About 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • Main-thread work: 2.7 s

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

  • 2,214 HTML elements

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

  • Server response: 982 ms

    982 ms

    Your server takes 982 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and jQuery CDN and others), adding 576 KiB and 338 ms of main-thread time.

  • Minify CSS

    180 ms · 61 KiB

    61 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    45 KiB

    45 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

11 to fix0
  • 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.6 s

    22.6 s

    Your largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FCNR (B) CALCULATOR REKYC UPDATION/ ACCOUNT ACTIVATION THRO…”.

  • Time to Interactive: 29.3 s

    29.3 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user INP: 222 ms

    222 ms

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

  • Real-user CLS: 0.19

    0.19

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.196

    0.196

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

  • 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

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

2 checks passed
  • Real-user TTFB: 740 ms

    740 ms

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

  • Total Blocking Time: 141 ms

    141 ms

    Scripts block the page for only 141 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • Page weight: 11.4 MB in 206 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 206 requests on a phone: images 5.9 MB (72), other files 2.8 MB (23) and scripts 1.5 MB (77). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    3.4 MB

    11 images are downloaded at several times the size a phone draws them, for example 55b48446-a09c-48d5-f317-a8c26e0edbeb at 1,921 px wide, shown at 390 px. Resized copies would save about 3.4 MB.

  • 8 images in older formats

    8 images (3.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.

  • 2 images below the first screen load straight away

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

  • About 3.2 g of CO₂ per visit

    3.23 g

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

Accessibility

3 to fixGoogle 10097
  • All page content should be contained by landmarks (9 elements)

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

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

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), 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).

2 checks passed
  • Every image has alt text

    All 89 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 9291
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

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

  • 365 internal links, 85 external

    The homepage links to 365 pages on canarabank.com and 85 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Canara Bank offers personal & corporate banking services including accounts, loans, cards, deposits, net banking & more…”.

  • One H1 headline

    Your main headline reads: “Home page”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Canara Bank - Personal & Corporate Banking Services”.

  • Canonical URL set

    The canonical URL is https://www.canarabank.bank.in/.

  • 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://canarabank.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.canarabank.bank.in/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 2 pages without a meta description

    https://www.canarabank.bank.in/screen-reader and https://www.canarabank.bank.in/feedback have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.canarabank.bank.in/about-us, whose canonical is https://www.canarabank.bank.in/pages/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.canarabank.bank.in/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.canarabank.bank.in/feedback took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://cabprod.gupshup.io/morfeuswebsdk/img/bot-icon-yellow.png.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'backdrop')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 842 words of copy

    The homepage carries about 842 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY FOR PRE-APPROVED CREDIT CARD”.

  • 32 calls to action

    The homepage has 32 calls to action, for example “Contact Us”, “Investment Secure your Future Apply Now” and “Apply Pre-Approved Credit card”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 canarabank.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
React
Analytics
Google Analytics
Hosting
AWS

Hiring

Hiring
2 open roles
Job board
careers page

Company

Employees
53,508
Founded
1906
Headquarters
Bengaluru

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on canarabank.com, including 22 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