nydj.com website review

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

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

19 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Osano CMP and route.com and others), adding 2.4 MB and 2.0 s of main-thread time.

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

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

Osano CMP costs a phone 364 ms of main-thread work and 85 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.

route.com costs a phone 299 ms of main-thread work and 542 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.

Google Tag Manager costs a phone 290 ms of main-thread work and 365 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 204 ms of main-thread work and 344 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,027 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

62 KiB could be saved by minifying JavaScript.

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

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

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

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.

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

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

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

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

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

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 8.2 MB in 408 requests on a phone: scripts 3.6 MB (162), images 2.5 MB (25) and other files 1.1 MB (187). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example MCLBMS9500-BLKST_PDP_1.jpg at 1,200 px wide, shown at 169 px. Resized copies would save about 1.6 MB.

2 images further down the page (46 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 2.32 g of CO₂e: 278.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Some list items are not inside a list.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

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

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

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

The homepage links to 264 pages on nydj.com and 9 external pages.

https://nydj.com/collections/40-off-holiday-sale is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://nydj.com/collections/gibsonlook-x-nydj and https://nydj.com/collections/cbs-x-nydj-denim-country have no meta description, so Google writes the search snippet from whatever text it finds.

https://nydj.com/collections/40-off-holiday-sale, https://nydj.com/collections/new-arrivals, https://nydj.com/pages/denimquiz, https://nydj.com/collections/nydjs-women-jeans, https://nydj.com/collections/straight-jeans and https://nydj.com/collections/womens-bootcut-jeans and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 107 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=15001173&Ver=2&mid=61d059f5-da9c-461b-8c27-6262d53e0606&bo=1&sid=05ff21f0d9a011f19cc14d23ec05ff75&vid=05ffc780d9a011f1b90c7d78ed1698c0&vids=1&msclkid=N&pi=918639831&lg.

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://nydj.com/cdn/shop/t/1904/assets/app_wishlist-king_templates.css?v=91273' because i…”.

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 610 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 Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 43 cookies (measured from a US location before any click).

Loading the homepage contacts 65 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.