mybarworld.com website review

6 images could be 658 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and Klaviyo and others), adding 1.0 MB and 476 ms of main-thread time.

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

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

Klaviyo costs a phone 123 ms of main-thread work and 322 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 25 ms of main-thread work and 362 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.

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

2 KiB JavaScript is shipped twice across bundles.

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

The layout shifts by 0.937 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

8 images 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.

homepage-bar-stacks2.png weighs 579 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 215 requests on a phone: images 1.6 MB (19), scripts 932 KiB (94) and other files 613 KiB (56). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example homepage-bar-stacks2.png at 2,760 px wide, shown at 390 px. Resized copies would save about 475 KiB.

3 images further down the page (119 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

4 dropdowns have no label.

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

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Discover MyBar World Protein Bar: Your Triple-Layered, Healthier Snack”.

There are 2 <h1> headlines (“” and “protein-packed perfection.”). One clear main headline is easier for people and search engines.

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

The homepage links to 35 pages on mybarworld.com and 6 external pages.

There is no https://mybarworld.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.

https://mybarworld.com/collections/all, https://mybarworld.com/products/mybar-caramel-craze-protein-bar, https://mybarworld.com/products/cookie-dough, https://mybarworld.com/products/peanut-butter-paradise and https://mybarworld.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://mybarworld.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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: 6 testimonial or review blocks. 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.

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 311 words of visible text.

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