namedcollective.com website review

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

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

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

2 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

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

Google Tag Manager costs a phone 592 ms of main-thread work and 920 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 270 ms of main-thread work and 570 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 1,663 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 135 ms of main-thread work and 307 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.

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

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

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

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

25 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

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 page becomes fully interactive after 22.4 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 24.2 MB in 311 requests on a phone: media 19.2 MB (2), scripts 2.4 MB (126) and images 1.3 MB (10). Under 2 MB keeps phones on slow connections fast.

mobile-animationNAT.gif weighs 839 KiB. On a phone connection a single image that size takes seconds.

mobile-animationNAT.gif 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).

2 images (939 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

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

Structured data found (BreadcrumbList and Organization) but with 2 problems, for example “Organization: missing name”.

The homepage links to 141 pages on namedcollective.com and 9 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://namedcollective.com/collections/only-in-ur-dreams and https://namedcollective.com/collections/poison have no meta description, so Google writes the search snippet from whatever text it finds.

https://namedcollective.com/collections/shop-our-sh-t, https://namedcollective.com/collections/sweatpants-joggers, https://namedcollective.com/collections/oversized-sweatpants-joggers, https://namedcollective.com/collections/shorts and https://namedcollective.com/collections/pink-sets have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://namedcollective.com/.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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.

The homepage has only about 131 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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