Website review, no card needed

sbicaps.com logo

sbicaps.com website review

Visit site (opens in a new tab)Reviewed 3 November 202642 issues · 86 checks

This review found 42 issues worth fixing on sbicaps.com, 22 of them high impact, across 86 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
2.6 s1.4 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20262.0 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
145 ms99 msMay 16Oct 31135 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026106 ms
May 23, 2026105 ms
May 30, 2026107 ms
Jun 6, 2026104 ms
Jun 13, 2026106 ms
Jun 20, 2026111 ms
Jun 27, 2026109 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026114 ms
Jul 25, 2026120 ms
Aug 1, 2026126 ms
Aug 8, 2026130 ms
Aug 15, 2026138 ms
Aug 22, 2026137 ms
Aug 29, 2026133 ms
Sep 5, 2026135 ms
Sep 12, 2026136 ms
Sep 19, 2026136 ms
Sep 26, 2026138 ms
Oct 3, 2026140 ms
Oct 10, 2026138 ms
Oct 17, 2026136 ms
Oct 24, 2026138 ms
Oct 31, 2026135 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 sbicaps.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sbicaps.com at 1.5 s1.5 s
  2. sbicaps.com at 3.1 s3.1 s
  3. sbicaps.com at 4.6 s4.6 s
  4. sbicaps.com at 6.2 s6.2 s
  5. sbicaps.com at 7.7 s7.7 s
  6. sbicaps.com at 9.3 s9.3 s
  7. sbicaps.com at 10.8 s10.8 s
  8. sbicaps.com at 12.4 s12.4 s

Speed

11 to fix52
  • Use efficient cache lifetimes

    6.5 s · 5.3 MB

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

  • Improve image delivery

    3.0 s · 1.8 MB

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

  • Render-blocking requests

    3.5 s

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

  • Font display

    2.2 s

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

  • Reduce unused JavaScript

    1.6 s · 195 KiB

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

  • Reduce unused CSS

    1.1 s · 139 KiB

    About 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • 7,061 HTML elements

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

  • Main-thread work: 5.7 s

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • 13 long tasks on the main thread

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

  • Minify CSS

    300 ms · 29 KiB

    29 KiB could be saved by minifying CSS.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Cloudflare CDN and others), adding 339 KiB and 135 ms of main-thread time.

  • Minify JavaScript

    150 ms · 3 KiB

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

1 checks passed
  • Server response: 504 ms

    504 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

    Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SBICAPS is proud to have acted as a left lead bank in succe…”. Most of its time is element render delay (12.8 s).

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 21.3 s

    21.3 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

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

    +29%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 326 ms

    326 ms

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

  • 19 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user INP: 185 ms

    185 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

3 to fix40
  • Page weight: 6.2 MB in 160 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 160 requests on a phone: images 4.2 MB (94), media 831 KiB (2) and scripts 557 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    991 KiB

    9 images are downloaded at several times the size a phone draws them, for example 1765966433173.jpg at 800 px wide, shown at 99 px. Resized copies would save about 991 KiB.

  • 10 images in older formats

    10 images (1.2 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 (118 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.75 g

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

Accessibility

6 to fixGoogle 8191
  • 5 tap targets too small

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

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

  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

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

    All page content should be contained by landmarks: 23 elements on the page fail 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.

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (1 element).

2 checks passed
  • Every image has alt text

    All 268 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 8581
  • 142 links with vague text

    142 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “SBI Capital Markets Limited | India's Leading Bank and Project Advisor”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Powering Ambition Through Innovation” and “Powering Ambition”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 261 internal links, 4 external

    The homepage links to 261 pages on sbicaps.com and 4 external pages.

5 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “India's premier investment bank with expertise in project advisory and structured finance, capital markets and merchant…”.

  • Canonical URL set

    The canonical URL is https://www.sbicaps.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.sbicaps.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.sbicaps.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 (10,453 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.sbicaps.com/expertises/debt-capital-markets, https://www.sbicaps.com/mandates-listing, https://www.sbicaps.com/latest-updates, https://www.sbicaps.com/research-reports, https://www.sbicaps.com/accolades and https://www.sbicaps.com/career-positions have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.sbicaps.com/expertises/project-advisory-structured-finance, https://www.sbicaps.com/expertises/equity-capital-markets and https://www.sbicaps.com/expertises/debt-capital-markets have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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://www.sbicaps.com/.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.google.com/recaptcha/api.js' violates the following Content Security Policy directive: …”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    155 of 158 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 5,544 words of copy

    The homepage carries about 5,544 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Join Us”, “Subscribe” and “Contact us”.

  • 6 short forms

    6 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, 7 customer or partner logos, 9 trust badges and “over 3,000 clients”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 sbicaps.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Web Werks India Pvt. Ltd.

Hiring

Hiring
8 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on sbicaps.com, including 22 speed issues and 5 SEO issues. 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