justaddbuoy.com website review

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

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

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

8 third-party services load with your homepage (ContentSquare, Facebook and Klaviyo and others), adding 1.5 MB and 1.4 s of main-thread time.

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

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

ContentSquare costs a phone 423 ms of main-thread work and 210 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.

Facebook costs a phone 318 ms of main-thread work and 226 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 327 ms. During a long task the page ignores taps.

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

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

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

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

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

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

11 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.

4 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 7.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.9 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

Your homepage downloads 7.5 MB in 342 requests on a phone: media 3.4 MB (1), scripts 1.7 MB (119) and other files 1,014 KiB (123). Under 2 MB keeps phones on slow connections fast.

1_1_BYOB_3919bbd6-4eb7-433c-ae52-d37f840196d8.webp weighs 692 KiB. On a phone connection a single image that size takes seconds.

4 images (827 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example hp-starter-set-fallback.webp at 1,080 px wide, shown at 350 px. Resized copies would save about 3 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.4 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.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Structured data found (Organization, VideoObject, WebPage and WebSite) but with 8 problems, for example “VideoObject: contentUrl is not an absolute URL ("//justaddbuoy.com/cdn/shop/videos/c/vp/b4eb65ab731…”.

The homepage links to 121 pages on justaddbuoy.com and 6 external pages.

https://justaddbuoy.com/pages/electrolyte-starter-set-cd and https://justaddbuoy.com/pages/buoy-rewards are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://justaddbuoy.com/collections/all and https://justaddbuoy.com/pages/electrolyte-starter-set-cd have no meta description, so Google writes the search snippet from whatever text it finds.

https://justaddbuoy.com/pages/byob, https://justaddbuoy.com/products/hydration-drops, https://justaddbuoy.com/products/digestion-drops, https://justaddbuoy.com/collections/all, https://justaddbuoy.com/pages/electrolyte-discovery-set and https://justaddbuoy.com/pages/chronic-illness-support and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 985 words of visible text.

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