palomawool.com website review

4 images could be 308 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 1.1 MB and 862 ms of main-thread time.

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

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

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

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.

Your largest element takes 18.5 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 19.3 s. Good is under 3.8 s.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 107 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.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 237 requests on a phone: scripts 1.3 MB (76), fonts 1.2 MB (11) and other files 777 KiB (117). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 25 characters: “Paloma Wool – paloma wool”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token '<', ..." "logo":<svg class"... is not va)”.

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

Your <h1> is empty.

The homepage links to 81 pages on palomawool.com and 29 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.

There is no /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.

/policies/shipping-policy, /collections/ready-to-wear and /collections/cupro have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/tops, /collections/bottoms and /collections/knits use the same meta description. A description written for each page earns more clicks.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 459 words of visible text.

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