Website review, no card needed

theavalanchesstore.com logo

theavalanchesstore.com website review

Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 75 checks

This review found 32 issues worth fixing on theavalanchesstore.com, 8 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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
1.2 s923 msMay 23Nov 7965 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 2026977 ms
Jul 11, 20261.0 s
Jul 25, 2026985 ms
Aug 1, 20261.1 s
Aug 8, 2026960 ms
Aug 15, 2026991 ms
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.0 s
Nov 7, 2026965 ms
Real-visitor tap response (INP)75th percentile, phones
141 ms80 msMay 23Nov 7128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 2026103 ms
Jun 20, 2026101 ms
Jun 27, 2026101 ms
Jul 4, 2026104 ms
Jul 25, 202692 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202695 ms
Aug 22, 202698 ms
Aug 29, 2026101 ms
Sep 5, 2026127 ms
Sep 12, 2026116 ms
Sep 19, 2026120 ms
Sep 26, 2026116 ms
Oct 3, 2026121 ms
Oct 10, 2026124 ms
Oct 17, 2026134 ms
Oct 24, 2026134 ms
Oct 31, 2026129 ms
Nov 7, 2026128 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 theavalanchesstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix60
  • Reduce unused JavaScript

    2.2 s · 642 KiB

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. 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 (Google Tag Manager, ZenDesk and transcend-cdn.com and others), adding 1.2 MB and 721 ms of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 206 KiB

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

  • Improve image delivery

    532 KiB

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

  • Google Tag Manager adds 352 ms

    352 ms

    Google Tag Manager costs a phone 352 ms of main-thread work and 342 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 CSS

    300 ms · 25 KiB

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

  • 7 long tasks on the main thread

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

  • ZenDesk adds 140 ms

    140 ms

    ZenDesk costs a phone 140 ms of main-thread work and 394 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.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Since I Left You (2026 Reissue 2LP)”.

  • Time to Interactive: 12.6 s

    12.6 s

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

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

    +34%

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

  • Total Blocking Time: 478 ms

    478 ms

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

8 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: 1.0 s

    1.0 s

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

  • Real-user INP: 117 ms

    117 ms

    Real visitors wait 117 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 465 ms

    465 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix60
  • 1 image over 500 KB

    NBM_Monster-Children_03_4a6bc94a-14e3-486b-a6d3-0a8cefce71ef weighs 897 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.1 MB in 175 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 175 requests on a phone: scripts 1.4 MB (51), images 862 KiB (15) and other files 794 KiB (103). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (897 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.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

2 checks passed
  • 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

3 to fixGoogle 9194
  • 7 tap targets too small

    7 tap targets are 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “The Avalanches AU Official Store - The Avalanches AU Official Store”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“The Avalanches AU Official Store” and “The Avalanches AU Official Store”). One clear main headline is easier for people and search engines.

  • 34 internal links, 15 external

    The homepage links to 34 pages on theavalanchesstore.com and 15 external pages.

5 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “Shop exclusive merch and apparel from The Avalanches AU Official Store. Apparel, music, and more.”.

  • Canonical URL set

    The canonical URL is https://theavalanchesstore.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://theavalanchesstore.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

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

  • llms.txt published

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://theavalanchesstore.com/collections/music, https://theavalanchesstore.com/collections/merchandise, https://theavalanchesstore.com/policies/terms-of-service and https://theavalanchesstore.com/policies/privacy-policy use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://theavalanchesstore.com/pages/contact-us has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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
  • 9 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 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 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 113 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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
  • 2 calls to action

    The homepage has 2 calls to action, for example “Subscribe” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 9 cookies set on arrival

    9

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 theavalanchesstore.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

trackedlink.net · privy.com · esc-apps-cdn.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on theavalanchesstore.com, including 14 speed issues, 3 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