thirtytwo.com website review

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

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

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

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

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

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

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

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

Klaviyo costs a phone 179 ms of main-thread work and 309 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 1,801 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Klaviyo, Shopify and shgcdn3.com and others), adding 586 KiB and 374 ms of main-thread time.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

9 KiB could be saved by minifying CSS.

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

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 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PUBLIC X THIRTYTWO”.

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

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

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

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

8 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.8 MB in 269 requests on a phone: images 1.5 MB (27), scripts 1,007 KiB (98) and other files 802 KiB (110). Under 2 MB keeps phones on slow connections fast.

Hero_Banner_Mobile_Public.webp 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).

10 images (1.0 MB) 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.

8 images are downloaded at several times the size a phone draws them, for example Boots_Collection_Homepage.webp at 600 px wide, shown at 156 px. Resized copies would save about 240 KiB.

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

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

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 190 pages on thirtytwo.com and 12 external pages.

https://thirtytwo.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://thirtytwo.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://thirtytwo.com/customer_authentication/redirect, https://thirtytwo.com/collections/best-seller-snowboards, https://thirtytwo.com/collections/mens-snowboards, https://thirtytwo.com/collections/womens-snowboards, https://thirtytwo.com/collections/youth-snowboards and https://thirtytwo.com/collections/boots and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://thirtytwo.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Shopify is not defined”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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.

The homepage shows no opening hours. If customers visit or call, show when.

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

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

Before a visitor clicks anything, the page loads 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 7 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.