Programmable

Website review, no card needed

vib.com.vn logo

vib.com.vn website review

Visit site (opens in a new tab)Reviewed 28 October 202646 issues · 90 checks

This review found 46 issues worth fixing on vib.com.vn, 19 of them high impact, across 90 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

Site score

65D

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.6 s1.7 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.2 s
Jul 11, 20262.0 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
405 ms293 msMay 9Oct 24367 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026325 ms
May 16, 2026343 ms
May 23, 2026359 ms
May 30, 2026371 ms
Jun 6, 2026384 ms
Jun 13, 2026392 ms
Jun 20, 2026391 ms
Jun 27, 2026378 ms
Jul 4, 2026361 ms
Jul 11, 2026340 ms
Jul 18, 2026324 ms
Jul 25, 2026319 ms
Aug 1, 2026314 ms
Aug 8, 2026314 ms
Aug 15, 2026312 ms
Aug 22, 2026306 ms
Aug 29, 2026318 ms
Sep 5, 2026337 ms
Sep 12, 2026344 ms
Sep 19, 2026348 ms
Sep 26, 2026346 ms
Oct 3, 2026334 ms
Oct 10, 2026335 ms
Oct 17, 2026353 ms
Oct 24, 2026367 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

www.vib.com.vn (opens in a new tab)
Full-page screenshot of vib.com.vn (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vib.com.vn at 1.5 s1.5 s
  2. vib.com.vn at 2.9 s2.9 s
  3. vib.com.vn at 4.4 s4.4 s
  4. vib.com.vn at 5.8 s5.8 s
  5. vib.com.vn at 7.3 s7.3 s
  6. vib.com.vn at 8.7 s8.7 s
  7. vib.com.vn at 10.2 s10.2 s
  8. vib.com.vn at 11.6 s11.6 s

Speed

10 to fix38

  • Use efficient cache lifetimes

    3.6 s · 764 KiB

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

  • Reduce unused JavaScript

    2.7 s · 685 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

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

    38/100

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

  • Main-thread work: 6.4 s

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

  • 8 third-party services on the page

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

  • Legacy JavaScript

    900 ms · 51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 900 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 127 KiB

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

  • 14 long tasks on the main thread

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

  • Improve image delivery

    12 KiB

    2 images could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 100 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    32 ms

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

Core Web Vitals

9 to fix33

  • 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: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 16.3 s

    16.3 s

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

  • Time to Interactive: 21.0 s

    21.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 261 ms

    261 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 618 ms

    618 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix85

  • Page weight: 3.3 MB in 219 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 219 requests on a phone: scripts 2.2 MB (84), images 379 KiB (65) and fonts 365 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

12 to fixGoogle 7383

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 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.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 12 links without text

    12 visible links have no text or label, so screen readers cannot say where they go.

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

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

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed

  • 35 automated accessibility rules passed

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

SEO

3 to fixGoogle 8590

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

  • 8 links crawlers can't follow

    8 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 set, so this is minor.

  • 79 internal links, 8 external

    The homepage links to 79 pages on vib.com.vn and 8 external pages.

6 checks passed

  • Meta description: 136 characters

    Your meta description is 136 characters: “VIB - Ngân hàng dẫn đầu xu thế với công nghệ tiên tiến, dịch vụ đa dạng, và nhiều ưu đãi hấp dẫn, đáp ứng mọi nhu cầu t…”.

  • One H1 headline

    Your main headline reads: “Tận hưởng ưu đãi độc quyền từ sản phẩm & dịch vụ tài chính VIB”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Ngân hàng Quốc Tế VIB - Trang dành riêng khách hàng cá nhân | VIB”.

  • 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.vib.com.vn/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.vib.com.vn/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 (621 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75

  • 1 page without a title

    https://www.vib.com.vn/vn/promotion/detail has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.vib.com.vn/vn/promotion/detail has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.vib.com.vn/vn/tiet-kiem, https://www.vib.com.vn/vn/tai-khoan, https://www.vib.com.vn/vn/nguon-von-va-ngoai-hoi, https://www.vib.com.vn/vn/promotion and https://www.vib.com.vn/vn/promotion/detail have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.vib.com.vn/vn/promotion has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 pages slow to respond

    https://www.vib.com.vn/vn/ngan-hang-so/myvib, https://www.vib.com.vn/vn/vay-tieu-dung, https://www.vib.com.vn/vn/cho-vay-mua-nha, https://www.vib.com.vn/vn/vay-mua-xe and https://www.vib.com.vn/vn/bao-hiem took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 42 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.

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

Best practices

2 to fixGoogle 9687

  • 7 small tap targets

    7 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'WindowUtils')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

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

  • Only about 208 words

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

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

3 checks passed

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 21 cookies set on arrival

    21

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

  • 24 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Vietnam Internationl commercial joint stock bank

Company

Founded
1996
Headquarters
Ho Chi Minh City

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on vib.com.vn, including 19 speed issues, 3 SEO issues and 4 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