Skip to main content

PLS by element

PLS by element without noise

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


What is PLS by element

PLS by element breaks down your Perceived Load Speed (PLS) based on the type of Largest Contentful Paint (LCP) element present on the page — whether it was an image (like a hero photo or banner) or a non-image (such as a headline or block of text).

This helps you understand if slower perceived speed is related to visual media (which are often heavier) or structural content (which might load faster but could shift or block visual completeness).



Healthy PLS by element sample


Should you worry

A healthy PLS by element view shows minimal difference between image and non-image LCP types — both delivering a smooth and fast perceived load experience. If image pages are slower, the difference should be negligible (e.g. within 200–300ms).

Unhealthy PLS by element sample

When image-based LCP pages consistently show higher PLS values, it often means large assets (like hero images or product banners) are delaying how complete the page feels. Even if the rest of the page loads quickly, one slow image can ruin the perception of speed.

On the other hand, if non-image LCP pages have high PLS, that could point to layout instability or delayed text rendering — which also hurts perceived smoothness.

A consistently slower PLS for image-based LCP pages can signal issues like:

  • Heavy or unoptimized media formats

  • Slow CDN response

  • Missing preload hints

  • Delayed rendering of above-the-fold content

For non-image elements, issues may involve:

  • Late-loading fonts

  • Render-blocking scripts

  • Layout shifts that delay perceived readiness

Resolving unhealthy PLS by element

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

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

  2. Use Filters to focus on pages where the perceived speed is slow when the LCP element is an image (or non-image), and trace which contributing factors (like size, load order, or rendering delay) are driving that slower experience.

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

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

  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?