Website review, no card needed

growthmentor.com logo

growthmentor.com website review

Visit site (opens in a new tab)Reviewed 31 October 202631 issues · 78 checks

This review found 31 issues worth fixing on growthmentor.com, 10 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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.6 s2.9 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.4 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
245 ms184 msMay 9Oct 24216 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026215 ms
May 16, 2026214 ms
May 23, 2026213 ms
May 30, 2026207 ms
Jun 6, 2026203 ms
Jun 13, 2026191 ms
Jun 20, 2026195 ms
Jun 27, 2026206 ms
Jul 4, 2026196 ms
Jul 11, 2026206 ms
Jul 18, 2026218 ms
Jul 25, 2026227 ms
Aug 1, 2026233 ms
Aug 8, 2026238 ms
Aug 15, 2026234 ms
Aug 22, 2026224 ms
Aug 29, 2026210 ms
Sep 5, 2026203 ms
Sep 12, 2026204 ms
Sep 19, 2026203 ms
Sep 26, 2026219 ms
Oct 3, 2026223 ms
Oct 10, 2026220 ms
Oct 17, 2026216 ms
Oct 24, 2026216 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 growthmentor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix49
  • Use efficient cache lifetimes

    5.0 s · 3.1 MB

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

  • Reduce unused JavaScript

    1.2 s · 573 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 5.0 s

    A phone's processor spends 5.0 s on main-thread work while loading, 2.6 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.0 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 797 ms

    797 ms

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

  • Facebook adds 381 ms

    381 ms

    Facebook costs a phone 381 ms of main-thread work and 269 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.

  • 18 long tasks on the main thread

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

  • TikTok adds 259 ms

    259 ms

    TikTok costs a phone 259 ms of main-thread work and 169 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.

  • 2,018 HTML elements

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

  • Reduce unused CSS

    150 ms · 11 KiB

    About 11 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

    32 KiB

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

  • Improve image delivery

    31 KiB

    3 images could be 31 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.

1 checks passed
  • Server response: 596 ms

    596 ms

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

Core Web Vitals

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

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 5.7 s

    5.7 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 203 ms

    203 ms

    Real visitors wait 203 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: 1.3 s

    1.3 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

3 checks passed
  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (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).

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 125 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 125 requests on a phone: scripts 1.5 MB (46), media 1.4 MB (2) and fonts 486 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.11 g

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

3 to fixGoogle 9796
  • 50 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 95 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (161 characters)

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

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 88 internal links, 26 external

    The homepage links to 88 pages on growthmentor.com and 26 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “You can build anything now.Getting customers is the hard part.”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Startup Mentors Who Help You Get Customers | GrowthMentor”.

  • Canonical URL set

    The canonical URL is https://www.growthmentor.com/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.growthmentor.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: 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 (4,333 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.growthmentor.com/ai-matching has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.growthmentor.com/ai-matching, https://www.growthmentor.com/customer-stories/blaine, https://www.growthmentor.com/customer-stories/minh, https://www.growthmentor.com/customer-stories/annie-chen, https://www.growthmentor.com/customer-stories/luka-karsten-breitig and https://www.growthmentor.com/customer-stories/maria-ledentsova and 5 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 50 found) and read each the way a search engine does.

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

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

Best practices

1 to fixGoogle 10093
  • 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.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 913 words of copy

    The homepage carries about 913 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: “Call”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Call”, “Why would a senior operator talk to me?” and “What happens after my first call?”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 47 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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
  • 8 trackers load before any consent

    8

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

  • 15 cookies set on arrival

    15

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

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Vue.js
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on growthmentor.com, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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