Website review, no card needed

vlisco.com logo

vlisco.com website review

Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 83 checks

This review found 41 issues worth fixing on vlisco.com, 11 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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.9 s1.5 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.5 s
Sep 26, 20263.3 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
369 ms187 msMay 9Oct 24348 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026215 ms
May 16, 2026208 ms
May 23, 2026210 ms
May 30, 2026212 ms
Jun 6, 2026219 ms
Jun 13, 2026231 ms
Jun 20, 2026233 ms
Jun 27, 2026230 ms
Jul 4, 2026227 ms
Jul 11, 2026217 ms
Jul 18, 2026212 ms
Jul 25, 2026216 ms
Aug 1, 2026225 ms
Aug 8, 2026243 ms
Aug 15, 2026258 ms
Aug 22, 2026263 ms
Aug 29, 2026258 ms
Sep 5, 2026250 ms
Sep 12, 2026246 ms
Sep 19, 2026261 ms
Sep 26, 2026303 ms
Oct 3, 2026327 ms
Oct 10, 2026333 ms
Oct 17, 2026342 ms
Oct 24, 2026348 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 vlisco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vlisco.com at 1.4 s1.4 s
  2. vlisco.com at 2.8 s2.8 s
  3. vlisco.com at 4.2 s4.2 s
  4. vlisco.com at 5.6 s5.6 s
  5. vlisco.com at 7.0 s7.0 s
  6. vlisco.com at 8.4 s8.4 s
  7. vlisco.com at 9.8 s9.8 s
  8. vlisco.com at 11.2 s11.2 s

Speed

9 to fix63
  • Reduce unused JavaScript

    450 ms · 657 KiB

    About 657 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    800 ms

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

  • 8 third-party services on the page

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

  • Improve image delivery

    300 ms · 51 KiB

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

  • Main-thread work: 3.3 s

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

  • 2,880 HTML elements

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

  • Google Tag Manager adds 159 ms

    159 ms

    Google Tag Manager costs a phone 159 ms of main-thread work and 310 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 115 ms

    115 ms

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

  • Minify JavaScript

    150 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    159 KiB

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    43 KiB

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

  • Legacy JavaScript

    28 KiB

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

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

1 checks passed
  • Server response: 73 ms

    73 ms

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

Core Web Vitals

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

  • Time to Interactive: 23.5 s

    23.5 s

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 272 ms

    272 ms

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

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

    +63%

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

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

    +79%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Total Blocking Time: 241 ms

    241 ms

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 8.3 MB in 419 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 419 requests on a phone: media 3.0 MB (1), scripts 1.8 MB (84) and other files 1.8 MB (274). Under 2 MB keeps phones on slow connections fast.

  • About 2.4 g of CO₂ per visit

    2.35 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8591
  • 8 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 6 links without text

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

  • 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
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Introducing Vlisco Vibe”). One clear main headline is easier for people and search engines.

  • Meta description is long (275 characters)

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

  • 69 internal links, 10 external

    The homepage links to 69 pages on vlisco.com and 10 external pages.

6 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “VLISCO Official | Luxury African Fabrics – Vlisco”.

  • Canonical URL set

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

  • 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://vlisco.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://vlisco.com/pages/vibe, https://vlisco.com/collections/sewing-patterns, https://vlisco.com/collections/vibe, https://vlisco.com/pages/radiance and https://vlisco.com/pages/silk-stories have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://vlisco.com/pages/vibe and https://vlisco.com/pages/radiance 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 36 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 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4057054&tm=gtm002&Ver=2&mid=feb76387-401b-4bcc-9afa-e5d0fbe558a8&bo=1&sid=f10ca010d57f11f19869ff04757e4aa6&vid=f10cc160d57f11f19a8d23d753c6cd87&vids=1&msclkid=N&pi=918.

  • 9 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

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

  • Only about 193 words

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

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “B2B shop” and “Contact Us”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Microsoft Ads, Pinterest Tag and TikTok Pixel (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.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 vlisco.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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on vlisco.com, including 20 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