Website review, no card needed

goodearthproducts.com logo

goodearthproducts.com website review

Visit site (opens in a new tab)Reviewed 12 November 202646 issues · 88 checks

This review found 46 issues worth fixing on goodearthproducts.com, 15 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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.7 s2.4 sMay 23Nov 72.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
226 ms168 msMay 23Nov 7216 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026177 ms
May 30, 2026177 ms
Jun 6, 2026175 ms
Jun 13, 2026184 ms
Jun 20, 2026188 ms
Jun 27, 2026189 ms
Jul 4, 2026197 ms
Jul 11, 2026192 ms
Jul 18, 2026188 ms
Jul 25, 2026188 ms
Aug 1, 2026187 ms
Aug 8, 2026193 ms
Aug 15, 2026198 ms
Aug 22, 2026203 ms
Aug 29, 2026208 ms
Sep 5, 2026218 ms
Sep 12, 2026219 ms
Sep 19, 2026212 ms
Sep 26, 2026209 ms
Oct 3, 2026202 ms
Oct 10, 2026194 ms
Oct 17, 2026202 ms
Oct 24, 2026206 ms
Oct 31, 2026210 ms
Nov 7, 2026216 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 goodearthproducts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goodearthproducts.com at 0.7 s0.7 s
  2. goodearthproducts.com at 1.5 s1.5 s
  3. goodearthproducts.com at 2.2 s2.2 s
  4. goodearthproducts.com at 2.9 s2.9 s
  5. goodearthproducts.com at 3.6 s3.6 s
  6. goodearthproducts.com at 4.4 s4.4 s
  7. goodearthproducts.com at 5.1 s5.1 s
  8. goodearthproducts.com at 5.8 s5.8 s

Speed

10 to fix41
  • Reduce unused JavaScript

    4.2 s · 903 KiB

    About 903 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 273 KiB

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

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 1.8 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 (Shopify, Bold Commerce and tidio.co and others), adding 1.9 MB and 746 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    371 KiB

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

  • Shopify adds 241 ms

    241 ms

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

  • 2,750 HTML elements

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

  • tidio.co adds 106 ms

    106 ms

    tidio.co costs a phone 106 ms of main-thread work and 515 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.

  • Duplicated JavaScript

    200 ms · 37 KiB

    37 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

  • Reduce unused CSS

    180 ms · 38 KiB

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

  • Legacy JavaScript

    150 ms · 34 KiB

    Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    11 ms

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

Core Web Vitals

9 to fix50
  • 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.

  • Largest Contentful Paint: 18.8 s

    18.8 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Cumulative Layout Shift: 0.439

    0.439

    The layout shifts by 0.439 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user CLS: 0.24

    0.24

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

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

    +20%

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 16 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 555 ms

    555 ms

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

  • Total Blocking Time: 139 ms

    139 ms

    Scripts block the page for only 139 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 4.3 MB in 296 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 296 requests on a phone: scripts 1.8 MB (103), images 1.0 MB (61) and other files 1,015 KiB (102). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    GED1800_GoodEarthWipes_Mobile_x800.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).

  • 3 images far larger than shown

    82 KiB

    3 images are downloaded at several times the size a phone draws them, for example GE_Homepage_Clorox_1200x628_copy_x800.jpg at 1,200 px wide, shown at 335 px. Resized copies would save about 82 KiB.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8390
  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (5 elements)

    Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

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

  • 97 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 13 form fields without a label

    13 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “Cleaning Supplies, Janitorial, Pack & Ship, Health & Safety, Office – GoodEarth Products”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “GOODEARTH ESSENTIAL CLEANING PRODUCTS”). 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 332 internal links, 7 external

    The homepage links to 332 pages on goodearthproducts.com and 7 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://goodearthproducts.com/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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://goodearthproducts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://goodearthproducts.com/collections/office-supplies, https://goodearthproducts.com/collections/cleaning-sanitation, https://goodearthproducts.com/collections/food-service, https://goodearthproducts.com/collections/office-furniture, https://goodearthproducts.com/collections/office-machines-tech and https://goodearthproducts.com/collections/eco-friendly and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://goodearthproducts.com/pages/national-parks-promotion 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 172 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

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • A 10-field form

    Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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,613 words of copy

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

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”, “Contact Us” and “Subscribe”.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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, Hotjar and Klaviyo 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.

  • 20 cookies set on arrival

    20

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

  • 47 other companies contacted

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

Apps your storefront loads

Consentmo Gdpr · Wingify · Pumper Bundles · Klaviyo Email Marketing Sms · Orderlogic Min Max Limits · Simprosys Google Shopping Feed · Forms · Gdpr Backpack · orderlogicapp.com · boldapps.net · tidio.co · b-cdn.net · techdignity.com · nice-team.net · cloudfront.net

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

Framework
jQuery
E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on goodearthproducts.com, including 19 speed issues, 4 SEO issues and 5 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