bariatricfoodsource.com website review

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

8 images could be 312 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

7 third-party services load with your homepage (omnisnippet1.com, Shopify and shop.app and others), adding 198 KiB and 95 ms of main-thread time.

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

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

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

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 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

BFS_To_Merge_With_AmBari_Nutrition_3_533x.png 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).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https:files/AB187-BFS-Logo.png")”.

The homepage links to 70 pages on bariatricfoodsource.com and 7 external pages.

https://www.bariatricfoodsource.com/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.bariatricfoodsource.com/collections/bariatric-shakes-drinks and https://www.bariatricfoodsource.com/collections/bariatric-protein-shakes-smoothies all use the title “Best Bariatric Protein Shakes & Drinks | High-Protein & Low-Sugar – A…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.bariatricfoodsource.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bariatricfoodsource.com/collections/bariatric-shakes-drinks and https://www.bariatricfoodsource.com/collections/bariatric-protein-shakes-smoothies use the same meta description. A description written for each page earns more clicks.

https://www.bariatricfoodsource.com/collections/all, https://www.bariatricfoodsource.com/collections, https://www.bariatricfoodsource.com/pages/dietary-concern-for-bariatric-patients and https://www.bariatricfoodsource.com/blogs/bariatric-guide-homepage have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.bariatricfoodsource.com/collections and https://www.bariatricfoodsource.com/pages/dietary-concern-for-bariatric-patients 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 42 found) and read each the way a search engine does.

5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 518 words of visible text.

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

Opening the homepage sets 10 cookies, 1 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.