Programmable

Website review, no card needed

younggoosepro.com logo

younggoosepro.com website review

Visit site (opens in a new tab)Reviewed 11 November 202624 issues · 69 checks

This review found 24 issues worth fixing on younggoosepro.com, 4 of them high impact, across 69 checks. The most urgent: 4,221 HTML elements. 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

Site score

84B

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

younggoosepro.com (opens in a new tab)
Full-page screenshot of younggoosepro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. younggoosepro.com at 0.6 s0.6 s
  2. younggoosepro.com at 1.3 s1.3 s
  3. younggoosepro.com at 1.9 s1.9 s
  4. younggoosepro.com at 2.6 s2.6 s
  5. younggoosepro.com at 3.2 s3.2 s
  6. younggoosepro.com at 3.8 s3.8 s
  7. younggoosepro.com at 4.5 s4.5 s
  8. younggoosepro.com at 5.1 s5.1 s

Speed

9 to fix81

  • 4,221 HTML elements

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

  • Mobile performance score: 81

    81/100

    Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, Shopify and 506.io and others), adding 894 KiB and 870 ms of main-thread time.

  • Render-blocking requests

    800 ms

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

  • route.com adds 633 ms

    633 ms

    route.com costs a phone 633 ms of main-thread work and 543 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

    569 KiB

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

  • 6 long tasks on the main thread

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

  • Reduce unused JavaScript

    512 KiB

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

  • Main-thread work: 3.0 s

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

  • Improve image delivery

    57 KiB

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

  • Reduce unused CSS

    40 KiB

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

  • Legacy JavaScript

    29 KiB

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

  • Minify CSS

    6 KiB

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

1 checks passed

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

3 to fix78

  • Time to Interactive: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

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

  • Total Blocking Time: 340 ms

    340 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.06

    0.06

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

Images and page weight

1 to fix85

  • Page weight: 2.3 MB in 228 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 228 requests on a phone: scripts 966 KiB (52), other files 799 KiB (117) and images 218 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.65 g

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

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

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9797

  • 12 text elements with low contrast

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

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

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

2 checks passed

  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("https://www.youtube.com/@ YoungGooseBiohackingBeauty")”.

  • One H1 headline

    Your <h1> is empty.

  • 33 internal links, 13 external

    The homepage links to 33 pages on younggoosepro.com and 13 external pages.

6 checks passed

  • Meta description: 155 characters

    Your meta description is 155 characters: “Discover Young Goose longevity skincare for professionals. Apply for wholesale access, expert training, treatment proto…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Young Goose for Professionals | Wholesale Longevity Skincare”.

  • Canonical URL set

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

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

AI search readiness

100

  • No llms.txt

    There is no https://younggoosepro.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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix93

  • 5 pages share a meta description

    https://younggoosepro.com/collections/all, https://younggoosepro.com/pages/contact, https://younggoosepro.com/pages/about-yg, https://younggoosepro.com/pages/registration-form and https://younggoosepro.com/blogs/podcast use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://younggoosepro.com/collections/all, https://younggoosepro.com/pages/contact, https://younggoosepro.com/pages/about-yg and https://younggoosepro.com/pages/registration-form have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

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

6 checks passed

  • Linked pages load

    7 pages of 12 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.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67

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

  • Thin social proof

    Social proof on the homepage: 44 customer or partner logos. 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.

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

    The homepage carries about 373 words of visible text.

3 checks passed

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Request Professional Access” and “Apply for a Professional Account”.

  • 4 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

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

  • 9 cookies set on arrival

    9

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

  • 14 other companies contacted

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

Apps your storefront loads

Hulk Form Builder · Minmaxify Order Limits · Helium Customer Fields · Eg Auto Add To Cart · Route Protection Tracking · Freegifts · 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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on younggoosepro.com, including 12 speed issues, 2 SEO issues and 3 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