Website review, no card needed

findgrowthtools.com logo

findgrowthtools.com website review

Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 77 checks

This review found 26 issues worth fixing on findgrowthtools.com, 7 of them high impact, across 77 checks. The most urgent: certain ARIA roles must contain particular children (1 element). 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 findgrowthtools.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix73
  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    810 ms · 131 KiB

    About 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 810 ms faster on a phone.

  • Render-blocking requests

    700 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts and others), adding 289 KiB and 140 ms of main-thread time.

  • Font display

    150 ms

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    100 ms · 16 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

  • Reduce unused CSS

    91 KiB

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

  • Duplicated JavaScript

    14 KiB

    14 KiB JavaScript is shipped twice across bundles.

  • Improve image delivery

    6 KiB

    1 image could be 6 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 385 ms of it running JavaScript. That is comfortably low.

  • Server response: 63 ms

    63 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 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.

3 checks passed
  • Total Blocking Time: 182 ms

    182 ms

    Scripts block the page for only 182 ms while loading. Good is under 200 ms.

  • Speed Index: 2.1 s

    2.1 s

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

  • Cumulative Layout Shift: 0.029

    0.029

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.19 g

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

4 checks passed
  • Page weight: 690 KiB in 18 requests

    690 KiB

    Your homepage downloads 690 KiB in 18 requests on a phone: scripts 373 KiB (7), fonts 165 KiB (5) and HTML 117 KiB (1). That is a lean page.

  • 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

11 to fixGoogle 7383
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • 85 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 43 elements on the page fail 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 form fields without a label

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

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 10088
  • No structured data

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

  • No canonical URL

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

  • No robots.txt

    There is no robots.txt at findgrowthtools.com/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 35 internal links, 3 external

    The homepage links to 35 pages on findgrowthtools.com and 3 external pages.

4 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “A curated list of the best SaaS tools to help your company grow. Discover growth tools by category, growth lever, integ…”.

  • One H1 headline

    Your main headline reads: “Find the best SaaS tools to help your company grow.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Find Growth Tools | The Best SaaS Tools To Help Startups Grow”.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.findgrowthtools.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://www.findgrowthtools.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.findgrowthtools.com/growthlevers, https://www.findgrowthtools.com/suggest and https://www.findgrowthtools.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages with very little text

    https://www.findgrowthtools.com/categories, https://www.findgrowthtools.com/growthlevers, https://www.findgrowthtools.com/integrations, https://www.findgrowthtools.com/customers, https://www.findgrowthtools.com/about and https://www.findgrowthtools.com/suggest and 1 other have 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.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    8 of 8 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 558 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Subscribe”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and 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.

  • 4 cookies set on arrival

    4

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 findgrowthtools.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
React
Analytics
Google Analytics
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on findgrowthtools.com, including 6 speed issues, 3 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