Skip to main content

PLS by shopping cart

PLS by shopping cart without noise

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


What is PLS by shopping cart

PLS by shopping cart compares Perceived Load Speed (PLS) for users who have items in their shopping cart versus those who don’t. This helps identify if cart state affects how fast the page feels to load.

PLS is Uxify’s real-user metric that reflects when the page visually feels ready. Since e-commerce experiences often personalize based on cart status, it’s crucial to ensure that personalization doesn’t degrade perceived speed.

Having items in the cart can trigger extra scripts, dynamic rendering, or personalized components — like cart drawers, recommendations, or banners — all of which can delay when the page appears visually ready.

Healthy PLS by shopping cart sample


Should you worry

A healthy cart-related PLS means both groups — with and without items — experience fast perceived load times. This suggests that cart-dependent components are well optimized and don’t block visual readiness.

Unhealthy PLS by shopping cart sample

When the PLS is noticeably slower for users with items in the cart, it indicates that personalization, dynamic elements, or third-party scripts tied to the cart might be delaying perceived load completion.

Resolving unhealthy PLS by shopping cart

Go-to action plan to resolve an unhealthy PLS by shopping cart:

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

  2. Use Filters to isolate sessions with items in the cart and check which pages have the highest PLS with the most traffic.

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

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

  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?