Website review, no card needed
ahc.sa website review
Visit site (opens in a new tab)Reviewed 19 October 202635 issues · 72 checks
This review found 35 issues worth fixing on ahc.sa, 15 of them high impact, across 72 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.8 s |
| Jul 4, 2026 | 3.4 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.2 s |
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
Speed
Render-blocking requests
4.7 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Reduce unused JavaScript
1.8 s · 385 KiBAbout 385 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 69). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and Cloudflare CDN and others), adding 1.2 MB and 704 ms of main-thread time.
Reduce unused CSS
300 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 307 ms. During a long task the page ignores taps.
Google CDN adds 258 ms
258 msGoogle CDN costs a phone 258 ms of main-thread work and 347 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.
Google Tag Manager adds 257 ms
257 msGoogle Tag Manager costs a phone 257 ms of main-thread work and 176 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.
Cloudflare CDN adds 158 ms
158 msCloudflare CDN costs a phone 158 ms of main-thread work and 571 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
13 KiB5 files are served with short cache lifetimes, so returning visitors download them again (13 KiB).
Phones get a much slower page than desktops
Desktop scores 69 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
Improve image delivery
6 KiB1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 892 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.5 s
8.5 sThe page becomes fully interactive after 8.5 s. Good is under 3.8 s.
Total Blocking Time: 701 ms
701 msScripts block taps and scrolling for 701 ms in total while the page loads. Good is under 200 ms.
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 3.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 40.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.2 MB in 18 requests
1.2 MBYour homepage downloads 1.2 MB in 18 requests on a phone: scripts 682 KiB (10), fonts 426 KiB (2) and stylesheets 82 KiB (3). That is a lean page.
Accessibility
19 buttons without a name
19 buttons have no accessible name, so screen readers announce just “button”.
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
22 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 6 failed. 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “Home | AHC”. 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.
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 robots.txt
There is no robots.txt at ahc.sa/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
42 internal links, 30 external
The homepage links to 42 pages on ahc.sa and 30 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://ahc.sa/.
XML sitemap found
Your XML sitemap is reachable at https://ahc.sa/sitemap.xml.
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://ahc.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
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
15 pages without a meta description
https://ahc.sa/divisions/infection-prevention-and-control, https://ahc.sa/divisions/medical-supply, https://ahc.sa/divisions/surgical, https://ahc.sa/divisions/emergency-medical-solutions, https://ahc.sa/divisions/renal and https://ahc.sa/divisions/hospital-automation and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 links to non-canonical URLs
Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://ahc.sa/divisions/infection-prevention-and-control, whose canonical is https://ahc.sa/divisions/infection-prevention-and-control?division=infection-prevention-and-control. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://ahc.sa/divisions/infection-prevention-and-control, https://ahc.sa/divisions/medical-supply, https://ahc.sa/divisions/surgical, https://ahc.sa/divisions/emergency-medical-solutions, https://ahc.sa/divisions/renal and https://ahc.sa/divisions/hospital-automation and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://ahc.sa/functions/supply-chain 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 20 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.
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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
43 of 43 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 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.
Only about 137 words
The homepage has only about 137 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “mdi-hammer-wrenchService Request” and “Service Request”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before 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
3Opening 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.
8 other companies contacted
Loading the homepage contacts 8 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 ahc.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
- Vue.js
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on ahc.sa, including 14 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.