sabb.com website review

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

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

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

13 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

About 298 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

49 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 12 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

Your largest element takes 5.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 (2.4 s).

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

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

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

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

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

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-31, real Chrome visitors' tap response (inp) went from 116 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.7 MB in 91 requests on a phone: images 3.8 MB (61), scripts 479 KiB (11) and fonts 192 KiB (5). Under 2 MB keeps phones on slow connections fast.

11 images (2.6 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.

7 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Banner 1872 x 800 Pixels.jpg at 1,872 px wide, shown at 390 px. Resized copies would save about 277 KiB.

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

1 element hidden from screen readers can still receive keyboard focus.

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.

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

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

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

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

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

No XML sitemap at https://www.sab.com/sitemap.xml, so Google discovers your pages only by following links.

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

10 links have no real href, so search engines can't follow them.

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

The homepage links to 554 pages on sabb.com and 31 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.sab.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.

https://www.sab.com/en/personal/compare-credit-cards, https://www.sab.com/en/personal/compare-credit-cards/miles-credit-cards and https://www.sab.com/en/personal/compare-credit-cards/icsab-credit-cards all use the title “Compare SAB Credit Cards Cards | Personal | SAB”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.sab.com/ar/personal, https://www.sab.com/en/personal/payments-and-transfers/sab-global-view-and-global-transfer, https://www.sab.com/en/personal/segments, https://www.sab.com/en/personal/segments/sab-premier, https://www.sab.com/en/personal/segments/sab-advance and https://www.sab.com/en/personal/segments/general-banking-account and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sab.com/en/personal/compare-credit-cards, https://www.sab.com/en/personal/compare-credit-cards/miles-credit-cards and https://www.sab.com/en/personal/compare-credit-cards/icsab-credit-cards use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.sab.com/en/personal/compare-credit-cards/miles-credit-cards, whose canonical is https://www.sab.com/en/personal/compare-credit-cards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sab.com/ar/personal, https://www.sab.com/en/personal/segments, https://www.sab.com/en/personal/segments/sab-premier, https://www.sab.com/en/personal/segments/sab-advance, https://www.sab.com/en/personal/segments/general-banking-account and https://www.sab.com/en/personal/segments/international-banking and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sab.com/ar/personal 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.

https://www.sab.com/ar/personal, https://www.sab.com/en/personal/payments-and-transfers/sab-global-view-and-global-transfer, https://www.sab.com/en/personal/segments, https://www.sab.com/en/personal/segments/sab-premier, https://www.sab.com/en/personal/segments/sab-advance and https://www.sab.com/en/personal/segments/general-banking-account and 3 others took over 3 s to send their HTML from our server.

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

6 images failed to load on a phone, for example https://www.sab.com/en/personal/Prices%20of%20Financing%20&%20Saving%20Products.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Large scripts ship without source maps.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 879 words of visible text.

Opening the homepage sets 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.