Website review, no card needed
westslopegear.com website review
Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 85 checks
This review found 35 issues worth fixing on westslopegear.com, 15 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #48,828 of 125,639 reviewed websitesbeats 55%
- #32,101 of 70,221 online storesbeats 48%
- #30,830 of 63,794 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 105 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 113 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Render-blocking requests
3.4 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused JavaScript
1.8 s · 885 KiBAbout 885 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (route.com, negate.io and Shopify and others), adding 2.2 MB and 1.5 s of main-thread time.
Use efficient cache lifetimes
150 ms · 831 KiB18 files are served with short cache lifetimes, so returning visitors download them again (831 KiB).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 441 ms. During a long task the page ignores taps.
route.com adds 369 ms
369 msroute.com costs a phone 369 ms of main-thread work and 542 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.
Shopify adds 255 ms
255 msShopify costs a phone 255 ms of main-thread work and 400 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.
Privy adds 228 ms
228 msPrivy costs a phone 228 ms of main-thread work and 403 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.
negate.io adds 260 ms
260 msnegate.io costs a phone 260 ms of main-thread work and 40 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.
Cloudflare CDN adds 164 ms
164 msCloudflare CDN costs a phone 164 ms of main-thread work and 697 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
150 ms · 130 KiBAbout 130 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.
Improve image delivery
150 ms · 20 KiB3 images could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Minify JavaScript
30 KiB30 KiB could be saved by minifying JavaScript.
Minify CSS
14 KiB14 KiB could be saved by minifying CSS.
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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 641 ms
641 msScripts block taps and scrolling for 641 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.154
0.154The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 277 ms
277 msReal visitors wait 277 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.5 MB in 242 requests
4.5 MBYour homepage downloads 4.5 MB in 242 requests on a phone: scripts 2.1 MB (69), images 941 KiB (32) and other files 881 KiB (109). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (56 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 1.3 g of CO₂ per visit
1.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 154.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 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
Invalid ARIA attributes
6 elements use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid values (6 elements)
ARIA attributes must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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
59 internal links, 4 external
The homepage links to 59 pages on westslopegear.com and 4 external pages.
8 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “At West Slope, we build highly functional, ultra rugged gear for adventure sports | Dedicated to Adventure”.
One H1 headline
Your main headline reads: “<img src="//westslopegear.com/cdn/shop/files/Logo_2x_77446ad8-cdeb-418a-9810-2ae9a0345641_100x.png?v=1642871014" srcset…”.
Title: 64 characters
Your title is a healthy 64 characters: “West Slope | Outdoor Gear - Chest Packs, Front Packs, Slope Pack”.
Canonical URL set
The canonical URL is https://westslopegear.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://westslopegear.com/sitemap.xml.
AI search readiness
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 description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (556 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://westslopegear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://westslopegear.com/products/universal-chest-pack declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://westslopegear.com/products/universal-chest-pack all use the title “West Slope | Outdoor Gear - Chest Packs, Front Packs, Slope Pack”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages without a meta description
https://westslopegear.com/collections/packs, https://westslopegear.com/collections/all-bundles, https://westslopegear.com/collections/accessories, https://westslopegear.com/collections/hunting, https://westslopegear.com/collections/snow-sports and https://westslopegear.com/collections/running and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
7 small tap targets
7 of 23 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 “Failed to load resource: net::ERR_FAILED”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 220 words
The homepage has only about 220 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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
14 calls to action
The homepage has 14 calls to action, for example “Shop by Activity”, “Shop Now” and “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 2 of them by other companies (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.
44 other companies contacted
Loading the homepage contacts 44 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 westslopegear.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
Eg Auto Add To Cart · Triplewhale · Instant Ai Page Builder · Judge Me Reviews · Epa Easy Product Addons · Hoppy Free Shipping · privy.com · govx.com · route.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
Company
- Headquarters
- Steamboat Springs
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on westslopegear.com, including 19 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.