> ## 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, Amplitude > Landing Page Performance vs Bounce for Amplitude 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:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Landing Page Performance vs Bounce** is a cross-channel card that lines up each landing page's performance signal against the bounce rate Amplitude measures for visitors who arrive on it. Read as a table, it lets you spot pages where a slow or weak experience is driving people straight back out. When a sluggish landing page and a high bounce rate co-occur on the same row, that page is quietly losing sessions before they ever reach the funnel, which is revenue left on the table at the very top of the journey. | | | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Each landing page broken out by row, pairing its performance signal with the Amplitude bounce rate for sessions that land there. | | **Sample type** | Amplitude session and page data combined with landing-page performance signal, refreshed on the standard data refresh. | | **Why it matters** | Slow landing pages with high bounce rates leak traffic before it can convert. Finding those rows tells you exactly where a fix recovers the most sessions. | | **Reading the value** | Scan the table for rows where weak performance and high bounce appear together. Those pages are the priority. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `slow landing page + high bounce co-occur` | | **Sentiment key** | `amp_xc_landing_page_perf_vs_bounce` | | **Roles** | owner, marketing | ## Calculation For each significant landing page, this card pairs a performance signal with the bounce rate Amplitude records for sessions that begin on that page, presenting the result as a sortable table over the selected period. The alert flags rows where a slow page and a high bounce rate occur together, since that combination is the strongest indicator of experience-driven drop-off. See the At a glance summary above for what the card tracks and the worked example below for a typical reading. ## Worked example *A representative reading of **Landing Page Performance vs Bounce** for a typical merchant on Amplitude.* For the 30 days to 22 Mar 26 most landing pages sit around a 45 percent bounce rate with healthy load performance. One campaign landing page stands out: it is noticeably slower to become usable and shows a 71 percent bounce rate against a much larger arriving audience. The row jumps out because both signals are bad at once, so the co-occurrence condition fires. Vortex Mind traces the slow performance to an oversized hero image and a third-party script blocking render, and links the bounce spike to a paid campaign sending high-intent traffic to that exact page. Ask Viq is used to ask, in plain English, how many sessions that page lost to bounce in the period, which frames the opportunity before the page is optimised. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | | [`amp_top_pages`](/nerve-centre/kpi-cards/amplitude/top-pages) | Identifies which landing pages carry the most traffic to prioritise. | | [`amp_bounce_rate`](/nerve-centre/kpi-cards/amplitude/bounce-rate) | Gives the overall bounce rate context behind the per-page rows. | | [`amp_pageviews_per_session`](/nerve-centre/kpi-cards/amplitude/pageviews-per-session) | Shows whether non-bouncing visitors go on to explore. | | [`amp_top_sources`](/nerve-centre/kpi-cards/amplitude/top-traffic-sources) | Reveals which sources feed the high-bounce landing pages. | | [`amp_xc_session_quality_vs_cart_abandonment`](/nerve-centre/kpi-cards/amplitude/session-engagement-vs-cart-abandonment) | Another cross-channel view of engagement quality versus drop-off. | ## Reconciling against Amplitude **Where to look in Amplitude's own dashboard:** Use Event Segmentation or a Pathfinder report grouped by landing page to read bounce behaviour per page, and pull the page performance signal from your performance tooling. This card combines two different systems, so the performance side lives outside Amplitude. Amplitude Dashboards can hold the bounce view; compare it against the same 30-day window in Vortex IQ. Confirm how a landing page and a bounce are defined before deciding the readings disagree. **Why the Vortex IQ value may legitimately differ:** Because this is a cross-channel card, you are comparing Amplitude event data with a separate landing-page performance source. Definitional differences between the two systems are expected, not a fault. | Reason | Direction | What to do | | ------------------------------------------------------------------------------------------------------------------------------------------ | --------- | ---------------------------------------------- | | **Period boundary.** The bounce window and the performance sampling window may not align exactly. | Variable | Match both to the same 30-day window. | | **Time zone.** Amplitude uses the project time zone; Vortex IQ aligns to the merchant reporting time zone. | Marginal | Confirm time zone match. | | **Definition and scope.** What counts as a bounce, and which pages count as landing pages, can differ between systems and profile filters. | Variable | Align the bounce and landing-page definitions. | **Cross-connector reconciliation:** because two systems are compared, expect baseline differences and focus on the rows where both signals move together. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: Why does Amplitude's bounce rate differ from my performance tool's view?** The two come from different systems with different definitions. Amplitude measures session behaviour, while a performance tool measures load and render timing. A row matters most when both signals are weak together, regardless of small definitional gaps. **Q: A page is slow but has a low bounce rate. Should I still fix it?** Performance is worth improving on its own, but this card prioritises rows where slow performance and high bounce co-occur, because those are where speed is most clearly costing you sessions. Use the broader performance cards for slow-but-sticky pages. **Q: How do I know which page to fix first?** Sort the table by the pages with both the worst performance and the highest bounce against meaningful traffic. A high-bounce page with little traffic recovers less than a moderately bad page that receives a large campaign audience. **Q: Can I customise the co-occurrence threshold?** Yes, the performance and bounce thresholds that define a flagged row are configurable per profile in the Sensitivity tab. Tune them to your store's typical landing-page baselines rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *Landing Page Performance vs Bounce* is one of hundreds of KPI pulses Vortex IQ tracks across Amplitude 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.