loyalwest.com website review

61 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and PayPal and others), adding 4.5 MB and 1.6 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

PayPal costs a phone 203 ms of main-thread work and 395 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.

LiveChat costs a phone 79 ms of main-thread work and 364 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.

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

27 KiB could be saved by minifying CSS.

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

8 KiB could be saved by minifying JavaScript.

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

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

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

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

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

The layout shifts by 0.289 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 11.5 MB in 637 requests on a phone: images 5.9 MB (112), scripts 3.4 MB (248) and other files 1.5 MB (230). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example 2_42c71f1a-c4f6-4c31-bcd5-e006effcd9aa_800x.webp at 800 px wide, shown at 161 px. Resized copies would save about 729 KiB.

22 images (2.0 MB) 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.

2 images further down the page (159 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Scrollable region must have keyboard access: 24 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 68 characters, so Google will cut it off around 60: “Loyal West | Premium Handcrafted Leather Goods & Western Accessories”.

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

The homepage links to 165 pages on loyalwest.com and 2 external pages.

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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://loyalwest.com/collections/conceal-bags, whose canonical is https://loyalwest.com/collections/concealed-carry-bags. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://loyalwest.com/collections/best-sellers, https://loyalwest.com/collections/new-arrivals, https://loyalwest.com/collections/new-best-seller, https://loyalwest.com/collections/new-bags, https://loyalwest.com/collections/new-shoes and https://loyalwest.com/collections/new-accessories and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

The homepage carries about 851 words of visible text.

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.

Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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