fuliage.com website review

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

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

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

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

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

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

7 third-party services load with your homepage (Clarity, Shopify and okendo.io and others), adding 662 KiB and 316 ms of main-thread time.

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

About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 220 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fuliage | Complete Plant Care Trio - Best Organic Fertilize…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.3 MB in 308 requests on a phone: other files 990 KiB (148), scripts 647 KiB (115) and images 582 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

7 tap targets are too small or too close together to hit reliably with a finger.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Fuliage | Organic Liquid Plant Food and Pest Control for House Plants”.

There are 4 <h1> headlines (“Your cart -”, “” and “”). One clear main headline is easier for people and search engines.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 52 pages on fuliage.com and 8 external pages.

https://fuliage.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://fuliage.com/products/wholesale and https://fuliage.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://fuliage.com/policies/shipping-policy, https://fuliage.com/pages/faqs, https://fuliage.com/customer_authentication/redirect and https://fuliage.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://fuliage.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus/css/okendo-reviews-styles.ffe4027a.css' f…”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 992 words of visible text.

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

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

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.

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