Skip to main content

PLS by error clicks

PLS by error clicks without noise

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


What is PLS by error clicks

PLS by error clicks shows how Perceived Load Speed (PLS) differs for sessions where users encounter error clicks compared to those without them.

An error click occurs when a user interacts with something but the outcome fails — like submitting a form that throws an error, clicking a broken link, or pressing a button that doesn’t respond properly. While these failures are functional, slow perceived speed (poor PLS) can make them feel even worse by dragging out the failure experience.

This breakdown helps you see whether sluggish-feeling loads are amplifying error frustration. If users don’t see immediate feedback, even minor errors can feel like the site is broken.

PLS by error clicks sample


Should you worry

In a healthy view, PLS values for error click sessions look similar to those without them. Errors may still happen, but they’re tied to business logic or validation — not perceived slowness.

A healthy setup typically shows:

  • PLS consistently fast in both groups.

  • Error messages appear instantly and clearly.

  • Failures feel functional, not like performance issues.

If PLS is strong, error clicks are not caused or worsened by perceived load delays.

Unhealthy PLS by error clicks

If error click sessions consistently show slower PLS values, perceived delays are making errors worse.

Common causes include:

  • Forms submitting slowly before returning an error.

  • Late-appearing error messages, leaving users uncertain.

  • Unresponsive buttons that feel broken before the error displays.

  • Heavy scripts or API delays dragging out feedback.

Here, poor PLS makes errors more painful by hiding or delaying system responses.

Resolving unhealthy PLS by error clicks

Go-to action plan to resolve an unhealthy PLS by error clicks:

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

  2. Use Filters to compare PLS for error sessions by device, geography, or traffic type.

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

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

  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?