Website review, no card needed

baboontothemoon.com logo

baboontothemoon.com website review

Visit site (opens in a new tab)Reviewed 10 November 202653 issues · 92 checks

This review found 53 issues worth fixing on baboontothemoon.com, 24 of them high impact, across 92 checks. The most urgent: unpkg adds 1.0 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
4.8 s2.8 sMay 23Nov 73.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.6 s
Jun 27, 20263.8 s
Jul 4, 20264.0 s
Jul 11, 20264.4 s
Jul 18, 20264.6 s
Jul 25, 20264.5 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.4 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.3 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.0 s
Oct 31, 20263.9 s
Nov 7, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
319 ms254 msMay 23Nov 7284 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026270 ms
May 30, 2026292 ms
Jun 6, 2026308 ms
Jun 13, 2026302 ms
Jun 20, 2026311 ms
Jun 27, 2026304 ms
Jul 4, 2026297 ms
Jul 11, 2026310 ms
Jul 18, 2026306 ms
Jul 25, 2026304 ms
Aug 1, 2026287 ms
Aug 8, 2026279 ms
Aug 15, 2026266 ms
Aug 22, 2026261 ms
Aug 29, 2026267 ms
Sep 5, 2026278 ms
Sep 12, 2026279 ms
Sep 19, 2026281 ms
Sep 26, 2026283 ms
Oct 3, 2026279 ms
Oct 10, 2026270 ms
Oct 17, 2026273 ms
Oct 24, 2026287 ms
Oct 31, 2026281 ms
Nov 7, 2026284 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 baboontothemoon.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baboontothemoon.com at 1.1 s1.1 s
  2. baboontothemoon.com at 2.3 s2.3 s
  3. baboontothemoon.com at 3.4 s3.4 s
  4. baboontothemoon.com at 4.5 s4.5 s
  5. baboontothemoon.com at 5.6 s5.6 s
  6. baboontothemoon.com at 6.8 s6.8 s
  7. baboontothemoon.com at 7.9 s7.9 s
  8. baboontothemoon.com at 9.0 s9.0 s

Speed

11 to fix46
  • Unpkg adds 1.0 s

    1.0 s

    Unpkg costs a phone 1.0 s of main-thread work and 32 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 6.0 s

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

  • 4,096 HTML elements

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

  • Improve image delivery

    1.8 MB

    15 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Unpkg, Klaviyo and LoyaltyLion and others), adding 1.3 MB and 1.4 s of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    393 KiB

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

  • 12 long tasks on the main thread

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

  • LoyaltyLion adds 74 ms

    74 ms

    LoyaltyLion costs a phone 74 ms of main-thread work and 353 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 58 ms

    58 ms

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

    150 KiB

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

  • Legacy JavaScript

    58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    36 KiB

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

  • 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

11 to fix67
  • 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 LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 8.9 s

    8.9 s

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

  • Time to Interactive: 22.0 s

    22.0 s

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

  • Total Blocking Time: 889 ms

    889 ms

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • 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

2 to fix64
  • Page weight: 6.2 MB in 377 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 377 requests on a phone: images 3.3 MB (56), scripts 1.4 MB (142) and other files 1.2 MB (164). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • About 1.8 g of CO₂ per visit

    1.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.5 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 are sized for phones

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

Accessibility

16 to fixGoogle 8581
  • Required ARIA attributes must be provided (5 elements)

    Required ARIA attributes must be provided: 5 elements on the page fail this check, rated critical by axe-core.

  • Malformed lists

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

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 18 images without alt text

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

  • Heading levels should only increase by one (5 elements)

    Heading levels should only increase by one: 5 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 43 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: 43 passed and 15 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 8 internal links, 1 external

    The homepage links to 8 pages on baboontothemoon.com and 1 external page.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “BABOON TO THE MOON is an adventure brand - we make versatile, technical and radical bags. All with a lifetime warranty …”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “BABOON TO THE MOON | Bags for Adventure”.

  • Canonical URL set

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

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    14%

    A phone browser shows 630 words, but the HTML your server sends has only 91. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

2 to fix90
  • 1 page without a meta description

    https://baboontothemoon.com/pages/rewards has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://baboontothemoon.com/pages/rewards and https://baboontothemoon.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://baboontothemoon.com/collections/all has 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.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    2 pages of 3 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 2 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 10 broken images

    10 images failed to load on a phone, for example https://baboontothemoon.com/.

  • 6 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • About 630 words of copy

    The homepage carries about 630 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop” and “Shop All”.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 33 cookies set on arrival

    33

    Opening the homepage sets 33 cookies, 1 of them by other companies (measured from a US location before any click).

  • 52 other companies contacted

    Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 baboontothemoon.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on baboontothemoon.com, including 22 speed issues, 3 SEO issues and 4 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