uab.ae website review

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

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

The HTML itself could arrive about 1.4 s sooner: redirects, a slow server response or missing compression delay everything after it.

6 images could be 669 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

Reduce initial server response time. Google estimates savings of 1.5 s on a phone.

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

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

Google CDN costs a phone 710 ms of main-thread work and 1.1 MB 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.

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

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

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

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

Your server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

33 KiB could be saved by minifying JavaScript.

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

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

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

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.

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

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

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

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

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

The layout shifts by 0.469 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 7.3 MB in 89 requests on a phone: images 3.2 MB (29), scripts 2.1 MB (24) and fonts 821 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

[role]s are not contained by their required parent element (3 elements).

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

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

2 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields do not have accessible names (1 element).

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

Your title is 80 characters, so Google will cut it off around 60: “Personal Banking | Corporate Banking | Islamic Banking in UAE | United Arab Bank”.

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

There are 10 <h1> headlines (“WIN A CAR”, “100% CASHBACK ON YOUR INTERNATIONAL TRANSFER FEES” and “A current account that earns you money!”). One clear main headline is easier for people and search engines.

Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 421 pages on uab.ae and 14 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://www.uab.ae/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://www.uab.ae/en/personal/cards/credit-cards/platinum-card and https://www.uab.ae/en/personal/cards/credit-cards/titanium-card took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).

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

Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

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

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 1,863 words of visible text.