At a glance
Landing Page Performance vs Bounce is a cross-channel table that sets each landing page’s performance against its bounce rate. It is built to catch a costly co-occurrence: a slow or poorly performing landing page that also bleeds visitors before they engage. When sluggish load and high bounce show up on the same page, you have found a leak you are paying to fill with traffic, and this table ranks those pages so you fix the worst first.
| What it counts | Each landing page with its performance signal alongside its bounce rate, ranked to surface the worst combinations. |
| Sample type | Backend API data from PostHog page and session data, aligned with performance signals on the standard data refresh. |
| Why it matters | A slow landing page that also bounces visitors wastes acquisition spend twice. Pairing the two metrics turns a vague “the page is bad” into a ranked fix list. |
| Reading the value | Read each row as a page. The pages where weak performance and high bounce co-occur are the priority fixes. |
| Currency | count |
| Time window | 30D |
| Alert trigger | slow landing page + high bounce co-occur |
| Sentiment key | ph_xc_landing_page_perf_vs_bounce |
| Roles | owner, marketing |
Calculation
Calculated automatically from your PostHog data alongside your connected performance signals. See the At a glance summary above for what the metric 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 PostHog. Suppose a paid-traffic landing page loads slowly and bounces 71% of visitors, while your homepage loads fast and bounces 38%. The table ranks the slow, high-bounce page at the top because that is where money leaks: you pay for the click, the page is slow, the visitor leaves. After an image-optimisation fix on 02 Jun 26, the page’s bounce falls to 49% and it drops down the ranking. Cross-reference Bounce Rate and Top Pages for the per-page detail. 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 |
|---|---|
pos_bounce_rate | Engagement sibling: bounce rate. |
pos_top_pages | Engagement sibling: highest-traffic pages. |
pos_top_sources | Engagement sibling: where landing traffic comes from. |
ph_xc_session_quality_vs_cart_abandonment | Cross-channel sibling: session quality vs abandonment. |
ph_paths_top_route | Funnels sibling: where users go after landing. |
Reconciling against the vendor’s own dashboard
Where to look in PostHog’s own dashboard: In PostHog, a trend or table insight on entry pages with a bounce filter gives the bounce side per landing page. The performance side comes from your connected performance signals. Line the two up per page to reproduce this table. Bounce definitions, single-event versus single-pageview sessions, are the main source of difference. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Bounce definition. A bounce as a single pageview versus a single event gives different rates. | Variable | Match the bounce definition. |
| Landing-page grouping. Query strings can split one landing page into several rows. | Variable | Apply URL cleaning. |
| Performance source. The performance signal may come from a separate connector with its own sampling. | Variable | Confirm the performance source. |