thestandardsqueeze.com website review

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

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

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

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

8 third-party services load with your homepage (omnisnippet1.com, Clarity and loox.io and others), adding 933 KiB and 746 ms of main-thread time.

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

omnisnippet1.com costs a phone 311 ms of main-thread work and 119 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 23 ms of main-thread work and 424 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 176 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

5 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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.62 (75th percentile). Good is under 0.1.

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

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

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

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

41 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 121 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.8 MB in 245 requests on a phone: media 14.7 MB (5), images 970 KiB (50) and other files 828 KiB (90). Under 2 MB keeps phones on slow connections fast.

opt5a_mobile_band_1080x1420_a9c1dc5a-a6f5-42a8-b7f1-0cd66853 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).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

10 elements hidden from screen readers can still receive keyboard focus.

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

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

All page content should be contained by landmarks: 1 element on the page fails 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 → h5), which makes the page harder to scan with a screen reader.

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

Your title is 79 characters, so Google will cut it off around 60: “The Original Alcohol Squeeze Bottle: Up to 50% Off – The Standard Squeeze AU/NZ”.

There are 2 <h1> headlines (“The Standard Squeeze AU/NZ” and “The Standard Squeeze™ (Black Friday: Up To 50% OF…”). One clear main headline is easier for people and search engines.

The homepage links to 208 pages on thestandardsqueeze.com and 10 external pages.

https://thestandardsqueeze.com/collections/packs, https://thestandardsqueeze.com/collections/coolers-%E2%9D%84%EF%B8%8F%F0%9F%8D%BB, https://thestandardsqueeze.com/collections/hydrate-stainless-steel-water-bottles and https://thestandardsqueeze.com/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://thestandardsqueeze.com/products/the-standard-squeeze%E2%84%A2, whose canonical is https://thestandardsqueeze.com/products/the-standard-squeeze%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thestandardsqueeze.com/pages/black-friday and https://thestandardsqueeze.com/pages/build-your-pack have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,136 words of visible text.

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