Website review, no card needed

downtoground.co logo

downtoground.co website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 84 checks

This review found 36 issues worth fixing on downtoground.co, 14 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
3.3 s2.2 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20263.0 s
Jul 25, 20263.2 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20262.6 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.6 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.1 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
1.3 s214 msMay 16Oct 311.2 s
Show as table
DateReal-visitor tap response (INP)
May 16, 2026338 ms
May 23, 2026354 ms
May 30, 2026361 ms
Jun 6, 2026386 ms
Jun 13, 2026409 ms
Jun 20, 2026444 ms
Jun 27, 2026532 ms
Jul 4, 2026536 ms
Jul 11, 2026553 ms
Jul 18, 2026563 ms
Jul 25, 2026561 ms
Aug 1, 2026563 ms
Aug 8, 2026527 ms
Aug 15, 2026487 ms
Aug 22, 2026504 ms
Aug 29, 2026531 ms
Sep 5, 2026563 ms
Sep 12, 2026630 ms
Sep 19, 2026658 ms
Sep 26, 2026714 ms
Oct 3, 2026800 ms
Oct 10, 2026832 ms
Oct 17, 2026909 ms
Oct 24, 20261.0 s
Oct 31, 20261.2 s

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 downtoground.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. downtoground.co at 1.7 s1.7 s
  2. downtoground.co at 3.4 s3.4 s
  3. downtoground.co at 5.1 s5.1 s
  4. downtoground.co at 6.8 s6.8 s
  5. downtoground.co at 8.4 s8.4 s
  6. downtoground.co at 10.1 s10.1 s
  7. downtoground.co at 11.8 s11.8 s
  8. downtoground.co at 13.5 s13.5 s

Speed

14 to fix30
  • Render-blocking requests

    2.4 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

  • Main-thread work: 16.0 s

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

  • Mobile performance score: 30

    30/100

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

  • 7,687 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Convert Insights and ContentSquare and others), adding 1.9 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 921 KiB

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

  • Use efficient cache lifetimes

    700 ms · 638 KiB

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

  • Google Tag Manager adds 730 ms

    730 ms

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

  • 20 long tasks on the main thread

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

  • Convert Insights adds 590 ms

    590 ms

    Convert Insights costs a phone 590 ms of main-thread work and 76 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.

  • ContentSquare adds 477 ms

    477 ms

    ContentSquare costs a phone 477 ms of main-thread work and 195 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.

  • Reduce unused CSS

    300 ms · 75 KiB

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

  • Facebook adds 321 ms

    321 ms

    Facebook costs a phone 321 ms of main-thread work and 262 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.

  • Shopify adds 291 ms

    291 ms

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

  • Improve image delivery

    200 ms · 37 KiB

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

  • Legacy JavaScript

    150 ms · 74 KiB

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 24 ms

    24 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user INP: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “50,000+ Happy Customers Heal Your Body Naturally Premium gr…”.

  • Time to Interactive: 30.2 s

    30.2 s

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

  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

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

    +219%

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 481 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 481 requests on a phone: scripts 2.5 MB (155), other files 1.4 MB (273) and images 606 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (79 KiB) are 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 1.5 g of CO₂ per visit

    1.45 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8996
  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • 3 text elements with low contrast

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

  • 1 link without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 181 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 3 H1 headlines

    There are 3 <h1> headlines (“Grounding Mattress Cover”, “Grounding Trainers” and “Heal Your Body Naturally”). One clear main headline is easier for people and search engines.

  • 70 internal links, 1 external

    The homepage links to 70 pages on downtoground.co and 1 external page.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Buy premium quality indoor grounding products from Down To Ground™. Experience the healing power of earthing to reduce …”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Down To Ground™ | Official Earthing & Grounding Products”.

  • Canonical URL set

    The canonical URL is https://downtoground.co/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (3,005 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://downtoground.co/collections/bundles, https://downtoground.co/products/deep-sleep-bundle, https://downtoground.co/products/cool-sleep-bundle and https://downtoground.co/products/pet-parent-bundle have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://downtoground.co/collections/products, https://downtoground.co/products/onearthing-mattress-cover, https://downtoground.co/collections/bundles, https://downtoground.co/products/dtg-01-grounding-shoes, https://downtoground.co/products/grounding-mat and https://downtoground.co/products/grounding-pillow-cover and 9 others have 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 22 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 7391
  • 1 third-party cookie

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “EF is not defined”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    14 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,256 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Products”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop All”, “Shop Now” and “SHOP THIS BUNDLE”.

  • 13 short forms

    13 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 110 testimonial or review blocks and “50,000+ Happy Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 55 cookies set on arrival

    55

    Opening the homepage sets 55 cookies, 2 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.

  • 63 other companies contacted

    Loading the homepage contacts 63 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 downtoground.co, 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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Black Crow Ai That Delivers · Triplewhale · Simprosys Google Shopping Feed · Postscript Sms Marketing · Contentsquare Analytics · Gorgias Live Chat Helpdesk · Growi Creator Management · Judge Me Reviews · Convert Experiences · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Convert Web Pixel · Applovin Shop Integration · Test Sms · Freegifts · trustpilot.com · goaffpro.com · bogos.io

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

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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 downtoground.co, including 25 speed issues and 1 SEO issue. 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