Website review, no card needed

coachfoundation.com logo

coachfoundation.com website review

Visit site (opens in a new tab)Reviewed 23 October 202643 issues · 79 checks

This review found 43 issues worth fixing on coachfoundation.com, 18 of them high impact, across 79 checks. The most urgent: page weight: 91.9 MB in 152 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.2 s1.9 sMay 2Sep 122.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.0 s
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.3 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.8 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.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 coachfoundation.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. coachfoundation.com at 0.4 s0.4 s
  2. coachfoundation.com at 0.8 s0.8 s
  3. coachfoundation.com at 1.2 s1.2 s
  4. coachfoundation.com at 1.6 s1.6 s
  5. coachfoundation.com at 1.9 s1.9 s
  6. coachfoundation.com at 2.3 s2.3 s
  7. coachfoundation.com at 2.7 s2.7 s
  8. coachfoundation.com at 3.1 s3.1 s

Speed

13 to fix50
  • Render-blocking requests

    1.4 s

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

  • Reduce unused JavaScript

    1.2 s · 242 KiB

    About 242 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Main-thread work: 4.5 s

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

  • Use efficient cache lifetimes

    150 ms · 63.5 MB

    17 files are served with short cache lifetimes, so returning visitors download them again (63.5 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (cloudflare.com, leadconnectorhq.com and Cloudflare and others), adding 90.2 MB and 133 ms of main-thread time.

  • Improve image delivery

    150 ms · 8.8 MB

    11 images could be 8.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Other Google APIs/SDKs adds 0 ms

    0 ms

    Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 79.3 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.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • leadconnectorhq.com adds 51 ms

    51 ms

    leadconnectorhq.com costs a phone 51 ms of main-thread work and 8.0 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.

  • 16 long tasks on the main thread

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

  • filesafe.space adds 0 ms

    0 ms

    filesafe.space costs a phone 0 ms of main-thread work and 2.3 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.

  • 1,669 HTML elements

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 373 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

    150 ms · 59 KiB

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

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 50. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    35 ms

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

Core Web Vitals

6 to fix59
  • Largest Contentful Paint: 56.1 s

    56.1 s

    Your largest element takes 56.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We don’t just train you—we build your entire coaching busin…”.

  • Time to Interactive: 62.0 s

    62.0 s

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

  • First Contentful Paint: 7.0 s

    7.0 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • Total Blocking Time: 321 ms

    321 ms

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

  • 6 images without width and height

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

  • 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 content (LCP) got 26% faster for real visitors

    -26%

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

  • Cumulative Layout Shift: 0.023

    0.023

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

Images and page weight

5 to fix18
  • Page weight: 91.9 MB in 152 requests

    91.9 MB

    Your homepage downloads 91.9 MB in 152 requests on a phone: media 71.2 MB (22), images 17.9 MB (26) and fonts 735 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 10.2 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    750 KiB

    3 images are downloaded at several times the size a phone draws them, for example 695b73e705b511a9f247ab7f.png at 1,152 px wide, shown at 370 px. Resized copies would save about 750 KiB.

  • 6 images in older formats

    6 images (10.3 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 26.0 g of CO₂ per visit

    26.04 g

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

Accessibility

6 to fixGoogle 8289
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 31 text elements with low contrast

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

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 7 images without alt text

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

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

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

  • 3 form fields without a label

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 7559
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“We don’t just train you—we build your entire coac…”, “We don’t just train you—we build your entire coac…” and “As Seen In”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 36 internal links, 8 external

    The homepage links to 36 pages on coachfoundation.com and 8 external pages.

2 checks passed
  • 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://coachfoundation.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://coachfoundation.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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

4 to fix41
  • 4 linked pages are broken

    Your homepage links to https://coachfoundation.com/health-coaching, https://coachfoundation.com/coaching-certifications, https://coachfoundation.com/business-coaching and https://coachfoundation.com/coaching-business, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 11 pages without a title

    https://coachfoundation.com/services, https://coachfoundation.com/free-resources, https://coachfoundation.com/success-stories, https://coachfoundation.com/about-us, https://coachfoundation.com/blog and https://coachfoundation.com/relationship-coaching and 5 others have no <title>, so Google invents the link text in results.

  • 11 pages without a meta description

    https://coachfoundation.com/services, https://coachfoundation.com/free-resources, https://coachfoundation.com/success-stories, https://coachfoundation.com/about-us, https://coachfoundation.com/blog and https://coachfoundation.com/relationship-coaching and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://coachfoundation.com/about-us and https://coachfoundation.com/blog 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 and read each the way a search engine does.

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • About 817 words of copy

    The homepage carries about 817 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 Started →” and “Get Started”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Get Started →”, “Get Started” and “Apply for Launch Accelerator”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and “Trusted by 1000+ Clients”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • 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
  • 1 tracker load before any consent

    1

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

  • 2 cookies set on arrival

    2

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 coachfoundation.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
Nuxt

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on coachfoundation.com, including 19 speed issues and 6 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