Website review, no card needed

spacegoods.com logo

spacegoods.com website review

Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 86 checks

This review found 42 issues worth fixing on spacegoods.com, 14 of them high impact, across 86 checks. The most urgent: main-thread work: 15.8 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
5.0 s3.8 sMay 16Oct 313.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.1 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.2 s
Jul 11, 20264.4 s
Jul 18, 20264.7 s
Jul 25, 20264.9 s
Aug 1, 20264.9 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.3 s
Aug 29, 20264.2 s
Sep 5, 20264.0 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.0 s
Oct 31, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
278 ms201 msMay 16Oct 31228 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026246 ms
May 23, 2026249 ms
May 30, 2026257 ms
Jun 6, 2026264 ms
Jun 13, 2026269 ms
Jun 20, 2026266 ms
Jun 27, 2026258 ms
Jul 4, 2026251 ms
Jul 11, 2026239 ms
Jul 18, 2026230 ms
Jul 25, 2026225 ms
Aug 1, 2026219 ms
Aug 8, 2026213 ms
Aug 15, 2026211 ms
Aug 22, 2026210 ms
Aug 29, 2026212 ms
Sep 5, 2026218 ms
Sep 12, 2026221 ms
Sep 19, 2026221 ms
Sep 26, 2026221 ms
Oct 3, 2026218 ms
Oct 10, 2026214 ms
Oct 17, 2026219 ms
Oct 24, 2026223 ms
Oct 31, 2026228 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 spacegoods.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. spacegoods.com at 1.4 s1.4 s
  2. spacegoods.com at 2.7 s2.7 s
  3. spacegoods.com at 4.1 s4.1 s
  4. spacegoods.com at 5.4 s5.4 s
  5. spacegoods.com at 6.8 s6.8 s
  6. spacegoods.com at 8.1 s8.1 s
  7. spacegoods.com at 9.5 s9.5 s
  8. spacegoods.com at 10.9 s10.9 s

Speed

12 to fix36
  • Main-thread work: 15.8 s

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 36

    36/100

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

  • 5,814 HTML elements

    The page has 5,814 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, loox.io and trackcollect.com and others), adding 2.5 MB and 1.3 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Reduce unused JavaScript

    300 ms · 502 KiB

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

  • Use efficient cache lifetimes

    500 ms · 189 KiB

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

  • Google Tag Manager adds 567 ms

    567 ms

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

    359 KiB

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

  • loox.io adds 318 ms

    318 ms

    loox.io costs a phone 318 ms of main-thread work and 27 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 36 ms

    36 ms

    Shopify costs a phone 36 ms of main-thread work and 1.2 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

    150 ms · 42 KiB

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

  • Duplicated JavaScript

    29 KiB

    29 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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: 22 ms

    22 ms

    Your server sent the HTML in 22 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.

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person relaxing in bed with Sleep+ Magnesium and a mug of h…”.

  • Time to Interactive: 17.0 s

    17.0 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Speed Index: 9.7 s

    9.7 s

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

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

    228 ms

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 801 ms

    801 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 246 ms to 228 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-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 8.2 MB in 539 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 539 requests on a phone: media 3.0 MB (1), images 2.3 MB (276) and scripts 1.7 MB (136). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    3 KiB

    1 image is downloaded at several times the size a phone draws it, for example 1RTD_Banner_Image_Mobile_3x-100_2.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 3 KiB.

  • About 2.3 g of CO₂ per visit

    2.32 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

Accessibility

7 to fixGoogle 8891
  • 6 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

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

  • 159 internal links, 28 external

    The homepage links to 159 pages on spacegoods.com and 28 external pages.

7 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Spacegoods | Unlock Your Full Potential All-in-one functional super blends designed to help you feel &amp; perform your…”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Spacegoods | Unlock Your Full Potential”.

  • Canonical URL set

    The canonical URL is https://spacegoods.com/en-us.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://spacegoods.com/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix74
  • 3 linked pages hidden from search

    https://spacegoods.com/en-us/products/astro-dust-sample-pack, https://spacegoods.com/en-us/products/hydro-dust and https://spacegoods.com/en-us/products/glow-dust are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://spacegoods.com/en-us/collections/sale and https://spacegoods.com/collections/sale all use the title “Mushroom Coffee Sale - Discounts & Offers - Spacegoods”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://spacegoods.com/en-us/collections/sale and https://spacegoods.com/collections/sale use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

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

  • 14 pages without an H1

    https://spacegoods.com/en-us/products/sleep-plus-starter-kit, https://spacegoods.com/en-us/collections/sale, https://spacegoods.com/products/oat-mushroom-latte, https://spacegoods.com/en-us/collections/bundles, https://spacegoods.com/en-us/products/matcha-dust-starter-kit and https://spacegoods.com/en-us/products/hydro-dust-starter-kit and 8 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 46 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET STARTED NOW GET STARTED NOW”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “SHOP BUNDLESSHOP BUNDLESSHOP BUNDLES”, “GET STARTED” and “SHOP ALL”.

  • 8 short forms

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

  • Social proof on the page

    Social proof on the homepage: 75 testimonial or review blocks, a star rating, 9 trust badges and “1M+ Happy Customers”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 29 cookies set on arrival

    29

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

  • 51 other companies contacted

    Loading the homepage contacts 51 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 spacegoods.com, 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
Google Analytics
Hosting
Shopify

Company

Headquarters
London

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 spacegoods.com, including 23 speed issues and 2 SEO issues. 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