snowbird.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.6 MB and 1.4 s of main-thread time.

14 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

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

Facebook costs a phone 337 ms of main-thread work and 340 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,420 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 49 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.

3 KiB could be saved by minifying CSS.

1 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 42.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile hero of an athlete hitting a cliff at Snowbird's in …”.

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 268 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

4 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-24, real Chrome visitors' tap response (inp) went from 254 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.7 MB in 170 requests on a phone: scripts 3.8 MB (47), images 3.8 MB (44) and other files 1,008 KiB (66). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example last.jpg at 1,920 px wide, shown at 340 px. Resized copies would save about 1.1 MB.

last.jpg weighs 569 KiB. On a phone connection a single image that size takes seconds.

7 images (1.4 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.

4 images further down the page (639 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (9 elements).

Your title is only 8 characters: “Snowbird”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Freeride World Tour at The Bird”, “Freeride World Tour at The Bird” and “Countdown Until Opening Day”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 66 pages on snowbird.com and 42 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.snowbird.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=26056042&tm=gtm002&Ver=2&mid=d355e18a-74b6-4c1e-bfb9-38840ff3a5aa&bo=1&sid=fbbecaa0d47411f1902a3f911c08c8fd&vid=fbbee2b0d47411f19d2a0bb61cbf4bcb&vids=1&msclkid=N&pi=91.

12 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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.

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 987 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 19 cookies (measured from a US location before any click).

Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.