Website review, no card needed
ak-hospital.com website review
Visit site (opens in a new tab)Reviewed 26 October 202648 issues · 90 checks
This review found 48 issues worth fixing on ak-hospital.com, 19 of them high impact, across 90 checks. The most urgent: improve image delivery. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 98 ms |
| Oct 17, 2026 | 100 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.8 s
4.3 s
5.7 s
7.1 s
8.5 s
10.0 s
11.4 s
Speed
Improve image delivery
1.1 s · 13.3 MB39 images could be 13.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
10.6 s · 3.4 MB84 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Reduce unused JavaScript
4.0 s · 925 KiBAbout 925 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
3.8 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 937 ms. During a long task the page ignores taps.
Reduce unused CSS
750 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (JSDelivr CDN, jQuery CDN and Vimeo and others), adding 1.3 MB and 256 ms of main-thread time.
Legacy JavaScript
300 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Vimeo adds 46 ms
46 msVimeo costs a phone 46 ms of main-thread work and 663 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.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 207 ms
207 msYour server sent the HTML in 207 ms, well inside Google's 600 ms guideline.
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.
Largest Contentful Paint: 26.4 s
26.4 sYour largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your companion in health, every step of the way. Our compre…”.
Time to Interactive: 27.0 s
27.0 sThe page becomes fully interactive after 27.0 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 661 ms
661 msScripts block taps and scrolling for 661 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 124 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 18.6 MB in 114 requests
18.6 MBYour homepage downloads 18.6 MB in 114 requests on a phone: images 15.7 MB (71), scripts 2.5 MB (17) and fonts 261 KiB (6). Under 2 MB keeps phones on slow connections fast.
11 images over 500 KB
11 images weigh 13.4 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
7.4 MB11 images are downloaded at several times the size a phone draws them, for example yOLo4GO2qWPo7S1y043I0MBFG9nDTnGDXPSgGZXW.png at 1,792 px wide, shown at 327 px. Resized copies would save about 7.4 MB.
17 images in older formats
17 images (14.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.
12 images below the first screen load straight away
12 images further down the page (13.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.3 g of CO₂ per visit
5.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.28 g of CO₂e: 633.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (20 elements)
Alternative text of images should not be repeated as text: 20 elements on the page fail this check, rated minor by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Page language is “English”
The page declares lang=“English”, which is not a usable language code, so screen readers and translation tools guess.
Headings skip levels
Headings skip levels (h1 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Nurturing your health with our elite team of prof…”, “Your companion in health, every step of the way.” and “Where your health and well-being are our top prio…”). One clear main headline is easier for people and search engines.
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://ak-hospital.com/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
107 internal links, 10 external
The homepage links to 107 pages on ak-hospital.com and 10 external pages.
3 checks passed
Title: 30 characters
Your title is a healthy 30 characters: “Home | Ain Al Khaleej Hospital”.
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
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://ak-hospital.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 (1,890 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages share a title
https://ak-hospital.com/specialities, https://ak-hospital.com/specialities-details/94, https://ak-hospital.com/specialities-details/55, https://ak-hospital.com/specialities-details/93, https://ak-hospital.com/specialities-details/76 and https://ak-hospital.com/specialities-details/51 and 4 others all use the title “Specialities | Ain Al Khaleej Hospital”. 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://ak-hospital.com/appointment, https://ak-hospital.com/survey-form, https://ak-hospital.com/about-us, https://ak-hospital.com/chairmans-word, https://ak-hospital.com/management-team and https://ak-hospital.com/specialities and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://ak-hospital.com/appointment, https://ak-hospital.com/survey-form, https://ak-hospital.com/about-us, https://ak-hospital.com/chairmans-word, https://ak-hospital.com/management-team and https://ak-hospital.com/specialities and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://ak-hospital.com/appointment 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.
5 pages slow to respond
https://ak-hospital.com/appointment, https://ak-hospital.com/specialities-details/51, https://ak-hospital.com/specialities-details/80, https://ak-hospital.com/specialities-details/81 and https://ak-hospital.com/specialities-details/82 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 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.
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
4 small tap targets
4 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,799 words of copy
The homepage carries about 1,799 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 “Book an Appointment”.
34 calls to action
The homepage has 34 calls to action, for example “Book an Appointment”, “Call Back” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 2 trust badges.
Direct contact links
Visitors can reach you directly: 6 phone links and 0 email links.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 2 of them by other companies (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.
9 other companies contacted
Loading the homepage contacts 9 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 ak-hospital.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
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on ak-hospital.com, including 19 speed issues, 6 SEO issues and 1 conversion gap. 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.