Website review, no card needed

thegoutlie.com logo

thegoutlie.com website review

Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 77 checks

This review found 30 issues worth fixing on thegoutlie.com, 8 of them high impact, across 77 checks. The most urgent: avoid multiple page redirects. 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

Full-page screenshot of thegoutlie.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thegoutlie.com at 0.4 s0.4 s
  2. thegoutlie.com at 0.8 s0.8 s
  3. thegoutlie.com at 1.1 s1.1 s
  4. thegoutlie.com at 1.5 s1.5 s
  5. thegoutlie.com at 1.9 s1.9 s
  6. thegoutlie.com at 2.3 s2.3 s
  7. thegoutlie.com at 2.6 s2.6 s
  8. thegoutlie.com at 3.0 s3.0 s

Speed

10 to fix79
  • Avoid multiple page redirects

    10.1 s

    The page goes through 1 redirect before it starts loading, costing about 10.1 s. Link and advertise the final URL directly.

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 1.8 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 (cloudfront.net, Klaviyo and Shopify and others), adding 2.2 MB and 993 ms of main-thread time.

  • Mobile performance score: 79

    79/100

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

  • Reduce unused JavaScript

    817 KiB

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

  • Use efficient cache lifetimes

    300 ms · 487 KiB

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

  • cloudfront.net adds 380 ms

    380 ms

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

  • Render-blocking requests

    400 ms

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

  • Klaviyo adds 138 ms

    138 ms

    Klaviyo costs a phone 138 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.

  • zipify.com adds 56 ms

    56 ms

    zipify.com costs a phone 56 ms of main-thread work and 538 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.

  • 12 long tasks on the main thread

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

  • Reduce unused CSS

    60 KiB

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

  • Legacy JavaScript

    53 KiB

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

  • Minify JavaScript

    40 KiB

    40 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    36 KiB

    1 image could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    9 ms

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

Core Web Vitals

4 to fix87
  • Time to Interactive: 23.5 s

    23.5 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 392 ms

    392 ms

    Scripts block taps and scrolling for 392 ms in total while the page loads. Good is under 200 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.

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

2 checks passed
  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “It Steals Your Life from You.”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 359 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 359 requests on a phone: scripts 2.0 MB (159), other files 1.1 MB (157) and images 467 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.20 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 143.6 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

6 to fixGoogle 8991
  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

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

    All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 2 links without text

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

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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 9287
  • Canonical points to another host

    Your canonical URL points to reddremedies.com, not thegoutlie.com, so Google may credit that host instead.

  • Meta description is long (165 characters)

    Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://reddremedies.com/)”.

  • 172 internal links, 7 external

    The homepage links to 172 pages on thegoutlie.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Master Herbalist Crafted Natural Supplements”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Redd Remedies | Putting Health In Order”.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    41%

    The HTML your server sends has 672 of the 1,649 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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: 5 of 6 facts

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9674
  • 2 broken images

    2 images failed to load on a phone, for example https://thegoutlie.com/pages/the-gout-lie-official-book-launch?_su_rec=TSMcVwSJc_z68tYOfvgoi5qkARagqdvTlFcpe9JxlGnZpWhnF19YJI-5ULIArmn8deJnYtsBPI903rImUb8wby8Mo-UzNvoH4NwX4p22QShjJH1uCTadQCOFfGgZNEjwE.

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get the Book”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop All Best Sellers”, “Shop” and “Shop All”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 25 cookies set on arrival

    25

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

  • 54 other companies contacted

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

Apps your storefront loads

Triplewhale · Patrol · Klaviyo Email Marketing Sms · Crazy Egg · Judge Me Reviews · Zipify Oneclickupsell · Repete Reorder · nice-team.net · zooomyapps.com · amazonaws.com · shareasale.com · cloudfront.net · rechargecdn.com · postscript.io · cart-bot.net · superfiliate-cdn.com

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
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on thegoutlie.com, including 14 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