utahskis.com website review

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

8 third-party services load with your homepage (Clarity, LiveChat and searchspring.io and others), adding 1.4 MB and 903 ms of main-thread time.

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

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

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

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

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

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

LiveChat costs a phone 165 ms of main-thread work and 364 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.

azurefd.net costs a phone 127 ms of main-thread work and 329 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 108 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.

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

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

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

3 KiB could be saved by minifying CSS.

Your largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Visually, the page fills in at 7.5 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 319 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 9.4 MB in 361 requests on a phone: images 6.6 MB (43), scripts 1.3 MB (118) and other files 1.1 MB (155). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example NoahWetzel_April-2023_SolitudeResortUtah_1.jpg at 4,000 px wide, shown at 264 px. Resized copies would save about 5.5 MB.

4 images weigh 4.8 MB together. On a phone connection a single image that size takes seconds.

101.png 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).

1 image (32 KiB) is 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.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 331 pages on utahskis.com and 3 external pages.

https://utahskis.com/collections/2027-gear, https://utahskis.com/collections/ski-25, https://utahskis.com/collections/mens, https://utahskis.com/collections/womens, https://utahskis.com/collections/kids and https://utahskis.com/collections/accessories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343259368&Ver=2&mid=f9887de6-f9c3-492d-97e5-9e92d29de7a1&bo=1&sid=236388a0ddcd11f19c34470486a3c840&vid=23643420ddcd11f18e2b7f17369976cb&vids=1&msclkid=N&pi=918639831&l.

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

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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