# Testing a Sticky Section Menu on a Long Landing Page

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/testing-a-sticky-section-menu-on-a-long-landing-page

## Hypothesis

If a long page gets a section menu that stays fixed while visitors scroll, they may reach the section they want without scrolling through everything else. Less hunting could lift the primary action completion rate, though the effect could reverse if the menu crowds the main content on mobile.

## When to run this test

Visitors who cannot find what they need on a long page leave a trail: repeated up-and-down scrolling in session recordings, exits before certain sections are reached, and support requests about questions the page already answers. With the menu in place, visitors should reach the section they need sooner and move from there to the primary action. If the problem lies in the content of the sections, a menu will not fix it, so review the content first, and confirm before launch that the menu works with a keyboard.

## Primary metric

**Primary action completion rate**: Compare whether adding navigation changes completion of the target action.

## Other metrics

- **Navigation usage rate**: Check whether visitors use the links.
- **Section visibility**: Measure actual visibility; jumping to a section does not show that intervening content was read.
- **Time to reach a target section**: If the task is known, measure time to the predefined section; do not infer intent from every jump.
- **Page exit rate**: Check whether exits after jumping to one section increase.

## What to check before and during the test

- **Navigation**: Add one fixed navigation element linked to existing sections.
- **Keep constant**: Keep section names, order, content and CTA unchanged.
- **Destination**: Keep the heading of the destination section visible.
- **Mobile**: Leave enough space for the main content on mobile.
- **Separate test**: A sticky table of contents or new section labels is a separate comparison.

## What to watch when reading the result

- Do not dismiss the menu because the navigation usage rate stays low; it may be critical for visitors who arrive with a specific need. What decides the result is the primary action completion rate, and if exits after a single jump rise while actions stay flat, do not ship it.
- Read mobile and desktop separately; if the menu takes up enough space on mobile to squeeze the content, a desktop gain can hide that loss. Keep in mind that jumping to a section does not show the content in between was read, and that the result applies to this page's length and section structure.
- When the difference is small, check time to reach a target section, but do not read intent into every jump. Because only part of the audience may use the menu, the overall difference can take a while to show; get the visitors needed per arm from the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator). Divide that by daily visitors per arm to decide up front how long the test stays open.

## Frequently Asked Questions

### Should low use mean section navigation is removed?

No. An infrequent shortcut can serve an important task. Use completed main actions as the primary outcome and monitor visits that end immediately after a jump.

### What mobile risk comes from sticky section navigation?

It reduces content space and may cover headings or controls. Check the occupied area and scroll destinations rather than allowing the navigation to dominate the screen.

### Does jumping to a section establish that intervening content was read?

No. Measure actual section exposure and relevant task time. Preserve keyboard navigation, and do not infer intent from a jump alone.