woolash.com website review

YouTube costs a phone 4.2 s of main-thread work and 5.8 MB 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 14.8 s on main-thread work while loading, 8.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Intercom and others), adding 7.2 MB and 5.6 s of main-thread time.

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

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

Intercom costs a phone 350 ms of main-thread work and 236 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.

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

Klaviyo costs a phone 276 ms of main-thread work and 331 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,594 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 117 KiB of CSS is downloaded but never applied on this page.

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

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

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

1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 23.5 s (Speed Index). Good is under 3.4 s.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.7 MB in 316 requests on a phone: scripts 6.4 MB (126), other files 929 KiB (115) and HTML 508 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

6 frames have no title, so screen-reader users cannot tell what they contain.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link has no real href, so search engines can't follow it.

The homepage links to 30 pages on woolash.com and 0 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

https://www.woolash.com/collections/all, https://www.woolash.com/customer_authentication/redirect, https://www.woolash.com/policies/shipping-policy, https://www.woolash.com/blogs/all, https://www.woolash.com/policies/refund-policy and https://www.woolash.com/pages/affiliate-program and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.woolash.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage 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=187033492&Ver=2&mid=bb4ccc3a-25ba-4cef-9f58-657ef62c01c3&bo=1&sid=7d3e7e00dc3311f1be816f02c76ceeaf&vid=7d3ea2d0dc3311f1b71c51f9e375b618&vids=1&msclkid=N&pi=918639831&l.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

The homepage carries about 2,066 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 24 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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.