Website review, no card needed

bandhanmutual.com logo

bandhanmutual.com website review

Visit site (opens in a new tab)Reviewed 30 October 202652 issues · 76 checks

This review found 52 issues worth fixing on bandhanmutual.com, 30 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
8.1 s4.4 sMay 9Oct 247.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.5 s
May 16, 20265.7 s
May 23, 20265.8 s
May 30, 20265.4 s
Jun 6, 20264.9 s
Jun 13, 20264.9 s
Jun 20, 20264.9 s
Jun 27, 20265.1 s
Jul 4, 20266.1 s
Jul 11, 20266.1 s
Jul 18, 20266.2 s
Jul 25, 20266.3 s
Aug 1, 20266.5 s
Aug 8, 20266.7 s
Aug 15, 20266.9 s
Aug 22, 20266.7 s
Aug 29, 20266.7 s
Sep 5, 20266.7 s
Sep 12, 20266.6 s
Sep 19, 20266.8 s
Sep 26, 20266.9 s
Oct 3, 20266.9 s
Oct 10, 20267.3 s
Oct 17, 20267.6 s
Oct 24, 20267.7 s
Real-visitor tap response (INP)75th percentile, phones
505 ms381 msMay 9Oct 24490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026395 ms
May 16, 2026406 ms
May 23, 2026411 ms
May 30, 2026410 ms
Jun 6, 2026410 ms
Jun 13, 2026412 ms
Jun 20, 2026414 ms
Jun 27, 2026420 ms
Jul 4, 2026427 ms
Jul 11, 2026427 ms
Jul 18, 2026430 ms
Jul 25, 2026439 ms
Aug 1, 2026449 ms
Aug 8, 2026463 ms
Aug 15, 2026472 ms
Aug 22, 2026468 ms
Aug 29, 2026463 ms
Sep 5, 2026453 ms
Sep 12, 2026447 ms
Sep 19, 2026449 ms
Sep 26, 2026462 ms
Oct 3, 2026477 ms
Oct 10, 2026478 ms
Oct 17, 2026491 ms
Oct 24, 2026490 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 bandhanmutual.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bandhanmutual.com at 1.7 s1.7 s
  2. bandhanmutual.com at 3.5 s3.5 s
  3. bandhanmutual.com at 5.2 s5.2 s
  4. bandhanmutual.com at 7.0 s7.0 s
  5. bandhanmutual.com at 8.7 s8.7 s
  6. bandhanmutual.com at 10.4 s10.4 s
  7. bandhanmutual.com at 12.2 s12.2 s
  8. bandhanmutual.com at 13.9 s13.9 s

Speed

13 to fix24
  • Reduce unused JavaScript

    11.8 s · 2.3 MB

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

  • Improve image delivery

    3.5 s · 2.2 MB

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

  • Use efficient cache lifetimes

    2.5 s · 465 KiB

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

  • Main-thread work: 13.1 s

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

  • Render-blocking requests

    1.1 s

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

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 696 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: 24

    24/100

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

  • 20 long tasks on the main thread

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

  • 8 third-party services on the page

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

  • Font display

    700 ms

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

  • Reduce unused CSS

    310 ms · 68 KiB

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

  • Facebook adds 290 ms

    290 ms

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

  • Other Google APIs/SDKs adds 0 ms

    0 ms

    Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 2.3 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.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • 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: 3 ms

    3 ms

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

Core Web Vitals

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

  • Real-user LCP: 10.4 s

    10.4 s

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

  • Real-user INP: 694 ms

    694 ms

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

  • Real-user CLS: 0.28

    0.28

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

  • Real-user FCP: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 40.2 s

    40.2 s

    Your largest element takes 40.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide 1 of 4”.

  • Speed Index: 28.8 s

    28.8 s

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

  • Total Blocking Time: 6.8 s

    6.8 s

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

  • Time to Interactive: 40.4 s

    40.4 s

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

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

    +22%

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

  • Largest content (LCP) got 36% slower for real visitors

    +36%

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

  • Real-user TTFB: 942 ms

    942 ms

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

  • Cumulative Layout Shift: 0.207

    0.207

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

  • 21 images without width and height

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

1 checks passed
  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 8.2 MB in 98 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 98 requests on a phone: scripts 4.0 MB (22), images 2.9 MB (38) and other files 1.1 MB (30). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.31 g of CO₂e: 277.3 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

8 to fixGoogle 7087
  • Certain ARIA roles must be contained by particular parents (6 elements)

    Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

  • Orphan list items

    Some list items are not inside a list.

  • 4 tap targets too small

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

  • 2 text elements with low contrast

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

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

7 to fixGoogle 9260
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Bandhan Mutual Fund - Leading Online Mutual Fund Services in India”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

2 checks passed
  • 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://bandhanmutual.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://bandhanmutual.com/llms.txt (6 KiB, 33 links), a plain-text guide to the site for AI tools.

Best practices

2 to fixGoogle 9674
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187233905&Ver=2&mid=cc763a42-479c-4b44-899a-6277365c5a49&bo=1&sid=73f32070d48f11f1b00a65a733f1e3be&vid=73f36780d48f11f1a047d54627281a98&vids=1&msclkid=N&pi=918639831&l.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 0 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 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.

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

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 bandhanmutual.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
F5

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on bandhanmutual.com, including 27 speed issues, 7 SEO issues and 5 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