Programmable

Website review, no card needed

ssv.net logo

ssv.net website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 74 checks

This review found 34 issues worth fixing on ssv.net, 11 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

73C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.8 s1.4 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 16, 20263.9 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jul 4, 20263.7 s
Aug 8, 20263.1 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.4 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
149 ms110 msSep 19Oct 17144 ms
Show as table
DateReal-visitor tap response (INP)
Sep 19, 2026129 ms
Sep 26, 2026122 ms
Oct 3, 2026114 ms
Oct 10, 2026142 ms
Oct 17, 2026144 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

www.vailresortsretail.com (opens in a new tab)
Full-page screenshot of ssv.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ssv.net at 0.4 s0.4 s
  2. ssv.net at 0.8 s0.8 s
  3. ssv.net at 1.1 s1.1 s
  4. ssv.net at 1.5 s1.5 s
  5. ssv.net at 1.9 s1.9 s
  6. ssv.net at 2.3 s2.3 s
  7. ssv.net at 2.6 s2.6 s
  8. ssv.net at 3.0 s3.0 s

Speed

6 to fix67

  • Render-blocking requests

    1.5 s

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

  • Use efficient cache lifetimes

    350 ms · 1.5 MB

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67 (desktop: 54). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 169 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (transcend-cdn.com, gravity-apps.com and Shopify and others), adding 3.9 MB and 95 ms of main-thread time.

  • gravity-apps.com adds 37 ms

    37 ms

    gravity-apps.com costs a phone 37 ms of main-thread work and 3.7 MB 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.

  • Font display

    50 ms

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

  • Reduce unused CSS

    18 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed

  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 353 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67

  • Fails Core Web Vitals for real visitors

    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.

  • Real-user FCP: 4.0 s

    4.0 s

    Real visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalize content and ads, to provide s…”.

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Time to Interactive: 6.7 s

    6.7 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 1 image without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

4 checks passed

  • Real-user INP: 144 ms

    144 ms

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

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70

  • Page weight: 4.9 MB in 151 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 151 requests on a phone: images 3.6 MB (5), other files 765 KiB (95) and scripts 445 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8490

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8586

  • Title is short (19 characters)

    Your title is only 19 characters: “Vail Resorts Retail”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (291 characters)

    Your meta description is 291 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 59 internal links, 7 external

    The homepage links to 59 pages on ssv.net and 7 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “<img src="//www.vailresortsretail.com/cdn/shop/files/vail-resorts-retail-logo_160x.jpg?v=1613534970" srcset="//www.vail…”.

  • Canonical URL set

    The canonical URL is https://www.vailresortsretail.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.vailresortsretail.com/sitemap.xml.

AI search readiness

100
3 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://www.vailresortsretail.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90

  • 14 pages share a title

    https://www.vailresortsretail.com/pages/about-us, https://www.vailresortsretail.com/pages/heavenly, https://www.vailresortsretail.com/pages/kirkwood, https://www.vailresortsretail.com/pages/northstar, https://www.vailresortsretail.com/pages/stevens-pass-1 and https://www.vailresortsretail.com/pages/hunter and 8 others all use the title “Retail - Vail Resorts”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://www.vailresortsretail.com/pages/about-us, https://www.vailresortsretail.com/pages/heavenly, https://www.vailresortsretail.com/pages/kirkwood, https://www.vailresortsretail.com/pages/northstar, https://www.vailresortsretail.com/pages/stevens-pass-1 and https://www.vailresortsretail.com/pages/hunter and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687

  • 8 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: This build of Transcend Consent Manager cannot run on https://www.vailresortsretail.com! If you are the…”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50

  • No call to action on the first screen

    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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • Only about 135 words

    The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

2 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    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.

  • 10 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ssv.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on ssv.net, including 14 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25