Website review, no card needed

alpinestars.com logo

alpinestars.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 90 checks

This review found 43 issues worth fixing on alpinestars.com, 14 of them high impact, across 90 checks. The most urgent: improve image delivery. 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
2.0 s1.3 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
205 ms110 msMay 2Oct 17188 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026124 ms
May 9, 2026122 ms
May 16, 2026122 ms
May 23, 2026122 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026121 ms
Jul 11, 2026123 ms
Jul 18, 2026132 ms
Jul 25, 2026145 ms
Aug 1, 2026157 ms
Aug 8, 2026173 ms
Aug 15, 2026179 ms
Aug 22, 2026180 ms
Aug 29, 2026183 ms
Sep 5, 2026183 ms
Sep 12, 2026187 ms
Sep 19, 2026194 ms
Sep 26, 2026193 ms
Oct 3, 2026192 ms
Oct 10, 2026187 ms
Oct 17, 2026188 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 alpinestars.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alpinestars.com at 0.4 s0.4 s
  2. alpinestars.com at 0.9 s0.9 s
  3. alpinestars.com at 1.3 s1.3 s
  4. alpinestars.com at 1.8 s1.8 s
  5. alpinestars.com at 2.2 s2.2 s
  6. alpinestars.com at 2.7 s2.7 s
  7. alpinestars.com at 3.1 s3.1 s
  8. alpinestars.com at 3.5 s3.5 s

Speed

10 to fix52
  • Improve image delivery

    2.0 s · 619 KiB

    15 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Main-thread work: 7.1 s

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

  • 4,940 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Google Tag Manager and iubenda and others), adding 953 KiB and 1.5 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Clarity adds 825 ms

    825 ms

    Clarity costs a phone 825 ms of main-thread work and 28 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.

  • Render-blocking requests

    800 ms

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

  • Reduce unused CSS

    450 ms · 80 KiB

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

  • Google Tag Manager adds 338 ms

    338 ms

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

  • Reduce unused JavaScript

    274 KiB

    About 274 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    150 ms · 80 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • 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: 17 ms

    17 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 20.9 s

    20.9 s

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

  • Time to Interactive: 23.2 s

    23.2 s

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

  • Speed Index: 8.4 s

    8.4 s

    Visually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 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 INP: 203 ms

    203 ms

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

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

    +52%

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

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

    +31%

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

  • Total Blocking Time: 363 ms

    363 ms

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 590 ms

    590 ms

    Real visitors wait 590 ms for your server to start answering (75th percentile). Good is under 800 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 fix63
  • Page weight: 6.1 MB in 347 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 347 requests on a phone: images 3.6 MB (55), scripts 1.1 MB (141) and other files 950 KiB (139). Under 2 MB keeps phones on slow connections fast.

  • 29 images below the first screen load straight away

    29 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.73 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8791
  • Hidden but focusable

    36 elements hidden from screen readers can still receive keyboard focus.

  • 5 text elements with low contrast

    5 text elements don'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.

  • 7 images without alt text

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

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

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

  • 73 links without text

    73 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h5), 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. (1 element).

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 9289
  • Title is short (26 characters)

    Your title is only 26 characters: “Alpinestars® Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.alpinestars.com/cdn/shop/files/alpinestars-square…”.

  • 662 internal links, 0 external

    The homepage links to 662 pages on alpinestars.com and 0 external pages.

6 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Alpinestars protection and performance apparel trusted by world champions, engineered for performance. Crafted with Ita…”.

  • One H1 headline

    Your main headline reads: “Alpinestars”.

  • Canonical URL set

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

  • 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.alpinestars.com/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix76
  • 2 pages share a title

    https://www.alpinestars.com/pages/road and https://www.alpinestars.com/pages/racing-sport all use the title “Road”. 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://www.alpinestars.com/pages/membership, https://www.alpinestars.com/collections/all-motorcycle, https://www.alpinestars.com/collections/new-arrivals-all-moto, https://www.alpinestars.com/pages/adventure-motorcycle, https://www.alpinestars.com/collections/all-terra-gear-sets and https://www.alpinestars.com/collections/motorcycle-hoodies-pullovers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.alpinestars.com/pages/road and https://www.alpinestars.com/pages/racing-sport use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.alpinestars.com/pages/racing-sport, whose canonical is https://www.alpinestars.com/pages/road. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://www.alpinestars.com/collections/sale-all, https://www.alpinestars.com/pages/help-center, https://www.alpinestars.com/pages/membership, https://www.alpinestars.com/pages/road, https://www.alpinestars.com/collections/all-motorcycle and https://www.alpinestars.com/collections/new-arrivals-all-moto and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.alpinestars.com/collections/all-terra-gear-sets, https://www.alpinestars.com/collections/moto-jackets and https://www.alpinestars.com/collections/motorcycle-hoodies-pullovers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://www.alpinestars.com/.

  • 11 small tap targets

    11 of 44 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 “Access to fetch at 'https://whoami.leafsignal.app/' from origin 'https://www.alpinestars.com' has been blocked by CORS …”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

  • About 287 words of copy

    The homepage carries about 287 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All S-R7” and “Shop Helmet”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop Tech-Air®”, “Shop All S-R7” and “Shop Helmet”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

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

  • 22 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 alpinestars.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity

Hiring

Hiring
8 open roles
Teams
Customer Service (2), Graphic Design (2), Sales (2), Video/Editing (2)
Job board
lever

Company

Founded
1963
Headquarters
Asolo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on alpinestars.com, including 19 speed issues, 2 SEO issues and 4 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