Website review, no card needed

zsupplyclothing.com logo

zsupplyclothing.com website review

Visit site (opens in a new tab)Reviewed 22 October 202649 issues · 100 checks

This review found 49 issues worth fixing on zsupplyclothing.com, 22 of them high impact, across 100 checks. The most urgent: reduce unused JavaScript. 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
2.4 s2.0 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
226 ms148 msMay 2Oct 17206 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026162 ms
May 9, 2026157 ms
May 16, 2026157 ms
May 23, 2026157 ms
May 30, 2026162 ms
Jun 6, 2026168 ms
Jun 13, 2026174 ms
Jun 20, 2026179 ms
Jun 27, 2026185 ms
Jul 4, 2026191 ms
Jul 11, 2026196 ms
Jul 18, 2026203 ms
Jul 25, 2026204 ms
Aug 1, 2026208 ms
Aug 8, 2026206 ms
Aug 15, 2026207 ms
Aug 22, 2026205 ms
Aug 29, 2026204 ms
Sep 5, 2026203 ms
Sep 12, 2026199 ms
Sep 19, 2026206 ms
Sep 26, 2026212 ms
Oct 3, 2026213 ms
Oct 10, 2026217 ms
Oct 17, 2026206 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 zsupplyclothing.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zsupplyclothing.com at 1.1 s1.1 s
  2. zsupplyclothing.com at 2.2 s2.2 s
  3. zsupplyclothing.com at 3.2 s3.2 s
  4. zsupplyclothing.com at 4.3 s4.3 s
  5. zsupplyclothing.com at 5.4 s5.4 s
  6. zsupplyclothing.com at 6.5 s6.5 s
  7. zsupplyclothing.com at 7.6 s7.6 s
  8. zsupplyclothing.com at 8.6 s8.6 s

Speed

13 to fix8
  • Reduce unused JavaScript

    2.3 s · 1.5 MB

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

  • Use efficient cache lifetimes

    2.4 s · 843 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Main-thread work: 14.0 s

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

  • Mobile performance score: 8

    8/100

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

  • 3,388 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and logr-in.com and others), adding 7.9 MB and 2.4 s of main-thread time.

  • Shopify adds 503 ms

    503 ms

    Shopify costs a phone 503 ms of main-thread work and 6.3 MB 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

    600 ms · 133 KiB

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

  • Google Tag Manager adds 562 ms

    562 ms

    Google Tag Manager costs a phone 562 ms of main-thread work and 356 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 385 ms. During a long task the page ignores taps.

  • logr-in.com adds 328 ms

    328 ms

    logr-in.com costs a phone 328 ms of main-thread work and 147 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.

  • ZenDesk adds 184 ms

    184 ms

    ZenDesk costs a phone 184 ms of main-thread work and 383 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.

  • Legacy JavaScript

    150 ms · 69 KiB

    Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    92 KiB

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

  • Duplicated JavaScript

    50 ms · 25 KiB

    25 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

  • Minify JavaScript

    12 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “New Arrivals SHOP NOW”.

  • Time to Interactive: 55.7 s

    55.7 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Cumulative Layout Shift: 0.5

    0.5

    The layout shifts by 0.5 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user CLS: 0.11

    0.11

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

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

    +33%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user INP: 138 ms

    138 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 570 ms

    570 ms

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

Images and page weight

5 to fix18
  • Page weight: 12.0 MB in 387 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 387 requests on a phone: images 7.6 MB (121), scripts 3.1 MB (106) and other files 879 KiB (132). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    5.6 MB

    8 images are downloaded at several times the size a phone draws them, for example ZT263277_WHT_FRONT.jpg at 2,912 px wide, shown at 111 px. Resized copies would save about 5.6 MB.

  • 4 images over 500 KB

    4 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.

  • 3 images below the first screen load straight away

    3 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (1.2 MB) is 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.

  • About 3.4 g of CO₂ per visit

    3.41 g

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

Accessibility

8 to fixGoogle 8488
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 9 images without alt text

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

  • All page content should be contained by landmarks (20 elements)

    All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.

  • 3 links without text

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

  • 1 form field without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

2 to fixGoogle 9293
  • 3 H1 headlines

    There are 3 <h1> headlines (“The Holiday Collection”, “The Colors of Summer” and “Keep It Cozy”). One clear main headline is easier for people and search engines.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 667 internal links, 8 external

    The homepage links to 667 pages on zsupplyclothing.com and 8 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Simplicity and comfort should coexist in every closet. Shop our versatile styles in signature soft fabrics. Free Shippi…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Z SUPPLY | Women's Clothing & Lounge Sets”.

  • Canonical URL set

    The canonical URL is https://zsupplyclothing.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://zsupplyclothing.com/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, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://zsupplyclothing.com/collections/the-layering-shop and https://zsupplyclothing.com/collections/holiday-party-edit have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://zsupplyclothing.com/collections/back-in-stock, https://zsupplyclothing.com/collections/the-layering-shop, https://zsupplyclothing.com/collections/100-cotton-clothing, https://zsupplyclothing.com/collections/travel-must-haves, https://zsupplyclothing.com/collections/holiday-party-edit and https://zsupplyclothing.com/collections/tees-1 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://zsupplyclothing.com/collections/back-in-stock and https://zsupplyclothing.com/collections/travel-must-haves 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 71 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 6 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 1 broken image

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

  • 13 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

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

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 171 words

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop +” and “FREE SHIPPING ON ORDERS $75+ | SHOP NOW”.

  • 109 calls to action

    The homepage has 109 calls to action, for example “The Layering Shop”, “100% Cotton Shop” and “shop +”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Pinterest Tag, The Trade Desk and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 38 cookies set on arrival

    38

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

  • 64 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 zsupplyclothing.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on zsupplyclothing.com, including 23 speed issues, 2 SEO issues and 4 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