What is PLS by browser
PLS by browser lens breaks down Perceived Load Speed (PLS) across the browsers your users are actually using — such as Chrome, Safari, Firefox, and Edge.
Each browser renders content slightly differently and may interpret your website’s structure, resources, and scripts in unique ways. This lens helps you uncover browser-specific performance patterns that can otherwise go unnoticed.
Healthy PLS by browser sample
Should you worry
A healthy PLS by browser lens shows consistent, low perceived load speed across all major browsers. While minor differences are expected, especially between Chromium-based and WebKit browsers, no browser should stand out as significantly slower.
If a major portion of your users experience higher PLS in one browser, their experience will feel sluggish — even if your overall metrics look fine.
Unhealthy PLS by browser sample
When one browser consistently shows slower perceived load times, it’s often due to compatibility issues, inconsistent rendering of heavy content, or under-optimized assets for that specific engine.
For example, Safari might show slower PLS due to image format handling or script timing, while Firefox may struggle with certain CSS effects. Identifying these differences early can help preserve performance across all your users.
Resolving unhealthy PLS by browser
Go-to action plan to resolve an unhealthy PLS by browser:
Ask Uxi to analyze your PLS by browser and suggest improvements.
Use Filters to isolate the browser and identify if certain page types or components load slowly.
Simulate LCP of the suspected lens to see if fixing it will resolve the PLS by browser. If yes, this is where the resolution focus should be.
Use an automated optimization tool like Navigation AI to improve your PLS by browser.
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.