willowboutique.com website review

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

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

getpurpledot.com costs a phone 1.0 s of main-thread work and 161 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 5.4 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (getpurpledot.com, justsell.live and alia-prod.com and others), adding 3.2 MB and 2.0 s of main-thread time.

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

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

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

alia-prod.com costs a phone 259 ms of main-thread work and 1.8 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.

justsell.live costs a phone 264 ms of main-thread work and 502 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.

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

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

40 KiB could be saved by minifying JavaScript.

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

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

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.

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

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

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

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

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

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

Your homepage downloads 12.9 MB in 420 requests on a phone: media 4.6 MB (8), images 3.9 MB (57) and scripts 2.4 MB (97). Under 2 MB keeps phones on slow connections fast.

Willow_Boutique_Black_Friday_Vault_4a6db41d-984b-4b54-8de0-7 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (385 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

9 buttons have no accessible name, so screen readers announce just “button”.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

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

The homepage links to 341 pages on willowboutique.com and 22 external pages.

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

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

https://willowboutique.com/customer_authentication/redirect, https://willowboutique.com/policies/shipping-policy, https://willowboutique.com/pages/willow-subscription-box and https://willowboutique.com/pages/vip-rewards-program have no meta description, so Google writes the search snippet from whatever text it finds.

https://willowboutique.com/customer_authentication/redirect, https://willowboutique.com/pages/willow-subscription-box and https://willowboutique.com/pages/vip-rewards-program have no <h1> headline, so visitors and search engines get no clear main topic.

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

26 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "video-player" has already been used…”.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 19 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.