Website review, no card needed

anbinvest.com.sa logo

anbinvest.com.sa website review

Visit site (opens in a new tab)Reviewed 21 October 202650 issues · 85 checks

This review found 50 issues worth fixing on anbinvest.com.sa, 23 of them high impact, across 85 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.6 s2.7 sMay 2Oct 175.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.5 s
May 9, 20263.6 s
May 16, 20263.5 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.3 s
Jul 11, 20263.5 s
Jul 18, 20263.8 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20264.3 s
Sep 5, 20264.7 s
Sep 12, 20264.5 s
Sep 19, 20265.3 s
Sep 26, 20265.0 s
Oct 3, 20264.9 s
Oct 10, 20265.0 s
Oct 17, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
209 ms112 msMay 2Oct 17151 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026154 ms
May 9, 2026163 ms
May 16, 2026198 ms
May 23, 2026171 ms
May 30, 2026164 ms
Jun 6, 2026158 ms
Jun 13, 2026152 ms
Jun 20, 2026148 ms
Jun 27, 2026148 ms
Jul 4, 2026137 ms
Jul 11, 2026137 ms
Jul 18, 2026152 ms
Jul 25, 2026131 ms
Aug 1, 2026140 ms
Aug 8, 2026136 ms
Aug 15, 2026130 ms
Aug 22, 2026126 ms
Aug 29, 2026128 ms
Sep 5, 2026123 ms
Sep 12, 2026128 ms
Sep 19, 2026146 ms
Sep 26, 2026137 ms
Oct 3, 2026151 ms
Oct 10, 2026146 ms
Oct 17, 2026151 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 anbinvest.com.sa (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix41
  • Render-blocking requests

    7.2 s

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

  • Reduce unused JavaScript

    4.6 s · 1.3 MB

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

  • Use efficient cache lifetimes

    2.6 s · 968 KiB

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

  • Font display

    1.9 s

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

  • Reduce unused CSS

    1.2 s · 241 KiB

    About 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Minify JavaScript

    1.1 s · 381 KiB

    381 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 41

    41/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Analytics and others), adding 1.2 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 921 ms

    921 ms

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

  • Main-thread work: 3.0 s

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

  • Improve image delivery

    150 ms · 239 KiB

    5 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Minify CSS

    150 ms · 43 KiB

    43 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    14 KiB

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

1 checks passed
  • Server response: 207 ms

    207 ms

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

Core Web Vitals

11 to fix50
  • 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: 5.7 s

    5.7 s

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

  • Real-user FCP: 4.9 s

    4.9 s

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

  • Largest Contentful Paint: 17.5 s

    17.5 s

    Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Download the App Securities Brokerage Wealth Management Ass…”.

  • Time to Interactive: 28.6 s

    28.6 s

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

  • Speed Index: 13.9 s

    13.9 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Largest content (LCP) got 43% slower for real visitors

    +43%

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 569 ms

    569 ms

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 154 ms to 151 ms 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

    0

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

Images and page weight

2 to fix63
  • Page weight: 6.6 MB in 100 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 100 requests on a phone: images 2.8 MB (19), scripts 2.5 MB (48) and other files 819 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

    8 images further down the page (359 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images in older formats

    6 images (309 KiB) 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.

  • About 1.9 g of CO₂ per visit

    1.86 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

7 to fixGoogle 7388
  • Invalid ARIA attributes

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

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 17 text elements with low contrast

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

  • 10 images without alt text

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

9 to fixGoogle 6262
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (25 characters)

    Your title is only 25 characters: “Landing Page - anbcapital”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Canonical points to another host

    Your canonical URL points to anb.com.sa, not anbcapital.com.sa, so Google may credit that host instead.

  • No structured data

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

  • No social preview image

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

  • No XML sitemap

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

  • No robots.txt

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

  • 5 links crawlers can't follow

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

  • 3 links with vague text

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

  • No X (Twitter) card tag

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

  • 54 internal links, 6 external

    The homepage links to 54 pages on anbinvest.com.sa and 6 external pages.

1 checks passed
  • One H1 headline

    Your main headline reads: “Navigation”.

AI search readiness

1 to fix81
  • 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://anbcapital.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.

1 checks passed
  • Text is in the HTML

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

Other pages

5 to fix43
  • 1 linked page is broken

    Your homepage links to https://anbcapital.com.sa/c/portal/update_language, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://anbcapital.com.sa/c/portal/layout has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://anbcapital.com.sa/web/anbcapital/about-us and https://anbcapital.com.sa/web/anbcapital/our-awards all use the title “About us - anbcapital”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://anbcapital.com.sa/web/anbcapital/about-us, https://anbcapital.com.sa/c/portal/layout, https://anbcapital.com.sa/web/anbcapital/our-awards, https://anbcapital.com.sa/web/anbcapital/corporate-disclosures, https://anbcapital.com.sa/web/anbcapital/securities-brokerage and https://anbcapital.com.sa/web/anbcapital/asset-management and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://anbcapital.com.sa/c/portal/layout has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://anbcapital.com.sa/c/portal/layout 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.

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

  • 2 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • No direct contact details

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

  • 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 592 words of copy

    The homepage carries about 592 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: “Download the App”.

  • 1 call to action

    The homepage has 1 call to action, for example “Download the App”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 11 cookies set on arrival

    11

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 anbinvest.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on anbinvest.com.sa, including 21 speed issues, 9 SEO issues and 2 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