Website review, no card needed
orionhealth.com website review
Visit site (opens in a new tab)Reviewed 31 October 202635 issues · 87 checks
This review found 35 issues worth fixing on orionhealth.com, 11 of them high impact, across 87 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.7 s |
| May 16, 2026 | 5.7 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 97 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 100 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 112 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.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Render-blocking requests
4.7 s53 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Use efficient cache lifetimes
1.1 s · 1.6 MB112 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Mobile performance score: 80
80/100Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (FontAwesome CDN, Hubspot and cdn-cookieyes.com and others), adding 770 KiB and 762 ms of main-thread time.
Reduce unused CSS
300 ms · 193 KiBAbout 193 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.
FontAwesome CDN adds 374 ms
374 msFontAwesome CDN costs a phone 374 ms of main-thread work and 121 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.
Hubspot adds 311 ms
311 msHubspot costs a phone 311 ms of main-thread work and 504 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,696 HTML elements
The page has 1,696 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
211 KiBAbout 211 KiB of JavaScript is downloaded but never used on this page.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user LCP: 4.7 s
4.7 sReal visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.9 s
9.9 sThe page becomes fully interactive after 9.9 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our platforms connect people, healthcare providers and data…”. Most of its time is element render delay (3.7 s).
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 97 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.7 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 138 ms
138 msScripts block the page for only 138 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.6 g of CO₂ per visit
0.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 66.9 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: 2.0 MB in 143 requests
2.0 MBYour homepage downloads 2.0 MB in 143 requests on a phone: scripts 746 KiB (56), fonts 664 KiB (8) and images 261 KiB (18). 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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
<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.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Page language is “global”
The page declares lang=“global”, which is not a usable language code, so screen readers and translation tools guess.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
181 internal links, 3 external
The homepage links to 181 pages on orionhealth.com and 3 external pages.
8 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Reimagine your healthcare delivery with Orion Health's healthcare software solutions. Improve patient outcomes and stre…”.
One H1 headline
Your main headline reads: “Talk to the health data specialists”.
Title: 64 characters
Your title is a healthy 64 characters: “Reimagining Healthcare through Software Solutions | Orion Health”.
Canonical URL set
The canonical URL is https://orionhealth.com/global/.
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://orionhealth.com/sitemap_index.xml.
AI search readiness
4 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,687 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://orionhealth.com/llms.txt (3 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share 4 titles
https://orionhealth.com/global/amadeus-ai and https://orionhealth.com/amadeus-ai all use the title “Amadeus AI: Real-Time AI Insights for Better Care | Orion Health”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://orionhealth.com/global/amadeus-ai and https://orionhealth.com/amadeus-ai use the same meta description. A description written for each page earns more clicks.
12 links to non-canonical URLs
Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://orionhealth.com/global/virtuoso, whose canonical is https://orionhealth.com/global/amadeus-ai. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://orionhealth.com/digital-front-door took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
9 small tap targets
9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 249 words
The homepage has only about 249 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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
8 calls to action
The homepage has 8 calls to action, for example “Learn More about Virtuoso”, “Learn More about SMART Suite” and “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 orionhealth.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
- Hosting
- SiteHost New Zealand
Company
- Founded
- 1993
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 orionhealth.com, including 17 speed issues, 1 SEO issue and 3 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.