Website review, no card needed

saddlebackleather.com logo

saddlebackleather.com website review

Visit site (opens in a new tab)Reviewed 25 October 202645 issues · 94 checks

This review found 45 issues worth fixing on saddlebackleather.com, 19 of them high impact, across 94 checks. The most urgent: render-blocking requests. 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.9 s1.6 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
121 ms110 msMay 2Oct 17116 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026111 ms
May 9, 2026112 ms
May 16, 2026114 ms
May 23, 2026116 ms
May 30, 2026116 ms
Jun 6, 2026117 ms
Jun 13, 2026117 ms
Jun 20, 2026118 ms
Jun 27, 2026119 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026113 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026112 ms
Aug 29, 2026115 ms
Sep 5, 2026119 ms
Sep 12, 2026119 ms
Sep 19, 2026118 ms
Sep 26, 2026116 ms
Oct 3, 2026118 ms
Oct 10, 2026117 ms
Oct 17, 2026116 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 saddlebackleather.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saddlebackleather.com at 0.8 s0.8 s
  2. saddlebackleather.com at 1.6 s1.6 s
  3. saddlebackleather.com at 2.4 s2.4 s
  4. saddlebackleather.com at 3.2 s3.2 s
  5. saddlebackleather.com at 4.0 s4.0 s
  6. saddlebackleather.com at 4.8 s4.8 s
  7. saddlebackleather.com at 5.6 s5.6 s
  8. saddlebackleather.com at 6.4 s6.4 s

Speed

12 to fix45
  • Render-blocking requests

    3.3 s

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

  • Use efficient cache lifetimes

    1.6 s · 859 KiB

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.3 s

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

  • Improve image delivery

    450 ms · 3.3 MB

    23 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    750 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, shgcdn2.com and Noibu and others), adding 4.5 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    600 ms · 225 KiB

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

  • YouTube adds 311 ms

    311 ms

    YouTube costs a phone 311 ms of main-thread work and 978 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.

  • Bigcommerce adds 71 ms

    71 ms

    Bigcommerce costs a phone 71 ms of main-thread work and 2.5 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.

  • 2,143 HTML elements

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

  • Google Tag Manager adds 146 ms

    146 ms

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

  • 14 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    74 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 73 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    10 KiB

    10 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: 29 ms

    29 ms

    Your server sent the HTML in 29 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.

  • Time to Interactive: 39.0 s

    39.0 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Brown boots on a wooden floor with promotional text about d…”.

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Total Blocking Time: 359 ms

    359 ms

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

  • 23 images without width and height

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

  • Cumulative Layout Shift: 0.122

    0.122

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 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 INP: 110 ms

    110 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 318 ms

    318 ms

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

Images and page weight

4 to fix25
  • Page weight: 9.0 MB in 240 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 240 requests on a phone: images 4.0 MB (46), scripts 3.1 MB (82) and other files 763 KiB (60). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    2.2 MB

    5 images are downloaded at several times the size a phone draws them, for example 31576_source_1787817074.jpg at 2,048 px wide, shown at 130 px. Resized copies would save about 2.2 MB.

  • 8 images in older formats

    8 images (2.7 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.

  • About 2.6 g of CO₂ per visit

    2.55 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 7688
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 12 links without text

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 8583
  • Title is long (91 characters)

    Your title is 91 characters, so Google will cut it off around 60: “Saddleback Leather Co. | Full Grain Leather Bags, Wallets & Accessories | 100-Year Warran…”.

  • Meta description is long (177 characters)

    Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 268 internal links, 7 external

    The homepage links to 268 pages on saddlebackleather.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “The Saddleback Story”.

  • Canonical URL set

    The canonical URL is https://saddlebackleather.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://saddlebackleather.com/xmlsitemap.php.

AI search readiness

100
  • No llms.txt

    There is no https://saddlebackleather.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix88
  • 2 pages share a title

    https://saddlebackleather.com/printed-love41-gift-certificate and https://saddlebackleather.com/printed-sbl-gift-certificate all use the title “Leather Gift Certificate | Saddleback Leather Co.”. 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://saddlebackleather.com/printed-love41-gift-certificate, https://saddlebackleather.com/printed-sbl-gift-certificate, https://saddlebackleather.com/mens-leather-new-arrivals, https://saddlebackleather.com/travel-bags-satchels-1, https://saddlebackleather.com/silverback and https://saddlebackleather.com/womens-wallets 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 106 found) and read each the way a search engine does.

5 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 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 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'contentId'”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    23 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

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

  • Thin social proof

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

  • Only about 155 words

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

  • No opening hours

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

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

5 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Register”, “CONTACT US” and “THE BOOK”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, Hotjar, HubSpot and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 37 cookies set on arrival

    37

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

  • 67 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 saddlebackleather.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Cloudflare Hosting;Black Lotus;Hubspot Hosted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on saddlebackleather.com, including 21 speed issues, 4 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