taylorstitch.net website review

Google Tag Manager costs a phone 1.7 s of main-thread work and 697 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Cookiebot and others), adding 1.9 MB and 4.3 s of main-thread time.

About 993 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Hotjar costs a phone 585 ms of main-thread work and 65 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.

Cookiebot costs a phone 553 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.

Facebook costs a phone 351 ms of main-thread work and 230 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.

Yotpo costs a phone 337 ms of main-thread work and 216 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.

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

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

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

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.

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

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Embedded Video: WINTER 2026”.

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

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

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

Your homepage downloads 13.8 MB in 337 requests on a phone: media 7.4 MB (1), images 2.7 MB (95) and scripts 2.3 MB (97). Under 2 MB keeps phones on slow connections fast.

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

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

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 206 pages on taylorstitch.net and 10 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 https://www.taylorstitch.com/collections/mens-shirts-sweaters, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.taylorstitch.com/blogs/help-center and https://www.taylorstitch.com/help all use the title “Help Center & Support Portal | Taylor Stitch”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.taylorstitch.com/pages/offers, https://www.taylorstitch.com/collections/mens-new-arrivals, https://www.taylorstitch.com/collections/mens-all-jacks, https://www.taylorstitch.com/collections/mens-bottoms, https://www.taylorstitch.com/collections/mens-outerwear and https://www.taylorstitch.com/collections/mens-accessories and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.taylorstitch.com/pages/offers, https://www.taylorstitch.com/collections/mens-new-arrivals, https://www.taylorstitch.com/collections/mens-all-jacks, https://www.taylorstitch.com/collections/mens-bottoms, https://www.taylorstitch.com/collections/mens-outerwear and https://www.taylorstitch.com/collections/mens-accessories and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

3 errors were logged to the browser console during Google's test (“Access to fetch at 'https://a.klaviyo.com/client/sessions/?company_id=fwLqkE' from origin 'https://…”).

Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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