Website review, no card needed

aljazirabank.com.sa logo

aljazirabank.com.sa website review

Visit site (opens in a new tab)Reviewed 24 October 202661 issues · 95 checks

This review found 61 issues worth fixing on aljazirabank.com.sa, 27 of them high impact, across 95 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
5.7 s3.9 sMay 2Oct 174.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.7 s
May 9, 20264.9 s
May 16, 20265.0 s
May 23, 20265.0 s
May 30, 20265.1 s
Jun 6, 20264.9 s
Jun 13, 20264.6 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20264.4 s
Aug 8, 20264.8 s
Aug 15, 20265.2 s
Aug 22, 20265.5 s
Aug 29, 20265.4 s
Sep 5, 20264.9 s
Sep 12, 20264.8 s
Sep 19, 20264.6 s
Sep 26, 20264.4 s
Oct 3, 20264.9 s
Oct 10, 20264.6 s
Oct 17, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
199 ms167 msMay 2Oct 17194 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026183 ms
May 9, 2026180 ms
May 16, 2026177 ms
May 23, 2026177 ms
May 30, 2026182 ms
Jun 6, 2026182 ms
Jun 13, 2026180 ms
Jun 20, 2026178 ms
Jun 27, 2026172 ms
Jul 4, 2026173 ms
Jul 11, 2026176 ms
Jul 18, 2026177 ms
Jul 25, 2026175 ms
Aug 1, 2026171 ms
Aug 8, 2026175 ms
Aug 15, 2026181 ms
Aug 22, 2026189 ms
Aug 29, 2026192 ms
Sep 5, 2026186 ms
Sep 12, 2026186 ms
Sep 19, 2026185 ms
Sep 26, 2026184 ms
Oct 3, 2026195 ms
Oct 10, 2026194 ms
Oct 17, 2026194 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

Full-page screenshot of aljazirabank.com.sa (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aljazirabank.com.sa at 1.0 s1.0 s
  2. aljazirabank.com.sa at 2.0 s2.0 s
  3. aljazirabank.com.sa at 3.0 s3.0 s
  4. aljazirabank.com.sa at 4.0 s4.0 s
  5. aljazirabank.com.sa at 5.0 s5.0 s
  6. aljazirabank.com.sa at 6.0 s6.0 s
  7. aljazirabank.com.sa at 7.0 s7.0 s
  8. aljazirabank.com.sa at 8.0 s8.0 s

Speed

18 to fix33
  • Render-blocking requests

    8.2 s

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

  • Reduce unused JavaScript

    4.5 s · 1.7 MB

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

  • Minify JavaScript

    1.4 s · 237 KiB

    237 KiB could be saved by minifying JavaScript.

  • Font display

    1.4 s

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

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 9.7 s

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

  • 3,614 HTML elements

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

  • Improve image delivery

    4.1 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and JSDelivr CDN and others), adding 2.7 MB and 2.3 s of main-thread time.

  • Google Tag Manager adds 889 ms

    889 ms

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

  • Document request latency

    750 ms · 188 KiB

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

  • Use efficient cache lifetimes

    400 ms · 365 KiB

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

  • Google CDN adds 637 ms

    637 ms

    Google CDN costs a phone 637 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.

  • Reduce initial server response time

    740 ms

    Reduce initial server response time. Google estimates savings of 740 ms on a phone.

  • Legacy JavaScript

    500 ms · 53 KiB

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

  • Reduce unused CSS

    450 ms · 66 KiB

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

  • 20 long tasks on the main thread

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

  • Server response: 840 ms

    840 ms

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

  • Minify CSS

    90 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

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

Core Web Vitals

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

  • Real-user LCP: 4.2 s

    4.2 s

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

  • Real-user FCP: 3.6 s

    3.6 s

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

  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “شريكك في النمو المالي”. Most of its time is element render delay (5.8 s).

  • Speed Index: 18.2 s

    18.2 s

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

  • Time to Interactive: 53.4 s

    53.4 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Real-user INP: 204 ms

    204 ms

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 21 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

5 to fix18
  • Page weight: 11.8 MB in 208 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 208 requests on a phone: images 6.4 MB (57), scripts 3.4 MB (56) and other files 1.1 MB (56). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    2.1 MB

    10 images are downloaded at several times the size a phone draws them, for example card-private.png at 2,560 px wide, shown at 342 px. Resized copies would save about 2.1 MB.

  • 23 images in older formats

    23 images (5.3 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.

  • 22 images below the first screen load straight away

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

  • About 3.4 g of CO₂ per visit

    3.36 g

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

Accessibility

9 to fixGoogle 8087
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 3 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 5 images without alt text

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (88 elements)

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

  • 27 form fields without a label

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

  • 17 links without text

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

6 to fixGoogle 9273
  • Title is short (7 characters)

    Your title is only 7 characters: “الأفراد”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

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

  • Meta description is long (215 characters)

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

  • Structured data has 1 problem

    Structured data found (BankOrCreditUnion, FAQPage and Service) but with 1 problem, for example “Service: no offers (price) block”.

  • No social preview image

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

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 129 internal links, 49 external

    The homepage links to 129 pages on aljazirabank.com.sa and 49 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “شريكك في النمو المالي”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    38%

    The HTML your server sends has 74 of the 195 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • llms.txt published

    The site publishes https://www.aljazirabank.com.sa/llms.txt (28 KiB, 175 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 14 pages with very little text

    https://www.aljazirabank.com.sa/ar-sa/Business, https://www.aljazirabank.com.sa/ar-sa/Bank, https://www.aljazirabank.com.sa/ar-sa/personal/programs-ar-SA, https://www.aljazirabank.com.sa/ar-sa/personal/credit-cards-ar-SA, https://www.aljazirabank.com.sa/ar-sa/personal/finances-ar-SA and https://www.aljazirabank.com.sa/ar-sa/personal/promotional-offers and 8 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.

  • 2 pages slow to respond

    https://www.aljazirabank.com.sa/ar-sa/personal/programs-ar-SA and https://www.aljazirabank.com.sa/ar-sa/personal/finances-ar-SA took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 4281
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “twq is not defined”.

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • 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 195 words

    The homepage has only about 195 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 (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 27 cookies set on arrival

    27

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

  • 35 other companies contacted

    Loading the homepage contacts 35 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 aljazirabank.com.sa, 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 Analytics | Google Tag Manager

Company

Founded
1975

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on aljazirabank.com.sa, including 29 speed issues, 6 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