suerox.us website review

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

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

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

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

About 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

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

46 KiB could be saved by minifying JavaScript.

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

About 13 KiB of CSS is downloaded but never applied 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.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GREAT TASTE & POWERFUL REHYDRATION”.

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

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

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

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

Your homepage downloads 3.7 MB in 289 requests on a phone: scripts 1.4 MB (84), images 1.3 MB (58) and other files 809 KiB (122). Under 2 MB keeps phones on slow connections fast.

SX_002.jpg 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).

2 images are downloaded at several times the size a phone draws them, for example SX_002.jpg at 1,169 px wide, shown at 376 px. Resized copies would save about 18 KiB.

1 image further down the page (115 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

Headings skip levels (h2 → h4 and h2 → h4), 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.

The homepage links to 48 pages on suerox.us and 7 external pages.

Your Organization JSON-LD is missing logo, 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.suerox.us/products/strawberry-punch and https://www.suerox.us/collections/products/products/strawberry-punch all use the title “Strawberry-Kiwi Punch 12 Pack – Suerox”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.suerox.us/pages/about-us and https://www.suerox.us/blogs/suerox-blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.suerox.us/products/orange-rescue, https://www.suerox.us/products/strawberry-punch, https://www.suerox.us/products/grape-boost, https://www.suerox.us/collections/products/products/lemon-lime-lift, https://www.suerox.us/collections/products/products/coconut-refresh and https://www.suerox.us/collections/products/products/grape-boost and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.suerox.us/collections/products/products/coconut-refresh-6-pack-copy, whose canonical is https://www.suerox.us/products/coconut-refresh-6-pack-copy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.suerox.us/collections/products and https://www.suerox.us/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.suerox.us/pages/store-locator has 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 26 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “[Weglot] Cannot load Weglot because the project has been deleted”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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