Website review, no card needed
continental.health website review
Visit site (opens in a new tab)Reviewed 2 November 202644 issues · 87 checks
This review found 44 issues worth fixing on continental.health, 13 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 156 ms |
| May 23, 2026 | 156 ms |
| May 30, 2026 | 156 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 155 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 151 ms |
| Oct 24, 2026 | 147 ms |
| Oct 31, 2026 | 145 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.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.1 s
5.9 s
Speed
Use efficient cache lifetimes
900 ms · 3.7 MB33 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Improve image delivery
300 ms · 2.3 MB12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 120 KiBAbout 120 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
600 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Amazon Web Services), adding 1.3 MB and 216 ms of main-thread time.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 978 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 1.1 MB 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Friday Consultation”.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Largest content (LCP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 156 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.096
0.096The layout barely moves while loading (CLS 0.096, good is under 0.1).
Total Blocking Time: 106 ms
106 msScripts block the page for only 106 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.5 MB in 70 requests
4.5 MBYour homepage downloads 4.5 MB in 70 requests on a phone: images 3.9 MB (33), scripts 514 KiB (22) and HTML 57 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.8 MB5 images are downloaded at several times the size a phone draws them, for example bab.png at 1,184 px wide, shown at 104 px. Resized copies would save about 1.8 MB.
6 images in older formats
6 images (2.0 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.
5 images below the first screen load straight away
5 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (319 characters)
Your meta description is 319 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Hospital) but with 1 problem, for example “Hospital: image is not an absolute URL ("https://continental.health/og-image.jpg")”.
49 internal links, 5 external
The homepage links to 49 pages on continental.health and 5 external pages.
5 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Continental Hospital - Best Hospital in Bangladesh”.
Canonical URL set
The canonical URL is https://continental.health/.
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://continental.health/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://continental.health/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,258 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://continental.health/contact-us/subscribe, https://continental.health/patient-guide and https://continental.health/help, which answer with an error. Visitors hit a dead end and search engines drop them.
2 linked pages hidden from search
https://continental.health/pages/md-and-ceo-message and https://continental.health/pages/operational-team are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages share a title
/, https://continental.health/packages, https://continental.health/clinics-and-centers, https://continental.health/book-appointment, https://continental.health/pages/md-and-ceo-message and https://continental.health/pages/operational-team all use the title “Continental Hospital - Best Hospital in Bangladesh”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://continental.health/packages, https://continental.health/clinics-and-centers, https://continental.health/book-appointment, https://continental.health/pages/md-and-ceo-message and https://continental.health/pages/operational-team use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://continental.health/contact-us, https://continental.health/find-doctor, https://continental.health/book-appointment, https://continental.health/board-members, https://continental.health/pages/md-and-ceo-message and https://continental.health/pages/operational-team have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://continental.health/contact-us, https://continental.health/careers, https://continental.health/find-doctor and https://continental.health/faq 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.
1 page slow to respond
https://continental.health/find-doctor took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 12 pages that loaded have a meta description.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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,134 words of copy
The homepage carries about 1,134 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book Appointment”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”, “Book Appointment” and “Contact Info”.
Social proof on the page
Social proof on the homepage: a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 7 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 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 continental.health, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
- Hosting
- CloudFront
Hiring
- Hiring
- 570 open roles
- Job board
- smartrecruiters
- Careers page
- continental.health/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on continental.health, including 18 speed issues, 3 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.