Website review, no card needed

fabuliv.com logo

fabuliv.com website review

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

This review found 29 issues worth fixing on fabuliv.com, 6 of them high impact, across 78 checks. The most urgent: main-thread work: 4.0 s. 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.3 s1.8 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
193 ms160 msMay 16Oct 31189 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026165 ms
May 23, 2026164 ms
May 30, 2026170 ms
Jun 6, 2026176 ms
Jun 13, 2026178 ms
Jun 20, 2026177 ms
Jun 27, 2026178 ms
Jul 4, 2026172 ms
Jul 11, 2026171 ms
Jul 18, 2026173 ms
Jul 25, 2026173 ms
Aug 1, 2026175 ms
Aug 8, 2026178 ms
Aug 15, 2026178 ms
Aug 22, 2026175 ms
Aug 29, 2026176 ms
Sep 5, 2026179 ms
Sep 12, 2026179 ms
Sep 19, 2026183 ms
Sep 26, 2026183 ms
Oct 3, 2026177 ms
Oct 10, 2026178 ms
Oct 17, 2026181 ms
Oct 24, 2026184 ms
Oct 31, 2026189 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 fabuliv.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fabuliv.com at 0.4 s0.4 s
  2. fabuliv.com at 0.9 s0.9 s
  3. fabuliv.com at 1.3 s1.3 s
  4. fabuliv.com at 1.8 s1.8 s
  5. fabuliv.com at 2.2 s2.2 s
  6. fabuliv.com at 2.6 s2.6 s
  7. fabuliv.com at 3.1 s3.1 s
  8. fabuliv.com at 3.5 s3.5 s

Speed

7 to fix66
  • Main-thread work: 4.0 s

    A phone's processor spends 4.0 s on main-thread work while loading, 1.9 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, razorpay.com and loox.io and others), adding 1.7 MB and 1.1 s of main-thread time.

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    150 ms · 527 KiB

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

  • Google Tag Manager adds 471 ms

    471 ms

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

  • Render-blocking requests

    300 ms

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

  • razorpay.com adds 182 ms

    182 ms

    razorpay.com costs a phone 182 ms of main-thread work and 920 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.

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    215 KiB

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

  • Improve image delivery

    79 KiB

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

  • Reduce unused CSS

    56 KiB

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

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 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: 9 ms

    9 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 17.3 s

    17.3 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stores in Delhi I Gurgaon I Dehradun”. Most of its time is element render delay (2.5 s).

  • Total Blocking Time: 447 ms

    447 ms

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

  • 1 image without width and height

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

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

    1.5 s

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

  • Real-user INP: 144 ms

    144 ms

    Real visitors wait 144 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 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: 661 ms

    661 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.5 MB in 405 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 405 requests on a phone: other files 1.4 MB (266), scripts 1.4 MB (78) and images 313 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Sale_mobile_banner001diwalipdp2631.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (62 KiB) 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 1.0 g of CO₂ per visit

    1.00 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8895
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

  • 40 links without text

    40 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 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 116 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 2 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
  • Meta description is long (173 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 188 internal links, 8 external

    The homepage links to 188 pages on fabuliv.com and 8 external pages.

6 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Buy Handcrafted Solid Wood Furniture Online I Fabuliv”.

  • Canonical URL set

    The canonical URL is https://www.fabuliv.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://www.fabuliv.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.fabuliv.com/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.

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.fabuliv.com/collections/bedroom has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.fabuliv.com/collections/beds has 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 67 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • 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 4 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6991
  • 1 third-party cookie

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

  • Only about 108 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 “Contact Us” and “Subscribe”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 19 cookies set on arrival

    19

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

  • 39 other companies contacted

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

Apps your storefront loads

C Hub Customer Accounts · Microsoft Clarity · mageworx.com · loox.io · hulkapps.com · zoko.io · amazonaws.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

  • The footer still says © 2018.

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Gurugram

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on fabuliv.com, including 13 speed issues, 2 SEO issues and 3 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