Website review, no card needed

albawani.com logo

albawani.com website review

Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 72 checks

This review found 31 issues worth fixing on albawani.com, 13 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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

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

How it loaded on a phone

  1. albawani.com at 1.1 s1.1 s
  2. albawani.com at 2.1 s2.1 s
  3. albawani.com at 3.2 s3.2 s
  4. albawani.com at 4.3 s4.3 s
  5. albawani.com at 5.3 s5.3 s
  6. albawani.com at 6.4 s6.4 s
  7. albawani.com at 7.5 s7.5 s
  8. albawani.com at 8.6 s8.6 s

Speed

7 to fix55
  • Use efficient cache lifetimes

    8.9 s · 2.6 MB

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

  • Render-blocking requests

    7.0 s

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

  • Reduce unused CSS

    3.3 s · 559 KiB

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

  • Reduce unused JavaScript

    2.4 s · 443 KiB

    About 443 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Font display

    650 ms

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

  • Improve image delivery

    597 KiB

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

  • Minify JavaScript

    150 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Document request latency

    122 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

  • Phones get a much slower page than desktops

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 82 KiB and 0 ms of main-thread time.

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

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

  • Server response: 349 ms

    349 ms

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

Core Web Vitals

4 to fix67
  • First Contentful Paint: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 14.1 s

    14.1 s

    Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”. Most of its time is element render delay (8.0 s).

  • Speed Index: 15.7 s

    15.7 s

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

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.009

    0.009

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

1 to fix70
  • Page weight: 16.4 MB in 65 requests

    16.4 MB

    Your homepage downloads 16.4 MB in 65 requests on a phone: media 13.5 MB (1), images 944 KiB (6) and scripts 894 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • About 4.7 g of CO₂ per visit

    4.65 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 8998
  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

8 to fixGoogle 6139
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (17 characters)

    Your title is only 17 characters: “Al Bawani Holding”. 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.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Pioneers in Transforming Industries”, “Pioneers in Transforming Industries” and “Pioneers in Transforming Industries”). One clear main headline is easier for people and search engines.

  • 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://albawani.com/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.

  • 51 internal links, 12 external

    The homepage links to 51 pages on albawani.com and 12 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://albawani.com/en/.

  • robots.txt in place

    robots.txt is in place.

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://albawani.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.

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.

  • Text is in the HTML

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

Other pages

3 to fix80
  • 15 linked pages hidden from search

    https://albawani.com/ar, https://albawani.com/projects, https://albawani.com/en/project-type/featured, https://albawani.com/en/project-type/sports-entertainment, https://albawani.com/en/project-type/cultural and https://albawani.com/en/project-type/healthcare and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://albawani.com/en and https://albawani.com/ar all use the title “Al Bawani Holding”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://albawani.com/ar, https://albawani.com/projects, https://albawani.com/en/project-type/featured, https://albawani.com/en/project-type/sports-entertainment, https://albawani.com/en/project-type/cultural and https://albawani.com/en/project-type/healthcare and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

4 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 an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 614 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 albawani.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on albawani.com, including 11 speed issues, 8 SEO issues and 3 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