Website review, no card needed

goodearth.in logo

goodearth.in website review

Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 85 checks

This review found 42 issues worth fixing on goodearth.in, 15 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
6.3 s4.5 sMay 9Oct 244.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.8 s
Jun 6, 20264.9 s
Jun 13, 20265.1 s
Jun 20, 20265.4 s
Jun 27, 20265.5 s
Jul 4, 20265.5 s
Jul 11, 20265.5 s
Jul 18, 20265.5 s
Jul 25, 20265.4 s
Aug 1, 20265.5 s
Aug 8, 20265.5 s
Aug 15, 20265.4 s
Aug 22, 20265.6 s
Aug 29, 20265.8 s
Sep 5, 20265.9 s
Sep 12, 20266.0 s
Sep 19, 20266.0 s
Sep 26, 20265.6 s
Oct 3, 20265.2 s
Oct 10, 20265.0 s
Oct 17, 20264.7 s
Oct 24, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
295 ms254 msMay 9Oct 24282 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026270 ms
May 16, 2026266 ms
May 23, 2026268 ms
May 30, 2026266 ms
Jun 6, 2026260 ms
Jun 13, 2026259 ms
Jun 20, 2026260 ms
Jun 27, 2026259 ms
Jul 4, 2026262 ms
Jul 11, 2026265 ms
Jul 18, 2026267 ms
Jul 25, 2026270 ms
Aug 1, 2026272 ms
Aug 8, 2026274 ms
Aug 15, 2026279 ms
Aug 22, 2026285 ms
Aug 29, 2026284 ms
Sep 5, 2026288 ms
Sep 12, 2026289 ms
Sep 19, 2026290 ms
Sep 26, 2026284 ms
Oct 3, 2026279 ms
Oct 10, 2026277 ms
Oct 17, 2026275 ms
Oct 24, 2026282 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 goodearth.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goodearth.in at 1.0 s1.0 s
  2. goodearth.in at 2.0 s2.0 s
  3. goodearth.in at 3.0 s3.0 s
  4. goodearth.in at 4.0 s4.0 s
  5. goodearth.in at 5.0 s5.0 s
  6. goodearth.in at 6.0 s6.0 s
  7. goodearth.in at 7.1 s7.1 s
  8. goodearth.in at 8.1 s8.1 s

Speed

9 to fix47
  • Use efficient cache lifetimes

    1.9 s · 542 KiB

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

  • Reduce unused JavaScript

    1.1 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Improve image delivery

    1.1 s · 300 KiB

    2 images could be 300 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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.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 (maker.co, Google Tag Manager and posthog.com and others), adding 3.5 MB and 1.4 s of main-thread time.

  • maker.co adds 595 ms

    595 ms

    maker.co costs a phone 595 ms of main-thread work and 1.3 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.

  • Google Tag Manager adds 505 ms

    505 ms

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

  • cloudfront.net adds 53 ms

    53 ms

    cloudfront.net costs a phone 53 ms of main-thread work and 1.5 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 CSS

    232 KiB

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

  • 14 long tasks on the main thread

    14 long tasks block the main thread while loading, the longest for 207 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).

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

    255 ms

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

Core Web Vitals

10 to fix0
  • 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: 10.5 s

    10.5 s

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

  • Speed Index: 16.6 s

    16.6 s

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

  • Time to Interactive: 27.7 s

    27.7 s

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

  • Total Blocking Time: 725 ms

    725 ms

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user INP: 279 ms

    279 ms

    Real visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.15

    0.15

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user FCP: 1.6 s

    1.6 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

3 to fix53
  • Page weight: 12.7 MB in 125 requests

    12.7 MB

    Your homepage downloads 12.7 MB in 125 requests on a phone: media 7.8 MB (1), scripts 2.4 MB (36) and images 1.3 MB (22). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    427 KiB

    4 images are downloaded at several times the size a phone draws them, for example Loader.9b7193f13770ad4f9b6b477e3ed82b6d.gif at 500 px wide, shown at 150 px. Resized copies would save about 427 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (437 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (317 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 3.6 g of CO₂ per visit

    3.59 g

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

Accessibility

7 to fixGoogle 7888
  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 5 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

  • 4 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 29 internal links, 5 external

    The homepage links to 29 pages on goodearth.in and 5 external pages.

5 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Good Earth – Luxury Indian Design House Explore handcrafted designs that celebrate style from an Indian perspective”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Good Earth – Stylish Sustainable Luxury Retail | Goodearth.in”.

  • Canonical URL set

    The canonical URL is https://www.goodearth.in/.

  • 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.goodearth.in/sitemap.xml.

AI search readiness

1 to fix83
  • 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.goodearth.in/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.

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

Other pages

4 to fix81
  • 8 pages share a title

    /, https://www.goodearth.in/catalogue/category/living/dining_28, https://www.goodearth.in/catalogue/category/gifting/new-gifting_581, https://www.goodearth.in/wishlist, https://www.goodearth.in/careers and https://www.goodearth.in/Cafe-Shop/Delhi and 2 others all use the title “Good Earth – Stylish Sustainable Luxury Retail | Goodearth.in”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.goodearth.in/our-world/about/our-journey and https://www.goodearth.in/our-world/in-the-media have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.goodearth.in/catalogue/category/living/dining_28, https://www.goodearth.in/catalogue/category/gifting/new-gifting_581, https://www.goodearth.in/category_landing/women_1, https://www.goodearth.in/wishlist, https://www.goodearth.in/customer-assistance/privacy-policy and https://www.goodearth.in/careers and 4 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.goodearth.in/catalogue/category/living/dining_28, https://www.goodearth.in/catalogue/category/gifting/new-gifting_581, https://www.goodearth.in/category_landing/living_26, https://www.goodearth.in/category_landing/women_1, https://www.goodearth.in/category_landing/gifting_373 and https://www.goodearth.in/our-world and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.goodearth.in/our-world, https://www.goodearth.in/our-world/about/our-journey and https://www.goodearth.in/our-world/in-the-media 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.

  • 2 pages slow to respond

    https://www.goodearth.in/category_landing/living_26 and https://www.goodearth.in/category_landing/women_1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 9287
  • 11 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

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

  • Only about 134 words

    The homepage has only about 134 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Track Order”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Track Order” and “Shop & Cafe Locator”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 10 cookies set on arrival

    10

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

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on goodearth.in, including 19 speed issues, 3 SEO issues and 2 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