unibank.az website review

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

About 269 KiB of JavaScript is downloaded but never used on this page.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Yandex Metrica and others), adding 653 KiB and 398 ms of main-thread time.

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

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

66 KiB could be saved by minifying JavaScript.

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

About 48 KiB of CSS is downloaded but never applied on this page.

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

8 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.3 s to 1.3 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.38 g of CO₂e: 45.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

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

The homepage links to 100 pages on unibank.az and 30 external pages.

There is no https://unibank.az/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.

https://unibank.az/az and https://unibank.az/az/corporate/index all use the title “Unibank - Sənin Bankın | Bank Xidmətləri ✅”. Search engines can't tell which page to show for a search, so each competes with the others.

https://unibank.az/az/corporate/index, https://unibank.az/az/sustain/index, https://unibank.az/az/documents/tariffs/62 and https://unibank.az/az/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://unibank.az/az/corporate/index, https://unibank.az/az/sustain/index, https://unibank.az/az/documents/tariffs/62, https://unibank.az/en and https://unibank.az/ru have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 359 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Yandex Metrica (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 7 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.