jnyofficial.us website review

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

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

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

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

8 third-party services load with your homepage (alia-prod.com, Dynamic Yield and jny.com and others), adding 1.7 MB and 1.0 s of main-thread time.

alia-prod.com costs a phone 484 ms of main-thread work and 265 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.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

jny.com costs a phone 91 ms of main-thread work and 369 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 53 ms of main-thread work and 403 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 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

23 KiB could be saved by minifying JavaScript.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TODAYS DEALS”.

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

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

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

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

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

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 3.7 MB in 274 requests on a phone: scripts 2.5 MB (127), images 413 KiB (18) and fonts 374 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.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”.

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

All page content should be contained by landmarks: 3 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 68 characters, so Google will cut it off around 60: “Jones New York: Women's Clothing, Suits, Jackets, Dresses, and Pants”.

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

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.jny.com/)”.

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

The homepage links to 14 pages on jnyofficial.us and 6 external pages.

The HTML your server sends has 93 of the 264 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.jnyofficial.us/pages/jny-lexington-denim, https://www.jnyofficial.us/pages/faq and https://www.jnyofficial.us/apps/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jnyofficial.us/pages/who-we-are, https://www.jnyofficial.us/blogs/jones-journal, https://www.jnyofficial.us/products/jones-new-york-gift-card, https://www.jnyofficial.us/pages/jny-lexington-denim, https://www.jnyofficial.us/pages/contact-us and https://www.jnyofficial.us/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jnyofficial.us/blogs/jones-journal, https://www.jnyofficial.us/pages/jny-lexington-denim and https://www.jnyofficial.us/pages/faq have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

The homepage carries about 264 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 21 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.