Website review, no card needed

fabricworld.com logo

fabricworld.com website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 81 checks

This review found 31 issues worth fixing on fabricworld.com, 9 of them high impact, across 81 checks. The most urgent: 8,719 HTML elements. 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.5 s1.5 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
141 ms99 msMay 23Nov 7121 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026129 ms
May 30, 2026122 ms
Jun 6, 2026128 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026104 ms
Jul 4, 2026109 ms
Jul 11, 2026113 ms
Jul 18, 2026113 ms
Jul 25, 2026128 ms
Aug 1, 2026121 ms
Aug 8, 2026120 ms
Aug 15, 2026120 ms
Aug 22, 2026113 ms
Aug 29, 2026118 ms
Sep 5, 2026121 ms
Sep 12, 2026121 ms
Sep 19, 2026133 ms
Sep 26, 2026133 ms
Oct 3, 2026136 ms
Oct 10, 2026121 ms
Oct 17, 2026112 ms
Oct 24, 2026111 ms
Oct 31, 2026104 ms
Nov 7, 2026121 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 fabricworld.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fabricworld.com at 0.7 s0.7 s
  2. fabricworld.com at 1.5 s1.5 s
  3. fabricworld.com at 2.2 s2.2 s
  4. fabricworld.com at 3.0 s3.0 s
  5. fabricworld.com at 3.7 s3.7 s
  6. fabricworld.com at 4.4 s4.4 s
  7. fabricworld.com at 5.2 s5.2 s
  8. fabricworld.com at 5.9 s5.9 s

Speed

9 to fix83
  • 8,719 HTML elements

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

  • Main-thread work: 4.3 s

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

  • Improve image delivery

    2.1 MB

    30 images could be 2.1 MB 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 (Facebook, Google Tag Manager and TikTok and others), adding 3.4 MB and 699 ms of main-thread time.

  • Mobile performance score: 83

    83/100

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

  • Reduce unused JavaScript

    394 KiB

    About 394 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 43 ms

    43 ms

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

  • Use efficient cache lifetimes

    276 KiB

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

  • Google Tag Manager adds 162 ms

    162 ms

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

  • 11 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Legacy JavaScript

    32 KiB

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

  • Reduce unused CSS

    17 KiB

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

  • 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: 20 ms

    20 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Total Blocking Time: 277 ms

    277 ms

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

  • 2 images without width and height

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

9 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.7 s

    1.7 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 577 ms

    577 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

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

    -13%

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Fabric World is your online fabric superstore with the newe…”.

  • 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: 7.1 MB in 259 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 259 requests on a phone: images 4.7 MB (53), scripts 1.3 MB (64) and other files 799 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.01 g of CO₂e: 240.9 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 8670
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

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

  • Headings skip levels

    Headings skip levels (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
  • 8 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Fabric World Brings You Top Designer Fabrics”). One clear main headline is easier for people and search engines.

  • Meta description is long (317 characters)

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

  • Structured data has 1 problem

    Structured data found (OnlineStore, Organization and WebSite) but with 1 problem, for example “OnlineStore: logo is not an absolute URL ("REPLACE_WITH_FABRICWORLD_LOGO_IMAGE_URL")”.

  • 2,123 internal links, 3 external

    The homepage links to 2,123 pages on fabricworld.com and 3 external pages.

5 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Fabric World - Online Fabric Store - Samples Ship Free”.

  • Canonical URL set

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

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

AI search readiness

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

  • llms.txt published

    The site publishes https://fabricworld.com/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://fabricworld.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://fabricworld.com/collections/all, https://fabricworld.com/collections/thibaut, https://fabricworld.com/collections/anna-french, https://fabricworld.com/collections/baker-lifestyle, https://fabricworld.com/collections/brunschwig-fils and https://fabricworld.com/collections/caroline-cecil-textiles and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://fabricworld.com/collections/baker-lifestyle, https://fabricworld.com/collections/gaston-y-daniela and https://fabricworld.com/collections/kravet-basics took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 199 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

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix71
  • 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.

  • About 5,873 words of copy

    The homepage carries about 5,873 words of visible text.

  • Urgency cues

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

5 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Clarke & Clarke Sketch Book”, “Specials Book” and “Scalamandre Fabrics Book 1”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity and TikTok Pixel.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 18 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.

  • 26 other companies contacted

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

Apps your storefront loads

Easyban · Microsoft Clarity · Upcharge Fees · amazonaws.com · kxcdn.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

E-commerce
Shopify
Analytics
Google Tag Manager | 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 31 issues on fabricworld.com, including 14 speed issues, 3 SEO issues 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