Website review, no card needed
acibademimc.com website review
Visit site (opens in a new tab)Reviewed 18 October 202621 issues · 77 checks
This review found 21 issues worth fixing on acibademimc.com, 7 of them high impact, across 77 checks. The most urgent: certain ARIA roles must contain particular children (3 elements). 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 698 ms |
| May 2, 2026 | 699 ms |
| May 9, 2026 | 686 ms |
| May 16, 2026 | 688 ms |
| May 23, 2026 | 725 ms |
| May 30, 2026 | 729 ms |
| Jun 6, 2026 | 740 ms |
| Jun 13, 2026 | 714 ms |
| Jun 20, 2026 | 686 ms |
| Jun 27, 2026 | 706 ms |
| Jul 4, 2026 | 702 ms |
| Jul 11, 2026 | 690 ms |
| Jul 18, 2026 | 705 ms |
| Jul 25, 2026 | 730 ms |
| Aug 1, 2026 | 775 ms |
| Aug 8, 2026 | 785 ms |
| Aug 15, 2026 | 788 ms |
| Aug 22, 2026 | 720 ms |
| Aug 29, 2026 | 682 ms |
| Sep 5, 2026 | 692 ms |
| Sep 12, 2026 | 667 ms |
| Sep 19, 2026 | 663 ms |
| Sep 26, 2026 | 667 ms |
| Oct 3, 2026 | 663 ms |
| Oct 10, 2026 | 680 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 71 ms |
| May 2, 2026 | 71 ms |
| May 9, 2026 | 71 ms |
| May 16, 2026 | 71 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 72 ms |
| Jul 4, 2026 | 72 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 71 ms |
| Aug 15, 2026 | 71 ms |
| Aug 22, 2026 | 71 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 72 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 73 ms |
| Oct 3, 2026 | 73 ms |
| Oct 10, 2026 | 73 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
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Mobile performance score: 78
78/100Your mobile performance score is 78 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 79 KiBAbout 79 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,609 HTML elements
The page has 1,609 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Improve image delivery
42 KiB2 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
32 KiB28 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).
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.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 3 KiB and 0 ms of main-thread time.
1 checks passed
Server response: 309 ms
309 msYour server sent the HTML in 309 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nu ook in Rotterdam! Hoogwaardige, verzekerde zorg met kort…”.
Time to Interactive: 5.1 s
5.1 sThe page becomes fully interactive after 5.1 s. Good is under 3.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 71 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 637 ms
637 msReal visitors wait 637 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 47 ms
47 msScripts block the page for only 47 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 25.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 766 KiB in 45 requests
766 KiBYour homepage downloads 766 KiB in 45 requests on a phone: scripts 316 KiB (28), images 164 KiB (5) and HTML 139 KiB (1). That is a lean page.
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
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
[role="img"] and [role="image"] elements must have alternative text (80 elements)
[role="img"] and [role="image"] elements must have alternative text: 80 elements on the page fail this check, rated serious by axe-core.
25 text elements with low contrast
25 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 (42 elements)
All page content should be contained by landmarks: 42 elements on the page fail this check, rated moderate by axe-core.
99 links without text
99 visible links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
44 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: 44 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Nu ook in Rotterdam!” and “Zorg verlenen is een kunst”). One clear main headline is easier for people and search engines.
187 internal links, 12 external
The homepage links to 187 pages on acibademimc.com and 12 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Acıbadem International Medical Center biedt multidisciplinaire zorg in Amsterdam met 19 afdelingen. Betalingen worden e…”.
Title: 49 characters
Your title is a healthy 49 characters: “ACIBADEM International Medical Center - Amsterdam”.
Canonical URL set
The canonical URL is https://acibademimc.com/.
Structured data in place
Structured data found: Article, BreadcrumbList, ImageObject, MedicalWebPage and Organization.
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://acibademimc.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://acibademimc.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,913 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://acibademimc.com/over-ons and https://acibademimc.com/nl/over-ons all use the title “Over ons - Acibadem International Medical Center”. 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://acibademimc.com/en, https://acibademimc.com/vacatures, https://acibademimc.com/over-ons, https://acibademimc.com/afdelingen, https://acibademimc.com/specialisten and https://acibademimc.com/verzekering and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://acibademimc.com/nl/insurance, whose canonical is https://acibademimc.com/en/insurance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://acibademimc.com/afdelingen 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 42 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 17 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 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 637 words of copy
The homepage carries about 637 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 6 phone links and 2 email links.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host 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 acibademimc.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
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on acibademimc.com, including 8 speed issues, 1 SEO issue and 2 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.