satchel-page.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Clarity and Klaviyo and others), adding 1.1 MB and 642 ms of main-thread time.

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

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

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

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

11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

1 image 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 120 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.6 MB in 304 requests on a phone: scripts 1.5 MB (106), other files 1.0 MB (165) and images 845 KiB (16). Under 2 MB keeps phones on slow connections fast.

Q1092979-750x720-3_700x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Your title is only 27 characters: “Satchel & Page leather bags”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 48 pages on satchel-page.com and 3 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.

https://www.satchel-page.com/collections/luggage, https://www.satchel-page.com/collections/belts and https://www.satchel-page.com/collections/warehouse-sale use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25063973&Ver=2&mid=e6b1cd13-5032-4074-adf9-0d303c60657a&bo=1&sid=c2f5fb70d9b711f19961c106f4396f1d&vid=c2f638a0d9b711f1a38ca54742d25de2&vids=1&msclkid=N&pi=918639831&lg.

5 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

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.

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

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

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

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

The homepage carries about 641 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.

Opening the homepage sets 31 cookies (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 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.