Website review, no card needed

grove.co logo

grove.co website review

Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 77 checks

This review found 36 issues worth fixing on grove.co, 13 of them high impact, across 77 checks. The most urgent: main-thread work: 12.3 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.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
239 ms152 msMay 16Oct 31214 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026162 ms
May 23, 2026162 ms
May 30, 2026163 ms
Jun 6, 2026168 ms
Jun 13, 2026171 ms
Jun 20, 2026171 ms
Jun 27, 2026171 ms
Jul 4, 2026171 ms
Jul 11, 2026171 ms
Jul 18, 2026171 ms
Jul 25, 2026170 ms
Aug 1, 2026169 ms
Aug 8, 2026170 ms
Aug 15, 2026171 ms
Aug 22, 2026172 ms
Aug 29, 2026179 ms
Sep 5, 2026180 ms
Sep 12, 2026184 ms
Sep 19, 2026187 ms
Sep 26, 2026188 ms
Oct 3, 2026193 ms
Oct 10, 2026204 ms
Oct 17, 2026217 ms
Oct 24, 2026229 ms
Oct 31, 2026214 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 grove.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grove.co at 1.3 s1.3 s
  2. grove.co at 2.7 s2.7 s
  3. grove.co at 4.0 s4.0 s
  4. grove.co at 5.3 s5.3 s
  5. grove.co at 6.7 s6.7 s
  6. grove.co at 8.0 s8.0 s
  7. grove.co at 9.3 s9.3 s
  8. grove.co at 10.7 s10.7 s

Speed

10 to fix45
  • Main-thread work: 12.3 s

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,115 HTML elements

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

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

  • 8 third-party services on the page

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

  • Shopify adds 357 ms

    357 ms

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

  • Reduce unused JavaScript

    529 KiB

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

  • Improve image delivery

    486 KiB

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

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 363 ms

    363 ms

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

  • Use efficient cache lifetimes

    111 KiB

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

  • Reduce unused CSS

    28 KiB

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

  • Legacy JavaScript

    7 KiB

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

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

    29 ms

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

Core Web Vitals

8 to fix100
  • 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: 19.0 s

    19.0 s

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

  • Total Blocking Time: 2.3 s

    2.3 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A lifestyle scene of a father and two young children washin…”.

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

    +37%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

6 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 152 ms

    152 ms

    Real visitors wait 152 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.

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

    -15%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 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 fix67
  • Page weight: 3.9 MB in 237 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 237 requests on a phone: images 1.6 MB (65), scripts 1.0 MB (59) and other files 894 KiB (106). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.10 g

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

Accessibility

5 to fixGoogle 8093
  • Images must have alternative text (83 elements)

    Images must have alternative text: 83 elements on the page fail this check, rated critical by axe-core.

  • 8 tap targets too small

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

  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 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. (5 elements).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9286
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 1,705 internal links, 5 external

    The homepage links to 1,705 pages on grove.co and 5 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Grove makes a healthier home easy. Shop vetted cleaning, personal care, vitamins and kitchen essentials screened agains…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Healthier Home Essentials | Grove Collaborative”.

  • Canonical URL set

    The canonical URL is https://www.grove.co/.

  • 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.grove.co/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.grove.co/pages/our-mission, https://www.grove.co/pages/beyond-plastic, https://www.grove.co/pages/environmental-impact, https://www.grove.co/pages/ingredient-standards, https://www.grove.co/blogs/blog and https://www.grove.co/pages/essentials have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.grove.co/pages/our-mission, https://www.grove.co/pages/beyond-plastic, https://www.grove.co/pages/environmental-impact, https://www.grove.co/pages/ingredient-standards, https://www.grove.co/blogs/blog and https://www.grove.co/pages/green-rewards and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.grove.co/pages/our-mission, https://www.grove.co/pages/beyond-plastic, https://www.grove.co/pages/environmental-impact, https://www.grove.co/pages/ingredient-standards, https://www.grove.co/blogs/blog and https://www.grove.co/pages/green-rewards and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.grove.co/.

  • 36 small tap targets

    36 of 125 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 “SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin "null" from access…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

  • About 1,175 words of copy

    The homepage carries about 1,175 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “The Unplastic Shop” and “open The Unplastic Shop menu”.

  • 239 calls to action

    The homepage has 239 calls to action, for example “Order History”, “The Unplastic Shop” and “Shop All”.

  • 1 short form

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

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, The Trade Desk 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.

  • 17 cookies set on arrival

    17

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 grove.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Heap | Microsoft Clarity
Hosting
Cloudflare

Hiring

Hiring
6 open roles
Teams
Packing & Shipping (3), Fulfillment Operations (1), Inbound, Receiving & Support (1), Inventory (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on grove.co, including 18 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