> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Landing Page Performance vs Bounce, Mixpanel > Landing Page Performance vs Bounce for Mixpanel stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Cross-Channel: Revenue at Risk](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Landing Page Performance vs Bounce** cross-references how fast your landing pages load against how often visitors bounce off them in Mixpanel. A page that loads slowly and bounces hard is leaking revenue at the front door, the visitor never gets far enough to convert. This card pairs the two signals so the pattern is obvious: instead of scanning a performance report and a bounce report separately, you see, page by page, where slowness and exits line up. Those are the pages where a speed fix pays for itself directly in retained sessions. | | | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The set of landing pages where a slow performance signal and a high Mixpanel bounce rate occur together, listed so the worst offenders rise to the top. | | **Sample type** | Backend API data joining landing-page performance signals against Mixpanel bounce data for the same pages over the window. | | **Why it matters** | Slow pages that bounce visitors waste the traffic you already paid to acquire. Finding where speed and exits co-occur tells you which fixes recover the most sessions. | | **Reading the value** | A table of landing pages with their performance signal and bounce alongside. Look for rows where both are poor at once; those are the highest-leverage pages to fix. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `slow landing page + high bounce co-occur` | | **Sentiment key** | `mix_xc_landing_page_perf_vs_bounce` | | **Roles** | owner, marketing | ## Calculation Vortex IQ takes the landing-page performance signal for each entry page and joins it to the bounce rate Mixpanel records for sessions that started on that page over the window. Pages are ranked so that those scoring poorly on both dimensions at once surface first. The alert latches when a landing page shows both a slow performance reading and an elevated bounce rate together, since either signal alone is less actionable than the combination. The performance signal reflects how the page loads and becomes usable; the bounce side reflects how many of those sessions left without a meaningful second interaction. ## Worked example *A representative reading of **Landing Page Performance vs Bounce** for a typical merchant on Mixpanel.* Suppose most of your landing pages load briskly and bounce around 40%. The card lists one campaign landing page, used by an ad set since 09 Jun 26, that loads noticeably slower than the rest and bounces at 71%. Because both signals are poor on the same row, the card flags it. You open the page, find a large unoptimised hero image and a render-blocking script added with the campaign, and ship a fix. Over the following week bounce on that page settles back toward the 40s and the flag clears. The traffic was fine all along; the page was turning it away. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | [`mix_bounce_rate`](/nerve-centre/kpi-cards/mixpanel/bounce-rate) | The bounce side of this comparison across all sessions, not just the flagged pages. | | [`mix_top_pages`](/nerve-centre/kpi-cards/mixpanel/top-pages) | Shows which pages carry the most traffic, so you can weigh a fix by how many visitors it touches. | | [`mix_flows_top_exit_event`](/nerve-centre/kpi-cards/mixpanel/top-exit-event) | Names the event where users most often leave, complementing the page-level bounce view. | | [`mix_pageviews_per_session`](/nerve-centre/kpi-cards/mixpanel/pageviews-per-session) | Low pageviews per session confirms visitors are leaving early, the behaviour behind a high bounce. | | [`mix_xc_session_quality_vs_cart_abandonment`](/nerve-centre/kpi-cards/mixpanel/session-engagement-vs-cart-abandonment) | A sister cross-channel card; isolates whether the problem is the entry page or later, at checkout. | ## Reconciling against Mixpanel **Where to look in Mixpanel's own dashboard:** In Mixpanel, build a bounce or single-event-session view broken down by landing page over the last 30 days, and note the bounce rate for the pages the card flags. Then check those same URLs in your performance tooling to confirm the load signal. The card's value is the join of the two; reproducing it by hand means lining up the bounce figure and the performance figure for each URL and looking for pages where both are poor. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------------------------- | | **Bounce definition.** What counts as a bounce (no second event vs short session) varies by setup. | Variable | Match the bounce definition the card uses before comparing. | | **Page grouping.** Query strings and variants may be merged or split differently. | Variable | Normalise URLs the same way in both views. | | **Performance sampling.** The performance signal may sample devices or regions the bounce data does not. | Variable | Compare on a like-for-like device and region split. | **Cross-connector reconciliation:** this card joins Mixpanel bounce behaviour with a landing-page performance signal, so the two sides come from different feeds by design. When they disagree, confirm the URL grouping matches on both sides before concluding the page is fine. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Landing Page Performance vs Bounce update?** It refreshes as both feeds report for the window. Mixpanel bounce data and the landing-page performance signal each update on their own cadence, so a flagged page settles once both sides have fresh readings. **Q: A page is slow but bounce is fine. Why is it not flagged?** The card deliberately requires both signals to be poor together. A slow page that still keeps visitors is lower priority than a slow page that drives them away, so single-signal pages do not raise the alert. **Q: Bounce is high but the page loads fast. What does that mean?** Speed is not the problem there. A fast page with high bounce usually points to a relevance or messaging mismatch, the wrong audience landed, or the page did not match the ad's promise. Treat it as a targeting or content issue rather than a performance one. **Q: Can I customise the alert threshold?** Yes, the bounce level, the performance threshold, and how the two must co-occur are configurable per profile in the Sensitivity tab. Tighten them for revenue-critical landing pages, loosen them for low-traffic pages where small numbers are naturally noisy. *** ### Tracked live in Vortex IQ Nerve Centre *Landing Page Performance vs Bounce* is one of hundreds of KPI pulses Vortex IQ tracks across Mixpanel and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.