growgrows.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, loox.io and Clarity and others), adding 824 KiB and 1.0 s of main-thread time.

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

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

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

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

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

About 158 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.

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

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

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

Polyfills for old browsers add 19 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

Your homepage downloads 4.0 MB in 227 requests on a phone: images 2.2 MB (43), scripts 796 KiB (73) and other files 748 KiB (89). Under 2 MB keeps phones on slow connections fast.

Black_Friday_GrowGrows_Sale_Assets_1.svg 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).

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your <h1> is empty.

The homepage links to 179 pages on growgrows.com and 9 external pages.

https://growgrows.com/en-us/collections/best-selling-baby-products/GrowSuits is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://growgrows.com/en-us/pages/faqs has no meta description, so Google writes the search snippet from whatever text it finds.

https://growgrows.com/collections/best-selling-baby-products and https://growgrows.com/en-us/collections/best-selling-baby-products/GrowSuits use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://growgrows.com/collections/best-selling-baby-products, whose canonical is https://growgrows.com/en-us/collections/best-selling-baby-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://growgrows.com/collections/best-selling-baby-products, https://growgrows.com/en-us/pages/reviews and https://growgrows.com/en-us/collections/best-selling-baby-products/GrowSuits have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

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

The homepage carries about 534 words of visible text.

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

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

Opening the homepage sets 28 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.