Website review, no card needed
alsalamahospital.com website review
Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 90 checks
This review found 40 issues worth fixing on alsalamahospital.com, 17 of them high impact, across 90 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71C- #101,370 of 125,940 reviewed websitesbeats 17%
- #61,571 of 70,311 online storesbeats 10%
- #2,126 of 2,956 WooCommerce storesbeats 24%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.5 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.7 s |
| Aug 1, 2026 | 5.9 s |
| Aug 8, 2026 | 6.1 s |
| Aug 15, 2026 | 6.1 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.2 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.2 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 5.9 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.4 s |
| Oct 24, 2026 | 6.4 s |
| Oct 31, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 234 ms |
| May 23, 2026 | 235 ms |
| May 30, 2026 | 247 ms |
| Jun 6, 2026 | 262 ms |
| Jun 13, 2026 | 264 ms |
| Jun 20, 2026 | 260 ms |
| Jun 27, 2026 | 253 ms |
| Jul 4, 2026 | 265 ms |
| Jul 11, 2026 | 271 ms |
| Jul 18, 2026 | 293 ms |
| Jul 25, 2026 | 292 ms |
| Aug 1, 2026 | 289 ms |
| Aug 8, 2026 | 293 ms |
| Aug 15, 2026 | 271 ms |
| Aug 22, 2026 | 273 ms |
| Aug 29, 2026 | 256 ms |
| Sep 5, 2026 | 253 ms |
| Sep 12, 2026 | 268 ms |
| Sep 19, 2026 | 265 ms |
| Sep 26, 2026 | 261 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 276 ms |
| Oct 17, 2026 | 269 ms |
| Oct 24, 2026 | 266 ms |
| Oct 31, 2026 | 248 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
How it loaded on a phone
1.4 s
2.7 s
4.1 s
5.5 s
6.9 s
8.2 s
9.6 s
11.0 s
Speed
Render-blocking requests
4.2 s37 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Font display
2.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.0 s).
Reduce unused JavaScript
1.2 s · 579 KiBAbout 579 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1,015 KiB and 1.1 s of main-thread time.
Reduce initial server response time
752 msReduce initial server response time. Google estimates savings of 752 ms on a phone.
Document request latency
750 msThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
600 ms · 119 KiBAbout 119 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 215 KiB8 files are served with short cache lifetimes, so returning visitors download them again (215 KiB).
Google Tag Manager adds 536 ms
536 msGoogle Tag Manager costs a phone 536 ms of main-thread work and 501 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.
2,397 HTML elements
The page has 2,397 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 852 ms
852 msYour server takes 852 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
150 ms · 116 KiB5 images could be 116 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.
Minify CSS
150 ms · 11 KiB11 KiB could be saved by minifying CSS.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Core Web Vitals
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: 7.2 s
7.2 sReal visitors wait 7.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.1 s
6.1 sReal visitors see the first content after 6.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.1 s
4.1 sReal visitors wait 4.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
Total Blocking Time: 916 ms
916 msScripts block taps and scrolling for 916 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 312 ms
312 msReal visitors wait 312 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.2 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 234 ms to 248 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 237 requests
2.8 MBYour homepage downloads 2.8 MB in 237 requests on a phone: scripts 1.5 MB (72), images 515 KiB (32) and fonts 478 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (48 KiB) is 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 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 64 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
186 internal links, 60 external
The homepage links to 186 pages on alsalamahospital.com and 60 external pages.
8 checks passed
Meta description: 109 characters
Your meta description is 109 characters: “أهلا وسهلا بكم في مستشفى السلامة ,ملتزمون بتقديم رعاية صحية رائدة، مفعمة بالإنسانية والرحمة، ومخصصة لكل فرد..”.
One H1 headline
Your main headline reads: “مستشفى السلامة تفتح أبوابها”.
Title: 36 characters
Your title is a healthy 36 characters: “الصفحة الرئيسية - Al Salama Hospital”.
Canonical URL set
The canonical URL is https://alsalamahospital.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://alsalamahospital.com/sitemap_index.xml.
AI search readiness
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://alsalamahospital.com/llms.txt (145 KiB, 689 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://alsalamahospital.com/book-an-appointment, https://alsalamahospital.com/specialties, https://alsalamahospital.com/doctors/internal-medicine/cardiac-center, https://alsalamahospital.com/doctors/internal-medicine/obgyn, https://alsalamahospital.com/doctors/clinical-services/urology and https://alsalamahospital.com/doctors/internal-medicine/pediatric and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages with very little text
https://alsalamahospital.com/book-an-appointment, https://alsalamahospital.com/doctors/internal-medicine/cardiac-center, https://alsalamahospital.com/doctors/internal-medicine/obgyn, https://alsalamahospital.com/doctors/clinical-services/urology, https://alsalamahospital.com/doctors/internal-medicine/pediatric and https://alsalamahospital.com/doctors/internal-medicine/family-medicine and 6 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.
11 pages slow to respond
https://alsalamahospital.com/doctors/internal-medicine/cardiac-center, https://alsalamahospital.com/doctors/internal-medicine/obgyn, https://alsalamahospital.com/doctors/internal-medicine/pediatric, https://alsalamahospital.com/doctors/internal-medicine/family-medicine, https://alsalamahospital.com/doctors/internal-medicine/dental-services and https://alsalamahospital.com/doctors/clinical-services/ophthalmology and 5 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 71 found) and read each the way a search engine does.
6 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.
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
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
100 of 104 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 25 words
The homepage has only about 25 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 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
7 short forms
7 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 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
9 trackers load before any consent
9Before 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
31 other companies contacted
Loading the homepage contacts 31 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 alsalamahospital.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on alsalamahospital.com, including 26 speed issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.