Website review, no card needed
healthiummedtech.com website review
Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 81 checks
This review found 38 issues worth fixing on healthiummedtech.com, 12 of them high impact, across 81 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
75C- #82,440 of 126,178 reviewed websitesbeats 30%
- #51,929 of 70,384 online storesbeats 22%
- #1,443 of 2,962 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 124 ms |
| May 16, 2026 | 124 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 110 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 111 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 100 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 101 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.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.2 s
7.0 s
Speed
Render-blocking requests
4.5 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Font display
2.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.0 s).
Reduce unused JavaScript
1.4 s · 329 KiBAbout 329 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Use efficient cache lifetimes
500 ms · 4.8 MB16 files are served with short cache lifetimes, so returning visitors download them again (4.8 MB).
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
365 KiB6 images could be 365 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,215 HTML elements
The page has 2,215 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
sociablekit.com adds 109 ms
109 mssociablekit.com costs a phone 109 ms of main-thread work and 609 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.
8 third-party services on the page
8 third-party services load with your homepage (sociablekit.com, Google Tag Manager and Clarity and others), adding 939 KiB and 319 ms of main-thread time.
Reduce unused CSS
150 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Minify JavaScript
34 KiB34 KiB could be saved by minifying JavaScript.
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 CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 240 ms
240 msYour server sent the HTML in 240 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: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to Healthium A global precision-medtech company foc…”.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Real-user TTFB: 918 ms
918 msReal visitors wait 918 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user INP: 111 ms
111 msReal visitors wait 111 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.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 124 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 52% faster for real visitors
-52%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Total Blocking Time: 42 ms
42 msScripts block the page for only 42 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 19.6 MB in 199 requests
19.6 MBYour homepage downloads 19.6 MB in 199 requests on a phone: media 11.2 MB (10), images 7.0 MB (68) and scripts 834 KiB (50). Under 2 MB keeps phones on slow connections fast.
22 images in older formats
22 images (1.5 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.
7 images below the first screen load straight away
7 images further down the page (277 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.6 g of CO₂ per visit
5.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.56 g of CO₂e: 667.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
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 (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 28 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 mores 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.
Title is short (23 characters)
Your title is only 23 characters: “Home - Healthiummedtech”. Between 30 and 65 characters leaves room to say what you do and for whom.
43 links with vague text
43 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
32 links crawlers can't follow
32 links have no real href, so search engines can't follow them.
Structured data has 4 problems
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 4 problems, for example “WebPage: thumbnailUrl is not an absolute URL ("https://healthiummedtech.com/wp-content/uploads/2023/07/healthium-logo.png")”.
62 internal links, 35 external
The homepage links to 62 pages on healthiummedtech.com and 35 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Healthium”.
Canonical URL set
The canonical URL is https://healthiummedtech.com/.
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://healthiummedtech.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://healthiummedtech.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 (847 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://healthiummedtech.com/category/news is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
14 pages without a meta description
https://healthiummedtech.com/overview, https://healthiummedtech.com/team, https://healthiummedtech.com/qms, https://healthiummedtech.com/r-d-innovation, https://healthiummedtech.com/us-products and https://healthiummedtech.com/products and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://azapp-ci-hml-prod.azurewebsites.net/wp-content/uploads/2023/08/Proxima-Nova.ttf' from origin…”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 2 trust badges. 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.
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,058 words of copy
The homepage carries about 1,058 words of visible text.
2 checks passed
24 calls to action
The homepage has 24 calls to action, for example “Contact Us”, “Learn More” and “Contact us”.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
20 other companies contacted
Loading the homepage contacts 20 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 healthiummedtech.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on healthiummedtech.com, including 18 speed issues, 5 SEO issues 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.