Skip to main content

PLS by URL sample

PLS by URL sample without noise

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


What is PLS by URL sample

PLS by URL sample compares Perceived Load Speed (PLS) for pages included in the Google CrUX dataset versus those that aren’t. This reveals how your site performs in the broader web performance landscape — and how your real user experience stacks up against what Google sees.

CrUX (Chrome User Experience Report) collects performance data from opted-in Chrome users across the web. Pages that meet CrUX’s visibility thresholds get included in the public dataset. Others, like admin pages, low-traffic URLs, or pages with strict cookie controls, don’t make the cut.



Healthy "PLS by URL sample" sample


Should you worry

If your CrUX-eligible pages have significantly better PLS than your non-CrUX pages, it might mean your most visible experiences are fast — but other areas of the site may be lagging behind. Conversely, if CrUX pages are slower, those performance issues are more likely to be picked up by external monitoring and could affect rankings or user trust.

Use this lens to assess whether your key landing pages (often indexed by Google and eligible for CrUX) are delivering the perceived speed that encourages engagement.

Unhealthy "PLS by URL sample" sample

An unhealthy pattern shows up when CrUX-included pages have higher PLS values than non-CrUX ones — meaning that the performance seen by search engines is slower than what most users experience elsewhere. This may lead to a skewed public impression of your site speed.

Another red flag: if non-CrUX pages have consistently poor PLS, it may indicate overlooked issues in gated, dynamic, or lower-traffic sections that still impact user experience.

Resolving unhealthy PLS by URL sample

Go-to action plan to resolve an unhealthy PLS by URL sample:

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

  2. Use Filters to isolate which pages have poor perceived speed and why.

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

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

  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?