mbiota.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Klaviyo and others), adding 3.4 MB and 1.3 s of main-thread time.

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

About 852 KiB of JavaScript is downloaded but never used on this page.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

Google Tag Manager costs a phone 453 ms of main-thread work and 839 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.

Shopify costs a phone 100 ms of main-thread work and 1.5 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.

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

Klaviyo costs a phone 191 ms of main-thread work and 524 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.

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

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

1 image could be 169 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

30 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 5.5 MB in 336 requests on a phone: scripts 2.4 MB (145), media 1.2 MB (2) and other files 910 KiB (139). Under 2 MB keeps phones on slow connections fast.

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

12 images have no alt text, which hurts accessibility and image search.

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 218 pages on mbiota.com and 6 external pages.

https://mbiota.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://mbiota.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://mbiota.com/pages/ibd and https://mbiota.com/pages/ibd-crohn-s-ulcerative-colitis all use the title “IBD (Crohn’s / Ulcerative Colitis) – mBIOTA Elemental”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mbiota.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://mbiota.com/pages/ibd and https://mbiota.com/pages/ibd-crohn-s-ulcerative-colitis use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mbiota.com/pages/ibd-crohn-s-ulcerative-colitis, whose canonical is https://mbiota.com/pages/ibd. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mbiota.com/customer_authentication/redirect, https://mbiota.com/products/elemental-diet, https://mbiota.com/products/elemental-diet-1-week-plan, https://mbiota.com/products/nutritional-maintenance-elemental-diet-plan and https://mbiota.com/pages/transitioning-from-an-elemental-diet-back-to-food have no <h1> headline, so visitors and search engines get no clear main topic.

https://mbiota.com/products/elemental-diet, https://mbiota.com/products/elemental-diet-1-week-plan and https://mbiota.com/products/nutritional-maintenance-elemental-diet-plan 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.

https://mbiota.com/customer_authentication/redirect, https://mbiota.com/products/elemental-diet-1-week-plan, https://mbiota.com/products/nutritional-maintenance-elemental-diet-plan and https://mbiota.com/pages/what-is-an-elemental-diet took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console during Google's test (“Access to fetch at 'https://shdid.me/api/cbc/identify' from origin 'https://mbiota.com' has been bl…”).

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.

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

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 1,343 words of visible text.