Website review, no card needed

kutfromthekloth.com logo

kutfromthekloth.com website review

Visit site (opens in a new tab)Reviewed 6 November 202627 issues · 78 checks

This review found 27 issues worth fixing on kutfromthekloth.com, 7 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
1.3 s812 msMay 16Oct 31971 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026918 ms
Oct 3, 2026870 ms
Oct 10, 2026869 ms
Oct 17, 2026895 ms
Oct 24, 2026947 ms
Oct 31, 2026971 ms
Real-visitor tap response (INP)75th percentile, phones
158 ms125 msMay 16Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026137 ms
May 23, 2026137 ms
May 30, 2026137 ms
Jun 6, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026141 ms
Jul 4, 2026145 ms
Jul 11, 2026145 ms
Jul 18, 2026140 ms
Jul 25, 2026137 ms
Aug 1, 2026130 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026130 ms
Aug 29, 2026132 ms
Sep 5, 2026135 ms
Sep 12, 2026137 ms
Sep 19, 2026138 ms
Sep 26, 2026145 ms
Oct 3, 2026148 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026146 ms
Oct 31, 2026138 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 kutfromthekloth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kutfromthekloth.com at 0.4 s0.4 s
  2. kutfromthekloth.com at 0.8 s0.8 s
  3. kutfromthekloth.com at 1.1 s1.1 s
  4. kutfromthekloth.com at 1.5 s1.5 s
  5. kutfromthekloth.com at 1.9 s1.9 s
  6. kutfromthekloth.com at 2.3 s2.3 s
  7. kutfromthekloth.com at 2.6 s2.6 s
  8. kutfromthekloth.com at 3.0 s3.0 s

Speed

4 to fix94
  • Render-blocking requests

    1.1 s

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

  • Use efficient cache lifetimes

    431 KiB

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

  • 1,555 HTML elements

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

  • Shopify adds 3 ms

    3 ms

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

  • Improve image delivery

    118 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (blink-script.com, Shopify and videowise.com and others), adding 680 KiB and 13 ms of main-thread time.

  • Reduce unused CSS

    74 KiB

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

  • Font display

    50 ms

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

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

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 44 ms of it running JavaScript. That is comfortably low.

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

1 to fix100
  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

12 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 148 ms

    148 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 575 ms

    575 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.5 s

    2.5 s

    The page is fully interactive after 2.5 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 87 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 87 requests on a phone: scripts 1,001 KiB (47), images 836 KiB (17) and HTML 183 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    33 KiB

    1 image is downloaded at several times the size a phone draws it, for example Doorbuster-Tile-Meg-kneeling_KUT0671_v3.jpg at 1,400 px wide, shown at 358 px. Resized copies would save about 33 KiB.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 9092
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 12 images without alt text

    12 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)

    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.

  • 19 links without text

    19 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

4 to fixGoogle 8380
  • Title is short (18 characters)

    Your title is only 18 characters: “Kut from the Kloth”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “In Your Element”). One clear main headline is easier for people and search engines.

  • Meta description is long (206 characters)

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

  • No social preview image

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

  • 228 internal links, 14 external

    The homepage links to 228 pages on kutfromthekloth.com and 14 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.kutfromthekloth.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage, WebPage and WebSite.

  • 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://www.kutfromthekloth.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

  • Text is in the HTML

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

Other pages

5 to fix58
  • 3 pages without a title

    /collections/game-day, /collections/exclusives and /collections/wide-leg have no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    /discount/EXTRA40 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and /discount/EXTRA40 all use the title “Kut from the Kloth”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    /collections/holiday-doorbusters, /collections/velveteen-1, /collections/corduroy, /collections/coated-denim, /collections/game-day and /collections/camo-animal-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    /discount/EXTRA40, /collections/new-arrivals, /collections/denim, /collections/holiday-doorbusters, /collections/velveteen-1 and /collections/corduroy and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9291
  • 6 JavaScript errors while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    21 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 762 words of copy

    The homepage carries about 762 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop New Arrivals”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “SHOP NOW”, “Shop All” and “Shop All Denim”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 51 cookies set on arrival

    51

    Opening the homepage sets 51 cookies (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.

  • 70 other companies contacted

    Loading the homepage contacts 70 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 kutfromthekloth.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 38 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Intelligems A B Testing · Videowise Connect · Klaviyo Email Marketing Sms · Microsoft Clarity · Unveild Kut From The Kloth · Yoast Seo · Checkmate · Attentive · Xo Insert Code · Eg Auto Add To Cart · Mntn · Puco Sections Blocks · Swatch King · Flair · Okendo · Ta Labels Badges · Triplewhale · Gorgias Live Chat Helpdesk · Wunderkind · Variant Image Swatch · Pusher Sections Builder · Gdpr Backpack · Rivo Loyalty Rewards Referrals · Loop Returns · Upcart · cloudfront.net · wheelio-app.com · snapchat.com · shoppinggives.com

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
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on kutfromthekloth.com, including 5 speed issues, 4 SEO issues and 1 conversion gap. 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