icometrix.com website review

Wix costs a phone 1.4 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 4.6 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 4,480 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Wix, Google Tag Manager and visitor-analytics.io and others), adding 2.3 MB and 1.6 s of main-thread time.

Your mobile performance score is 55 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

About 301 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

10 long tasks block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.

About 69 KiB of CSS is downloaded but never applied on this page.

34 KiB JavaScript is shipped twice across bundles.

3 files are served with short cache lifetimes, so returning visitors download them again (24 KiB).

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

Desktop scores 81 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “icometrix home page”.

The page becomes fully interactive after 18.3 s. Good is under 3.8 s.

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 383 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 128 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.8 MB in 269 requests on a phone: other files 1.4 MB (121), scripts 1.4 MB (107) and fonts 347 KiB (4). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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.

8 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (6 elements).

Your meta description is 434 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 38 pages on icometrix.com and 1 external page.

A phone browser shows 844 words, but the HTML your server sends has only 160. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your homepage links to /disease/dementia-and-alzheimer%E2%80%99s, which answers with an error. Visitors hit a dead end and search engines drop it.

/parkinsons-disease and /brain-tumors are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/aria and /disease/amyloid-related-imaging-abnormalities all use the title “ARIA (Amyloid Related Imaging Abnormalities) | Brain MRI AI Detection…”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/post/ge-healthcare-announces-intent-to-acquire-icometrix-to-strengthen-neurology-portfolio-with-brain-mri has no meta description, so Google writes the search snippet from whatever text it finds.

/aria and /disease/amyloid-related-imaging-abnormalities use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /disease/amyloid-related-imaging-abnormalities, whose canonical is /aria. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/contact, /multiple-sclerosis, /dementia-and-alzheimers, /aria, /disease/amyloid-related-imaging-abnormalities and /stroke and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

/multiple-sclerosis, /stroke, /disease/stroke, /traumatic-brain-injury, /disease/traumatic-brain-injury and /epilepsy and 2 others 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.

We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 844 words of visible text.

Before a visitor clicks anything, the page loads Google Ads 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.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.