Skip to main content

PLS by U-turns

PLS by U-turns without noise

Vasil Dachev avatar
Written by Vasil Dachev
Updated over 2 months ago


What is PLS by U-turns

PLS by U-turns shows how Perceived Load Speed (PLS) differs for users who make a U-turn compared to those who stay and interact with the page.

A U-turn occurs when a user lands on a page, stays for five seconds or less, doesn’t interact (no clicks, scrolls, or inputs), and then navigates back to the previous page. It’s a strong signal that something didn’t meet expectations — often tied to how quickly the page looked ready.

This breakdown helps you see whether a slow-perceived load experience (poor PLS) is contributing to early abandonment. Since PLS measures how fast users feel the page is loading, higher values can make a site seem sluggish even if technical metrics look fine.

PLS by U-turns sample


Should you worry

In a healthy view, PLS values for U-turn sessions look similar to non-U-turn sessions. U-turns may still occur, but they’re not because the page appeared slow or incomplete.

A healthy setup typically shows:

  • PLS consistently fast across both groups.

  • Above-the-fold content visible quickly, creating a sense of speed.

  • U-turns driven by intent or relevance, not perceived slowness.

If PLS feels fast to users, abandonment is less likely tied to loading perception.

Unhealthy PLS by U-turns

If U-turn sessions consistently show slower PLS values, users may be leaving because the page doesn’t look ready soon enough.

Common causes include:

  • Empty or blank above-the-fold sections during initial load.

  • Large hero images delaying visual completion.

  • Animations or placeholders extending the perceived load.

  • Late-loading ads, fonts, or scripts blocking visual stability.

Here, poor PLS means users don’t feel the site is usable fast enough, leading to U-turns.

Resolving unhealthy PLS by U-turns

Go-to action plan to resolve an unhealthy PLS by U-turns:

  1. Ask Uxi to analyze your PLS by U-turns and suggest improvements.

  2. Use Filters to compare PLS gaps between U-turn and non-U-turn sessions by device or geography.

  3. Simulate LCP of the suspected breakdown to see if fixing it will resolve the PLS by U-turns. If yes, this is where the resolution focus should be.

  4. Use an automated optimization tool like Navigation AI to improve your PLS by U-turns.

  5. Once you’ve improved PLS, set an alert to be the first to know if it starts worsening again.

Try it yourself

Discover how your website performs with real user data.

Did this answer your question?