vtb.ge website review

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

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

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

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

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

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

Google Tag Manager costs a phone 321 ms of main-thread work and 297 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.

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

4 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 414 KiB and 449 ms of main-thread time.

1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

15 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (5.6 s).

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

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

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

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

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Some list items are not inside a list.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 15 characters: “Assets For Sale”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 15 characters: “Assets for sale”. 70 to 160 characters is enough to sell the click.

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

No XML sitemap at https://vtb.ge/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at vtb.ge/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 35 pages on vtb.ge and 6 external pages.

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.

There is no https://vtb.ge/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.

Your homepage links to https://vtb.ge/ge/individuals/exchange-rates and https://vtb.ge/ge/ethics, which answer with an error. Visitors hit a dead end and search engines drop them.

https://vtb.ge/ge/assets-for-sale and https://vtb.ge/ge/individuals all use the title “Assets For Sale”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://vtb.ge/ge/individuals/agreements, https://vtb.ge/ge/business, https://vtb.ge/ge/business/agreements, https://vtb.ge/ge/about-the-bank, https://vtb.ge/ge/about-the-bank/financial-reporting and https://vtb.ge/ge/about-the-bank/public-information have no meta description, so Google writes the search snippet from whatever text it finds.

https://vtb.ge/ge/business and https://vtb.ge/ge/about-the-bank have no <h1> headline, so visitors and search engines get no clear main topic.

https://vtb.ge/ge/individuals, https://vtb.ge/ge/individuals/agreements, https://vtb.ge/ge/business, https://vtb.ge/ge/business/agreements, https://vtb.ge/ge/about-the-bank and https://vtb.ge/ge/about-the-bank/financial-reporting and 2 others have 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.

https://vtb.ge/ge/individuals/agreements, https://vtb.ge/ge/business, https://vtb.ge/ge/business/agreements, https://vtb.ge/ge/about-the-bank/financial-reporting, https://vtb.ge/ge/about-the-bank/public-information and https://vtb.ge/ge/about-the-bank/bank-details took over 3 s to send their HTML from our server.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.