Website review, no card needed

alpine-footwear.com logo

alpine-footwear.com website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 85 checks

This review found 40 issues worth fixing on alpine-footwear.com, 14 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
3.9 s3.1 sMay 30Nov 143.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20263.8 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.7 s
Aug 22, 20263.6 s
Aug 29, 20263.5 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Nov 7, 20263.2 s
Nov 14, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
183 ms123 msMay 30Nov 14171 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026136 ms
Jun 6, 2026130 ms
Jun 13, 2026131 ms
Jun 20, 2026132 ms
Jun 27, 2026137 ms
Jul 4, 2026138 ms
Jul 11, 2026143 ms
Jul 18, 2026143 ms
Jul 25, 2026143 ms
Aug 1, 2026145 ms
Aug 8, 2026146 ms
Aug 15, 2026151 ms
Aug 22, 2026152 ms
Aug 29, 2026153 ms
Sep 5, 2026156 ms
Sep 12, 2026161 ms
Sep 19, 2026163 ms
Sep 26, 2026164 ms
Oct 3, 2026170 ms
Oct 10, 2026175 ms
Oct 17, 2026174 ms
Oct 24, 2026176 ms
Oct 31, 2026170 ms
Nov 7, 2026171 ms
Nov 14, 2026171 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

Full-page screenshot of alpine-footwear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alpine-footwear.com at 0.6 s0.6 s
  2. alpine-footwear.com at 1.3 s1.3 s
  3. alpine-footwear.com at 1.9 s1.9 s
  4. alpine-footwear.com at 2.6 s2.6 s
  5. alpine-footwear.com at 3.2 s3.2 s
  6. alpine-footwear.com at 3.9 s3.9 s
  7. alpine-footwear.com at 4.5 s4.5 s
  8. alpine-footwear.com at 5.2 s5.2 s

Speed

8 to fix59
  • Use efficient cache lifetimes

    1.6 s · 221 KiB

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

  • Reduce unused JavaScript

    1.4 s · 227 KiB

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

  • Mobile performance score: 59

    59/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (loox.io, Facebook and cloudfront.net and others), adding 2.5 MB and 576 ms of main-thread time.

  • Improve image delivery

    400 ms · 282 KiB

    6 images could be 282 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • 2,782 HTML elements

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

  • Shopify adds 72 ms

    72 ms

    Shopify costs a phone 72 ms of main-thread work and 1.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.

  • Main-thread work: 2.3 s

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

  • Legacy JavaScript

    200 ms · 51 KiB

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

  • Reduce unused CSS

    150 ms · 38 KiB

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

  • Render-blocking requests

    150 ms

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

  • 3 long tasks on the main thread

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.7 s

    17.7 s

    Your largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BAREFOOT SHOES - Lorax Pro”.

  • Time to Interactive: 20.9 s

    20.9 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

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

    +29%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 757 ms

    757 ms

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

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

    -11%

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

  • Total Blocking Time: 106 ms

    106 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.4 MB in 276 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 276 requests on a phone: images 2.2 MB (53), scripts 1,007 KiB (93) and other files 834 KiB (108). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    42 KiB

    2 images are downloaded at several times the size a phone draws them, for example bare-foot-icon-muscules.webp at 390 px wide, shown at 100 px. Resized copies would save about 42 KiB.

  • 5 images in older formats

    5 images (238 KiB) 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.

  • About 1.3 g of CO₂ per visit

    1.26 g

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

1 checks passed
  • Images load when needed

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

Accessibility

9 to fixGoogle 9088
  • 5 tap targets too small

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

  • 2 text elements with low contrast

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

  • Malformed lists

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

  • 6 images without alt text

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

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (15 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 78 internal links, 4 external

    The homepage links to 78 pages on alpine-footwear.com and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://alpine-footwear.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://alpine-footwear.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,036 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix52
  • 1 linked page is broken

    Your homepage links to https://alpine-footwear.com/collections/barefoot-shoes, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 10 pages share 5 titles

    / and https://alpine-footwear.com/apps/tracktor/track all use the title “Alpine Footwear”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://alpine-footwear.com/collections/barefoot-shoes-for-kids, https://alpine-footwear.com/collections/foot-care-accessories, https://alpine-footwear.com/collections/winter-barefoot-shoes, https://alpine-footwear.com/pages/support, https://alpine-footwear.com/apps/tracktor/track and https://alpine-footwear.com/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://alpine-footwear.com/products/toe-separator and https://alpine-footwear.com/collections/all/products/toe-separator use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://alpine-footwear.com/collections/all/products/toe-separator, whose canonical is https://alpine-footwear.com/products/toe-separator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://alpine-footwear.com/collections/barefoot-shoes-for-kids, https://alpine-footwear.com/collections/foot-care-accessories, https://alpine-footwear.com/collections/winter-barefoot-shoes, https://alpine-footwear.com/pages/support and https://alpine-footwear.com/apps/tracktor/track have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://alpine-footwear.com/collections/all/products/foot-massage-cone and https://alpine-footwear.com/collections/all/products/insoles took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 13 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 analytics detected

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

  • About 384 words of copy

    The homepage carries about 384 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Apply discount code”, “Track Your Order” and “email [email protected]”.

  • 12 short forms

    12 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, 1 trust badge and “15,000+ reviews”.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 alpine-footwear.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Kaching Bundles · Klaviyo Email Marketing Sms · Nabu For Fb Pixel · Countdown Timer · Accessibility Assistant · Zipify Oneclickupsell · loox.io · cloudfront.net · goaffpro.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on alpine-footwear.com, including 13 speed issues, 4 SEO issues and 2 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