ninewest.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Noibu and Klaviyo and others), adding 1.7 MB and 1.5 s of main-thread time.

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

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

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

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

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

Noibu costs a phone 262 ms of main-thread work and 162 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.

Klaviyo costs a phone 172 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.

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

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

11 KiB JavaScript is shipped twice across bundles.

6 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.

3 KiB could be saved by minifying JavaScript.

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 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 26.3 s. Good is under 3.8 s.

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

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

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

Real visitors wait 233 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 9.0 MB in 449 requests on a phone: media 4.1 MB (3), scripts 2.6 MB (218) and other files 1.1 MB (186). Under 2 MB keeps phones on slow connections fast.

NW_1126_PROMO_HOLIDAY_HOT_HEELS_EVENT_HP_P1_MB_37368d06-9b72 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).

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

1 button has no accessible name, so screen readers announce just “button”.

5 tap targets are too small or too close together to hit reliably with a finger.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h6, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

Your <h1> is empty.

The homepage links to 509 pages on ninewest.com and 10 external pages.

https://ninewest.com/policies/shipping-policy, https://ninewest.com/pages/nw-welcome-offer, https://ninewest.com/pages/promotions/2026-11-01-holiday-hot-heels-event-collection-header, https://ninewest.com/pages/promotions/2026-11-03-currently-coveting-ohmy and https://ninewest.com/collections/holiday-plaid-exclusive-drop have no meta description, so Google writes the search snippet from whatever text it finds.

https://ninewest.com/policies/shipping-policy, https://ninewest.com/pages/nw-welcome-offer, https://ninewest.com/collections/heels-event, https://ninewest.com/pages/promotions/2026-11-01-holiday-hot-heels-event-collection-header, https://ninewest.com/products/ohmy-pointy-toe-stiletto-heel-dress-booties-in-leopard-n-ohmyp5-dna01 and https://ninewest.com/pages/promotions/2026-11-03-currently-coveting-ohmy and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ninewest.com/collections/wedding-guest took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 117 found) 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=16002154&tm=gtm002&Ver=2&mid=ef011415-6679-4645-9034-9cda530cb880&bo=1&sid=1fe33a70d80d11f1ace477bbb973646f&vid=1fe36450d80d11f1bdbbfd366ff35bfc&vids=1&msclkid=N&pi=91.

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

5 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.

Social proof on the homepage: 12 testimonial or review blocks. 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.

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.

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

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

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