Website review, no card needed
hsbc.co.in website review
Visit site (opens in a new tab)Reviewed 3 November 202636 issues · 80 checks
This review found 36 issues worth fixing on hsbc.co.in, 6 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 378 ms |
| May 23, 2026 | 378 ms |
| May 30, 2026 | 381 ms |
| Jun 6, 2026 | 383 ms |
| Jun 13, 2026 | 384 ms |
| Jun 20, 2026 | 384 ms |
| Jun 27, 2026 | 368 ms |
| Jul 4, 2026 | 345 ms |
| Jul 11, 2026 | 328 ms |
| Jul 18, 2026 | 312 ms |
| Jul 25, 2026 | 307 ms |
| Aug 1, 2026 | 304 ms |
| Aug 8, 2026 | 297 ms |
| Aug 15, 2026 | 294 ms |
| Aug 22, 2026 | 292 ms |
| Aug 29, 2026 | 272 ms |
| Sep 5, 2026 | 258 ms |
| Sep 12, 2026 | 253 ms |
| Sep 19, 2026 | 246 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 237 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 235 ms |
| Oct 24, 2026 | 235 ms |
| Oct 31, 2026 | 236 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.2 s · 500 KiBAbout 500 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 214 KiB7 files are served with short cache lifetimes, so returning visitors download them again (214 KiB).
5 third-party services on the page
5 third-party services load with your homepage (LivePerson, awswaf.com and Tealium and others), adding 931 KiB and 673 ms of main-thread time.
Improve image delivery
600 ms · 120 KiB2 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
450 ms · 95 KiBAbout 95 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.
LivePerson adds 272 ms
272 msLivePerson costs a phone 272 ms of main-thread work and 504 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 264 ms. During a long task the page ignores taps.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
awswaf.com adds 200 ms
200 msawswaf.com costs a phone 200 ms of main-thread work and 315 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,049 HTML elements
The page has 2,049 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Real-user INP: 353 ms
353 msReal visitors wait 353 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user TTFB: 836 ms
836 msReal visitors wait 836 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.232
0.232The layout shifts by 0.232 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 368 ms
368 msScripts block taps and scrolling for 368 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 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.
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 378 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 45% faster for real visitors
-45%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
2 images in older formats
2 images (60 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 2.0 MB in 77 requests
2.0 MBYour homepage downloads 2.0 MB in 77 requests on a phone: scripts 1.1 MB (20), images 428 KiB (18) and fonts 193 KiB (7). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
451 internal links, 24 external
The homepage links to 451 pages on hsbc.co.in and 24 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Get banking and financial investment services such as credit card, nri services, loans and money transfers via internet…”.
Title: 59 characters
Your title is a healthy 59 characters: “HSBC India - Credit Cards, NRI Services, Saving and Deposit”.
Canonical URL set
The canonical URL is https://www.hsbc.bank.in/.
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.hsbc.bank.in/sitemaps.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.hsbc.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.
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 (2,035 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.hsbc.bank.in/security is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.hsbc.bank.in/security has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hsbc.bank.in/premier/international-privileges, whose canonical is https://www.hsbc.bank.in/accounts/products/premier. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.hsbc.bank.in/security has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.hsbc.bank.in/premier/family-banking, https://www.hsbc.bank.in/premier/offers and https://www.hsbc.bank.in/premier/international-privileges took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 127 found) and read each the way a search engine does.
3 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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
20 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 939 words of copy
The homepage carries about 939 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: “Learn more”.
29 calls to action
The homepage has 29 calls to action, for example “Register”, “Contact us” and “Do Not Call & Marketing Opt-out”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
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
2 cookies set on arrival
2Opening the homepage sets 2 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 hsbc.co.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on hsbc.co.in, including 23 speed issues, 3 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.