Kajabi Paid-Funnel Revenue Leak Report
Two confirmed paid-funnel leaks on Kajabi’s live comparison route—one slowing mobile acquisition, one breaking signup intent.
Two confirmed paid-funnel leaks on Kajabi’s live comparison route—one slowing mobile acquisition, one breaking signup intent.
Company audited: Kajabi
Business URL: https://kajabi.com
Paid destination audited: https://www.kajabi.com/vs/teachable
Audit date: July 24, 2026
Ad evidence: Five current public ad records were reviewed. Two route to the Kajabi-vs-Teachable page; one of those uses a Sign Up CTA and the other uses Learn More.
Funnel depth tested: paid ad destination → Kajabi-vs-Teachable sales page → linked online-courses product page. The signup form, account creation, order form/payment, form submission, confirmation email, and lifecycle email were not tested. No payment or irreversible action was attempted.
Owner Brief
Your comparison campaign is sending paid prospects to a live, relevant Kajabi page—but the mobile experience creates two measurable leaks before those visitors can start a trial.
We found two priority issues worth fixing and monitoring: the paid destination’s largest mobile content element took 10.3 seconds to render in a controlled test, and a Sign Up ad hands mobile visitors to a hero whose visible actions are See Full Comparison and Watch our demo, not signup.
This is not a generic website critique. Both issues sit directly on a current paid route and can quietly reappear when campaign destinations, page code, scripts, navigation, or responsive layouts change.
Paid-ad problems
1. Paid mobile visitors can wait 10.3 seconds for the page’s largest content element
Confidence: Confirmed
Two current public ads route directly to your Kajabi-vs-Teachable destination. In a controlled mobile diagnostic on that live page, the largest content element rendered at 10.33 seconds. The first content appeared at 7.08 seconds, total blocking time was 998 milliseconds, and the page made 159 requests. The resulting mobile performance score was 34/100.
The same destination measured 1.99 seconds for its largest content element on desktop. That mobile-versus-desktop gap points to a device-specific acquisition risk rather than a universally slow page.
Why this wastes spend: A comparison-page visitor is already evaluating Kajabi against a named competitor. If the mobile page takes several seconds to communicate its main value, the campaign pays for clicks that may abandon before the comparison or trial path becomes usable.
First fix: Profile the mobile critical path on this exact paid destination. Start with the approximately 1.15 MiB of unused JavaScript identified in the test, third-party code that occupied the main thread, and render-blocking resources. Re-test from a mobile profile after each change rather than optimizing against the desktop result.
What continuous monitoring should catch: mobile largest-content render time, first-content render time, blocking time, request count, page weight, and regressions introduced by new analytics, personalization, chat, experimentation, or campaign scripts.
2. A Sign Up ad becomes a comparison-first hero on mobile
Confidence: Confirmed
One current ad routes to this page with a Sign Up CTA. On mobile, the destination opens with “Which platform is right for you?” and presents “See Full Comparison” plus “Watch our demo.” The desktop navigation exposes Start Free Trial, but the mobile header replaces navigation with a menu icon, so no signup action is visible in the captured first viewport.
Evidence: the paid mobile destination leads with comparison and demo actions; the signup action promised by the ad is not visible in the first viewport.
Why this wastes spend: The visitor clicked a direct-response signup prompt but receives a research-oriented next step. That extra decision can reduce message continuity and forces a ready-to-start prospect either to open the menu, scroll, or switch intent to a demo/comparison path.
First fix: For traffic from the Sign Up ad, add a visible mobile hero CTA such as Start Free Trial, while retaining See Full Comparison as the lower-commitment secondary action. If the page is intentionally education-first, align that campaign CTA to Learn More instead.
What continuous monitoring should catch: each ad’s CTA and final destination, first-viewport headline and actions by device, mobile menu state, and whether the promised conversion action remains visible after page or navigation releases.
Live-funnel evidence
Desktop overview: the comparison page renders successfully, keeps Start Free Trial visible in navigation, and moves into the side-by-side guide below the hero.
Mobile overview: the page renders genuine Kajabi content without a challenge screen, but the first viewport changes the paid signup path into comparison and demo choices.
What we verified—and what remains untested
The paid destination, desktop and mobile presentation, 20 sampled links, tracking requests, comparison content, and a linked online-courses page were reviewed. All 20 sampled links resolved successfully. Campaign parameters were retained on the tested page load and propagated into observed cross-domain signup links.
The safe trace did not submit a signup form or create an account. It did not reach a payment/order form, send a form submission, or verify confirmation and lifecycle emails. Those steps require an approved test identity and inbox; any payment-stage monitoring should use a test environment or explicit authorization.