thejacketmaker.com website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

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 9.5 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Shopify, gotolstoy.com and Google Tag Manager and others), adding 4.1 MB and 2.5 s of main-thread time.

35 images could be 1.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.

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

136 KiB could be saved by minifying JavaScript.

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

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

gotolstoy.com costs a phone 500 ms of main-thread work and 547 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.

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

rebuyengine.com costs a phone 242 ms of main-thread work and 709 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.

ZenDesk costs a phone 177 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.

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

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

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

7 KiB could be saved by minifying CSS.

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.

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 28.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

16 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 146 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.8 MB in 594 requests on a phone: images 6.1 MB (104), scripts 3.4 MB (159) and other files 1.1 MB (277). Under 2 MB keeps phones on slow connections fast.

31 images further down the page (3.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

11 images (1.2 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.

5 images are downloaded at several times the size a phone draws them, for example Mens_Leather_Shoes.webp at 1,000 px wide, shown at 179 px. Resized copies would save about 346 KiB.

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

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

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

10 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 66 characters, so Google will cut it off around 60: “The Jacket Maker: Authentic Custom Leather Jackets For Men & Women”.

There are 2 <h1> headlines (“” and “Create Your Custom Leather Jackets”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 317 pages on thejacketmaker.com and 57 external pages.

https://www.thejacketmaker.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.thejacketmaker.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.thejacketmaker.com/collections/all and https://www.thejacketmaker.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thejacketmaker.com/collections/all, https://www.thejacketmaker.com/customer_authentication/redirect, https://www.thejacketmaker.com/collections/mens-leather-jackets, https://www.thejacketmaker.com/collections/mens-bomber-jackets, https://www.thejacketmaker.com/collections/mens-biker-leather-jackets and https://www.thejacketmaker.com/collections/mens-suede-jackets and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thejacketmaker.com/collections/all, https://www.thejacketmaker.com/collections/mens-leather-jackets, https://www.thejacketmaker.com/collections/mens-bomber-jackets, https://www.thejacketmaker.com/collections/mens-biker-leather-jackets, https://www.thejacketmaker.com/collections/mens-suede-jackets and https://www.thejacketmaker.com/collections/mens-varsity-jacket and 4 others have 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.

https://www.thejacketmaker.com/customer_authentication/redirect, https://www.thejacketmaker.com/collections/mens-bomber-jackets, https://www.thejacketmaker.com/collections/mens-biker-leather-jackets, https://www.thejacketmaker.com/collections/mens-suede-jackets, https://www.thejacketmaker.com/collections/mens-varsity-jacket and https://www.thejacketmaker.com/collections/mens-blazers and 1 other took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Your longest form asks for 10 fields (3 required). Every extra field lowers completion.

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 1,896 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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