Skip to main content

PLS by page

PLS by page without noise

Vasil Dachev avatar
Written by Vasil Dachev
Updated over a week ago


What is PLS by page

PLS by page shows how long each individual page on your website takes to load — not technically, but as perceived by your real users. Perceived Load Speed (PLS) is Uxify’s real-user metric that captures the moment when users feel the page is visually complete and ready to interact with.

Each row in this view represents a single page URL. Pages with high pageviews and poor PLS are high-priority candidates for optimization because they slow down the experience for many users at once.

Unlike metrics like LCP, which only measure the load time of the largest element on the screen, PLS reflects the loading experience of all meaningful content in view — making it the best representation of how fast a page feels to load.



Healthy PLS by page sample


Should you worry

A healthy PLS by page lens is one where the highest-traffic pages also have fast perceived load times. These pages typically fall into the green zone (good performance). Pages in yellow or red indicate that users are waiting too long to start interacting with content — and these can quickly lead to frustration, drop-offs, and lower engagement.

If high-traffic or high-value pages (such as product, checkout, or landing pages) are showing slow PLS, it's time to investigate. A fast page feels better, even if the underlying technical load hasn’t changed.

Unhealthy PLS by page sample

An unhealthy PLS by page view often reveals that a small number of pages account for the bulk of perceived slowdowns. These are typically complex layouts, media-heavy experiences, or pages burdened by third-party content. If these slow pages also have high pageviews, they can disproportionately impact user engagement and conversion.

Resolving unhealthy PLS by page

Go-to action plan to resolve an unhealthy PLS by page:

  1. Ask Uxi to analyze your PLS by page and suggest improvements.

  2. Use Filters to focus on the slowest pages and look across other lenses (like device, connection, or layout type) to identify patterns.

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

  4. Use an automated optimization tool like Navigation AI to improve your PLS by page.

  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?