Website review, no card needed

naadamcashmere.com logo

naadamcashmere.com website review

Visit site (opens in a new tab)Reviewed 12 November 202640 issues · 89 checks

This review found 40 issues worth fixing on naadamcashmere.com, 11 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s2.9 sMay 23Nov 73.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.0 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.4 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
275 ms178 msMay 23Nov 7258 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026194 ms
May 30, 2026211 ms
Jun 6, 2026221 ms
Jun 13, 2026220 ms
Jun 20, 2026248 ms
Jun 27, 2026248 ms
Jul 4, 2026236 ms
Jul 11, 2026215 ms
Jul 18, 2026203 ms
Jul 25, 2026196 ms
Aug 1, 2026189 ms
Aug 8, 2026204 ms
Aug 15, 2026212 ms
Aug 22, 2026213 ms
Aug 29, 2026222 ms
Sep 5, 2026221 ms
Sep 12, 2026226 ms
Sep 19, 2026237 ms
Sep 26, 2026241 ms
Oct 3, 2026246 ms
Oct 10, 2026249 ms
Oct 17, 2026255 ms
Oct 24, 2026263 ms
Oct 31, 2026264 ms
Nov 7, 2026258 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of naadamcashmere.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. naadamcashmere.com at 1.1 s1.1 s
  2. naadamcashmere.com at 2.3 s2.3 s
  3. naadamcashmere.com at 3.4 s3.4 s
  4. naadamcashmere.com at 4.6 s4.6 s
  5. naadamcashmere.com at 5.7 s5.7 s
  6. naadamcashmere.com at 6.9 s6.9 s
  7. naadamcashmere.com at 8.0 s8.0 s
  8. naadamcashmere.com at 9.2 s9.2 s

Speed

13 to fix40
  • Improve image delivery

    1.1 s · 302 KiB

    6 images could be 302 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 6.8 s

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    900 ms

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

  • Google Tag Manager adds 613 ms

    613 ms

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

  • Use efficient cache lifetimes

    596 KiB

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

  • Reduce unused CSS

    300 ms · 125 KiB

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

  • Klaviyo adds 256 ms

    256 ms

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

  • 2,858 HTML elements

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

  • rebuyengine.com adds 193 ms

    193 ms

    rebuyengine.com costs a phone 193 ms of main-thread work and 777 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 adds 144 ms

    144 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    89 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 36 ms

    36 ms

    Your server sent the HTML in 36 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 34.0 s

    34.0 s

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

  • Speed Index: 14.6 s

    14.6 s

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

  • Largest Contentful Paint: 7.5 s

    7.5 s

    Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “30% OFF SITEWIDE*”.

  • Total Blocking Time: 931 ms

    931 ms

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

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 5 images without width and height

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

  • Largest content (LCP) got 17% slower for real visitors

    +17%

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

4 checks passed
  • Real-user INP: 160 ms

    160 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 756 ms

    756 ms

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

  • Cumulative Layout Shift: 0.072

    0.072

    The layout barely moves while loading (CLS 0.072, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 6.8 MB in 428 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 428 requests on a phone: scripts 3.3 MB (154), images 1.5 MB (30) and other files 1.2 MB (201). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    148 KiB

    3 images are downloaded at several times the size a phone draws them, for example Super-Luxe-Cashmino-Fisherman-Rib-Crewneck-Sweater_Smoke_008 at 750 px wide, shown at 115 px. Resized copies would save about 148 KiB.

  • 1 image below the first screen load straight away

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

  • About 1.9 g of CO₂ per visit

    1.92 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 9595
  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    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)

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

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

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

  • 189 internal links, 4 external

    The homepage links to 189 pages on naadamcashmere.com and 4 external pages.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “NAADAM responsibly sources & produces luxury knitwear while preserving nomadic lifestyle in Mongolia. Shop cashmere clo…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “NAADAM | 100% Cashmere Clothing & Accessories”.

  • Canonical URL set

    The canonical URL is https://naadam.co/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://naadam.co/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (782 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://naadam.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://naadam.co/pages/the-cashmere-people has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://naadam.co/collections/sale, https://naadam.co/collections/all, https://naadam.co/pages/gift-guide, https://naadam.co/pages/the-cashmere-people, https://naadam.co/pages/ten-years-of-cashmere and https://naadam.co/pages/original-cashmere-sweater and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://naadam.co/pages/gift-guide took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=22a063d7-45f4-4deb-bb5a-6c1f90076db5&referrer=&landingpage=https%3A%2F%2Fnaadam.co%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_5%20.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 1 third-party cookie

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://naadam.co/cdn/shop/t/1465/assets/main.min.css.liquid?v=143700529891253706751793372…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    118 of 131 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

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

  • About 1,092 words of copy

    The homepage carries about 1,092 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “SHOP WOMEN”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Shop Now”, “Contact Us” and “Shop All”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 5 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.

  • 43 cookies set on arrival

    43

    Opening the homepage sets 43 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 77 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at naadamcashmere.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Klaviyo Email Marketing Sms · Checkmate · Yotpo Loyalty Rewards · Nosto · Rebuy Personalization Engine · Awin Affiliate Marketing · Gdpr Backpack · Giftnote App

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Vue.js
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on naadamcashmere.com, including 23 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25