Website review, no card needed

abana.com.sa logo

abana.com.sa website review

Visit site (opens in a new tab)Reviewed 20 October 202624 issues · 75 checks

This review found 24 issues worth fixing on abana.com.sa, 5 of them high impact, across 75 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
3.0 s1.7 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.3 s
May 23, 20262.1 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
123 ms91 msMay 2Oct 1799 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026115 ms
May 9, 2026107 ms
May 16, 2026106 ms
May 23, 2026108 ms
May 30, 2026106 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026117 ms
Jun 27, 2026119 ms
Jul 4, 2026104 ms
Jul 11, 2026103 ms
Jul 18, 2026104 ms
Jul 25, 2026107 ms
Aug 1, 2026108 ms
Aug 8, 2026110 ms
Aug 15, 2026108 ms
Aug 22, 2026108 ms
Aug 29, 2026116 ms
Sep 5, 2026112 ms
Sep 12, 2026111 ms
Sep 19, 2026103 ms
Sep 26, 202697 ms
Oct 3, 202695 ms
Oct 10, 202697 ms
Oct 17, 202699 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 abana.com.sa (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abana.com.sa at 1.5 s1.5 s
  2. abana.com.sa at 2.9 s2.9 s
  3. abana.com.sa at 4.4 s4.4 s
  4. abana.com.sa at 5.9 s5.9 s
  5. abana.com.sa at 7.3 s7.3 s
  6. abana.com.sa at 8.8 s8.8 s
  7. abana.com.sa at 10.3 s10.3 s
  8. abana.com.sa at 11.7 s11.7 s

Speed

3 to fix66
  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 72 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 167 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    32 KiB

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

  • Improve image delivery

    32 KiB

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

  • Legacy JavaScript

    11 KiB

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

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

  • Forced reflow

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 683 ms of it running JavaScript. That is comfortably low.

  • Server response: 514 ms

    514 ms

    Your server sent the HTML in 514 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Speed Index: 11.5 s

    11.5 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Time to Interactive: 6.0 s

    6.0 s

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 99 ms

    99 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Total Blocking Time: 195 ms

    195 ms

    Scripts block the page for only 195 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.015

    0.015

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.2 g of CO₂ per visit

    0.23 g

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

3 checks passed
  • Page weight: 813 KiB in 37 requests

    813 KiB

    Your homepage downloads 813 KiB in 37 requests on a phone: scripts 362 KiB (17), fonts 245 KiB (2) and images 163 KiB (10). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9495
  • 15 text elements with low contrast

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

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 80 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

7 to fixGoogle 9170
  • Title is short (5 characters)

    Your title is only 5 characters: “Abana”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (60 characters)

    Your meta description is only 60 characters: “Your Strategic Technology Partner for Digital Transformation”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

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

  • No XML sitemap

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

  • No robots.txt

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

  • 4 links with vague text

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

  • 77 internal links, 12 external

    The homepage links to 77 pages on abana.com.sa and 12 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “About ABANA”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.abana.com.sa/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (582 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://www.abana.com.sa/en/careers, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 10 pages share a title

    https://www.abana.com.sa/en, https://www.abana.com.sa/en/solution/network-and-infrastructure-solutions, https://www.abana.com.sa/en/solution/technical-expertise-and-consulting-services, https://www.abana.com.sa/en/solution/visual-and-audio-solutions, https://www.abana.com.sa/en/solution/self-service-kiosk and https://www.abana.com.sa/en/solution/banking-solutions and 4 others all use the title “Abana”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://www.abana.com.sa/en/about, https://www.abana.com.sa/en/solution, https://www.abana.com.sa/en/sectors, https://www.abana.com.sa/en/media, https://www.abana.com.sa/en/contact and https://www.abana.com.sa/en/solution/network-and-infrastructure-solutions and 8 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://www.abana.com.sa/en/sectors, https://www.abana.com.sa/en/media and https://www.abana.com.sa/en/contact took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418 for the full message or use the non-minified dev environm…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

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

  • About 483 words of copy

    The homepage carries about 483 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Download ABANA Profile”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Us”, “Download ABANA Profile” and “Get in touch to sustain your success”.

  • Social proof on the page

    Social proof on the homepage: 3 trust badges and “0+ satisfied clients”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 3 cookies set on arrival

    3

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 abana.com.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on abana.com.sa, including 6 speed issues and 7 SEO issues. 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