Website review, no card needed

saas-founders.com logo

saas-founders.com website review

Visit site (opens in a new tab)Reviewed 11 November 202630 issues · 67 checks

This review found 30 issues worth fixing on saas-founders.com, 11 of them high impact, across 67 checks. The most urgent: improve image delivery. 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 saas-founders.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saas-founders.com at 0.6 s0.6 s
  2. saas-founders.com at 1.2 s1.2 s
  3. saas-founders.com at 1.8 s1.8 s
  4. saas-founders.com at 2.5 s2.5 s
  5. saas-founders.com at 3.1 s3.1 s
  6. saas-founders.com at 3.7 s3.7 s
  7. saas-founders.com at 4.3 s4.3 s
  8. saas-founders.com at 4.9 s4.9 s

Speed

7 to fix60
  • Improve image delivery

    3.6 s · 2.0 MB

    13 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    3.0 s

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

  • Reduce unused CSS

    1.5 s · 290 KiB

    About 290 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (WordPress and WordPress Site Stats), adding 5.2 MB and 8 ms of main-thread time.

  • WordPress adds 7 ms

    7 ms

    WordPress costs a phone 7 ms of main-thread work and 5.2 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.

  • Font display

    350 ms

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

  • Minify CSS

    150 ms · 38 KiB

    38 KiB could be saved by minifying CSS.

  • Reduce unused JavaScript

    150 ms · 31 KiB

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

  • 3 long tasks on the main thread

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 37 ms

    37 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 28.8 s

    28.8 s

    Your largest element takes 28.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE GREATEST SAAS FOUNDERS OF OUR GENERATION! Learn more”.

  • Time to Interactive: 29.0 s

    29.0 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 10 images without width and height

    10 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
  • Total Blocking Time: 74 ms

    74 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 8.0 MB in 88 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 88 requests on a phone: images 6.5 MB (27), fonts 849 KiB (15) and stylesheets 337 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.26 g

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

Accessibility

4 to fixGoogle 8582
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Skip links are not focusable.

    Skip links are not focusable. (1 element).

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 9 automated accessibility rules passed

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

SEO

5 to fixGoogle 8575
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “SaaS Founders – Learn about the greatest SaaS Founders of our Generation!”.

  • 29 links with vague text

    29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Meta description is long (395 characters)

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

  • 2 links crawlers can't follow

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

  • 56 internal links, 9 external

    The homepage links to 56 pages on saas-founders.com and 9 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://saas-founders.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

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

    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 description; sameAs (social profiles) and contact details would complete it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://saas-founders.com/saas-founders-books has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://saas-founders.com/about, https://saas-founders.com/articles, https://saas-founders.com/contact and https://saas-founders.com/saas-founders-books have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://saas-founders.com/about and https://saas-founders.com/contact 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 19 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    8 pages of 15 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.

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

Best practices

1 to fixGoogle 10092
  • 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 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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: 25 trust badges. 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 33 words

    The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Learn more” and “Start Exploring”.

  • 2 short forms

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

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 saas-founders.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
jQuery
E-commerce
WooCommerce
Hosting
WordPress.com

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 saas-founders.com, including 12 speed issues, 5 SEO issues and 5 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