Website review, no card needed

almana.com.sa logo

almana.com.sa website review

Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 85 checks

This review found 42 issues worth fixing on almana.com.sa, 12 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
4.0 s3.2 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.7 s
Jul 18, 20263.4 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.5 s
Aug 15, 20263.7 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.8 s
Sep 19, 20263.6 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.5 s
Oct 24, 20263.4 s
Oct 31, 20263.5 s
Nov 7, 20263.6 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
158 ms100 msMay 30Nov 14115 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026119 ms
Jun 6, 2026122 ms
Jun 13, 2026127 ms
Jun 20, 2026133 ms
Jun 27, 2026135 ms
Jul 4, 2026151 ms
Jul 11, 2026148 ms
Jul 18, 2026131 ms
Jul 25, 2026130 ms
Aug 1, 2026125 ms
Aug 8, 2026129 ms
Aug 15, 2026133 ms
Aug 22, 2026130 ms
Aug 29, 2026127 ms
Sep 5, 2026125 ms
Sep 12, 2026122 ms
Sep 19, 2026122 ms
Sep 26, 2026118 ms
Oct 3, 2026113 ms
Oct 10, 2026109 ms
Oct 17, 2026107 ms
Oct 24, 2026108 ms
Oct 31, 2026108 ms
Nov 7, 2026112 ms
Nov 14, 2026115 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 almana.com.sa (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. almana.com.sa at 0.9 s0.9 s
  2. almana.com.sa at 1.8 s1.8 s
  3. almana.com.sa at 2.8 s2.8 s
  4. almana.com.sa at 3.7 s3.7 s
  5. almana.com.sa at 4.6 s4.6 s
  6. almana.com.sa at 5.5 s5.5 s
  7. almana.com.sa at 6.4 s6.4 s
  8. almana.com.sa at 7.3 s7.3 s

Speed

8 to fix61
  • Use efficient cache lifetimes

    3.1 s · 1.4 MB

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

  • Improve image delivery

    2.4 s · 1.7 MB

    15 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.5 s · 287 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Reduce unused CSS

    640 ms · 130 KiB

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

  • Google Tag Manager adds 357 ms

    357 ms

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

  • Main-thread work: 2.1 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 513 KiB and 360 ms of main-thread time.

  • Minify CSS

    150 ms · 28 KiB

    28 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Font display

    100 ms

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

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix67
  • 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 FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 15.1 s

    15.1 s

    Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 15.4 s

    15.4 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 33 images without width and height

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

4 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 169 ms

    169 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

3 to fix68
  • Page weight: 3.9 MB in 72 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 72 requests on a phone: images 2.9 MB (26), scripts 716 KiB (15) and stylesheets 187 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.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.

  • 8 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.3 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

8 to fixGoogle 7186
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 2 text elements with low contrast

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

5 to fixGoogle 7585
  • No structured data

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

  • 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.almana.com.sa/sitemap.xml, so Google discovers your pages only by following links.

  • 18 links crawlers can't follow

    18 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 set, so this is minor.

  • 49 internal links, 9 external

    The homepage links to 49 pages on almana.com.sa and 9 external pages.

5 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Ebrahim Almana & Brothers Co. is the largest medical company & health care provider with over six decades of existence.”.

  • One H1 headline

    Your main headline reads: “Advancing Kingdom’s Healthcare Sector”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Almana | Kingdom of Saudi Arabia”.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

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

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

Other pages

2 to fix93
  • 11 pages share a meta description

    https://www.almana.com.sa/en/category/overview, https://www.almana.com.sa/en/category/our-culture, https://www.almana.com.sa/en/category/strategic-goals, https://www.almana.com.sa/en/category/gms-message, https://www.almana.com.sa/en/category/group-structure and https://www.almana.com.sa/en/category/products-and-solutions and 5 others use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://www.almana.com.sa/en/category/overview, https://www.almana.com.sa/en/category/our-culture, https://www.almana.com.sa/en/category/strategic-goals, https://www.almana.com.sa/en/category/gms-message, https://www.almana.com.sa/en/category/group-structure and https://www.almana.com.sa/en/category/products-and-solutions and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://www.almana.com.sa/en/category/strategic-goals, https://www.almana.com.sa/en/category/gms-message, https://www.almana.com.sa/en/category/group-structure, https://www.almana.com.sa/en/category/products-and-solutions, https://www.almana.com.sa/en/category/hospital-beds and https://www.almana.com.sa/en/category/dental and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 10 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 144 words

    The homepage has only about 144 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 almana.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 42 issues on almana.com.sa, including 17 speed issues, 5 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