bariatriceating.com website review

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

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

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

Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (alia-prod.com, Shopify and rebuyengine.com and others), adding 2.3 MB and 1.7 s of main-thread time.

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

About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

alia-prod.com costs a phone 538 ms of main-thread work and 272 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.

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

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

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

rebuyengine.com costs a phone 211 ms of main-thread work and 758 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.

Google CDN costs a phone 134 ms of main-thread work and 300 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.

7 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

10 KiB could be saved by minifying JavaScript.

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.

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.

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

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pink and brown protein powder packages labeled Vanilla Bean…”.

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

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

Real visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 5.5 MB in 400 requests on a phone: scripts 2.3 MB (156), fonts 1.3 MB (29) and other files 811 KiB (129). Under 2 MB keeps phones on slow connections fast.

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

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Eating After Weight-Loss Surgery & on GLP-1 Meds | Bariatric Eating”.

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

The homepage links to 240 pages on bariatriceating.com and 12 external pages.

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.

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

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

https://www.bariatriceating.com/policies/shipping-policy and https://www.bariatriceating.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bariatriceating.com/pages/contact-us and https://www.bariatriceating.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=151003988&tm=gtm002&Ver=2&mid=def8e91d-d06b-4144-86d4-6daa2b480209&bo=1&sid=e93b3720dd9011f1a3d5137e3f0216bc&vid=e93b47c0dd9011f1a92f5763b403a12b&vids=1&msclkid=N&pi=9.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

2 images are served at too low a resolution for sharp phone screens.

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.

The homepage carries about 3,436 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 22 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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.