brumeta.us website review

The page goes through 2 redirects before it starts loading, costing about 9.0 s. Link and advertise the final URL directly.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

Shopify costs a phone 1.6 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and brumate.com and others), adding 4.6 MB and 2.9 s of main-thread time.

brumate.com costs a phone 316 ms of main-thread work and 1.0 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.

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

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

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

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

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

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

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 57 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.

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.

For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.

Your largest element takes 31.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A sparkly Jade green BrüMate tumbler with a handle and stra…”.

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

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

The first text or image appears after 6.6 s on a phone. Good is under 1.8 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 1.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 985 ms for your server to start answering (75th percentile). Good is under 800 ms.

Your homepage downloads 8.3 MB in 606 requests on a phone: scripts 4.3 MB (197), fonts 1.6 MB (30) and other files 1.0 MB (250). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

The robots meta tag says “noindex”: Google is told not to list this page at all.

Your title is 79 characters, so Google will cut it off around 60: “BrüMate | Innovative + Leakproof Straw Tumblers, Drinkware & Coolers. – BruMate”.

Your canonical URL points to shop.brumate.com, not brumeta.us, so Google may credit that host instead.

There are 2 <h1> headlines (“Shopping Cart” and “INNOVATIVE PRODUCTS TO ENHANCE YOUR EVERY DAY.”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 105 pages on brumeta.us and 8 external pages.

Your homepage links to https://brumeta.us/collections/growl-r, https://brumeta.us/collections/winesulator, https://brumeta.us/collections/infinity-collection and https://brumeta.us/collections/spirits, which answer with an error. Visitors hit a dead end and search engines drop them.

https://brumeta.us/collections/beer, https://brumeta.us/collections/hopsulator-slim-1, https://brumeta.us/collections/hopsulator-trio-1, https://brumeta.us/collections/hopsulator-duo-1, https://brumeta.us/collections/hopsulator-bott-l and https://brumeta.us/collections/juggernaut and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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