Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.scalev.com/llms.txt

Use this file to discover all available pages before exploring further.

A newly created Scalev landing page always performs great. Fast speed. Minimum OCLP results touching ~90% in your ad dashboard. Even more so when optimized following this article → Advanced Landing Page Optimization Tutorial with Speed Boost Feature Performance becomes more optimal and stable. But… Over time, even if a landing page performed well initially, its speed will gradually decline. OCLP results no longer reach the expected target.

​
Why Does a Landing Page Slow Down?

Many factors cause it. A landing page that’s been running for a long time on Scalev with a custom domain often experiences performance drops caused by several factors. Could be due to:
  • Accumulation of tracking and analytics data
  • Sub-optimal cache from various sources
  • Increasingly complex interaction history
  • etc.
So what’s the solution?

​
Duplicate Landing Page and Swap Slug Trick

The concept:
  1. Duplicate the underperforming landing page
  2. Optimize the duplicate landing page with a fresh configuration
  3. Swap slugs between the old and new landing page
Slug swap means rotating/exchanging the slug name used in a Scalev landing page. A slug looks like this, for example: https://yourstore.com`**/this-is-the-lp-slug**`

​
How to Swap Slugs

Before performing a slug swap, it’s worth:
  • Choosing the right time (usually when traffic is low)
  • Preparing a backup of the old landing page
  • Thoroughly testing the duplicate landing page
Here’s how. So, there are two landing pages:
  1. Original landing page (LP 1)
  2. Duplicate landing page (LP 2)
The original landing page is your currently active landing page that’s still running but with declining performance. The duplicate landing page is the fresh landing page that will be the swap target from the original. For example, Original landing page slug is **/lp-ori** (LP 1) When duplicated in Scalev, its slug becomes **/lp-ori-duplicated** (LP 2) Change the original landing page slug to **/lp-ori-2** (LP 1) Then change the duplicate landing page slug to **/lp-ori** (LP 2) I labeled them LP 1 and LP 2 so you don’t get confused about which is the original and which is the duplicate. Note that during the slug swap process, traffic coming to your original landing page may hit 404 for a few seconds. After the slug swap completes, everything returns to normal. At this point you’ve successfully performed the slug swap. Your original landing page now uses the new landing page configuration. Hopefully speed and performance will improve.